0d9e8c0b67
This driver is like virtio-balloon on steroids: it allows both changing the guest memory allocation via ballooning and (in the next patch) inserting pieces of extra RAM into it on demand from a provided memory backend. The actual resizing is done via ballooning interface (for example, via the "balloon" HMP command). This includes resizing the guest past its boot size - that is, hot-adding additional memory in granularity limited only by the guest alignment requirements, as provided by the next patch. In contrast with ACPI DIMM hotplug where one can only request to unplug a whole DIMM stick this driver allows removing memory from guest in single page (4k) units via ballooning. After a VM reboot the guest is back to its original (boot) size. In the future, the guest boot memory size might be changed on reboot instead, taking into account the effective size that VM had before that reboot (much like Hyper-V does). For performance reasons, the guest-released memory is tracked in a few range trees, as a series of (start, count) ranges. Each time a new page range is inserted into such tree its neighbors are checked as candidates for possible merging with it. Besides performance reasons, the Dynamic Memory protocol itself uses page ranges as the data structure in its messages, so relevant pages need to be merged into such ranges anyway. One has to be careful when tracking the guest-released pages, since the guest can maliciously report returning pages outside its current address space, which later clash with the address range of newly added memory. Similarly, the guest can report freeing the same page twice. The above design results in much better ballooning performance than when using virtio-balloon with the same guest: 230 GB / minute with this driver versus 70 GB / minute with virtio-balloon. During a ballooning operation most of time is spent waiting for the guest to come up with newly freed page ranges, processing the received ranges on the host side (in QEMU and KVM) is nearly instantaneous. The unballoon operation is also pretty much instantaneous: thanks to the merging of the ballooned out page ranges 200 GB of memory can be returned to the guest in about 1 second. With virtio-balloon this operation takes about 2.5 minutes. These tests were done against a Windows Server 2019 guest running on a Xeon E5-2699, after dirtying the whole memory inside guest before each balloon operation. Using a range tree instead of a bitmap to track the removed memory also means that the solution scales well with the guest size: even a 1 TB range takes just a few bytes of such metadata. Since the required GTree operations aren't present in every Glib version a check for them was added to the meson build script, together with new "--enable-hv-balloon" and "--disable-hv-balloon" configure arguments. If these GTree operations are missing in the system's Glib version this driver will be skipped during QEMU build. An optional "status-report=on" device parameter requests memory status events from the guest (typically sent every second), which allow the host to learn both the guest memory available and the guest memory in use counts. Following commits will add support for their external emission as "HV_BALLOON_STATUS_REPORT" QMP events. The driver is named hv-balloon since the Linux kernel client driver for the Dynamic Memory Protocol is named as such and to follow the naming pattern established by the virtio-balloon driver. The whole protocol runs over Hyper-V VMBus. The driver was tested against Windows Server 2012 R2, Windows Server 2016 and Windows Server 2019 guests and obeys the guest alignment requirements reported to the host via DM_CAPABILITIES_REPORT message. Acked-by: David Hildenbrand <david@redhat.com> Signed-off-by: Maciej S. Szmigiero <maciej.szmigiero@oracle.com>
52 lines
653 B
Plaintext
52 lines
653 B
Plaintext
# These are "proxy" symbols used to pass config-host.mak values
|
|
# down to Kconfig. See also kconfig_external_symbols in
|
|
# meson.build: these two need to be kept in sync.
|
|
|
|
config LINUX
|
|
bool
|
|
|
|
config OPENGL
|
|
bool
|
|
|
|
config X11
|
|
bool
|
|
|
|
config SPICE
|
|
bool
|
|
|
|
config IVSHMEM
|
|
bool
|
|
|
|
config TPM
|
|
bool
|
|
|
|
config VHOST_USER
|
|
bool
|
|
|
|
config VHOST_VDPA
|
|
bool
|
|
|
|
config VHOST_KERNEL
|
|
bool
|
|
|
|
config VIRTFS
|
|
bool
|
|
|
|
config PVRDMA
|
|
bool
|
|
|
|
config MULTIPROCESS_ALLOWED
|
|
bool
|
|
imply MULTIPROCESS
|
|
|
|
config FUZZ
|
|
bool
|
|
select SPARSE_MEM
|
|
|
|
config VFIO_USER_SERVER_ALLOWED
|
|
bool
|
|
imply VFIO_USER_SERVER
|
|
|
|
config HV_BALLOON_POSSIBLE
|
|
bool
|