Skip to content

VMware balloon driver over virtio

Dmitry Torokhov lkml 1 version In review

Get series with b4
b4 am [email protected]

Versions newest first

  1. v1 Latest4 patches 4 repliesIn review

Patches in v1 No applies recorded yet

#Subject and filesSizeRepliesApplied
1/4virtio-balloon: allow hypervisor refuse locking some pagesdrivers/virtio/virtio_balloon.c include/linux/virtio_balloon.h+67 -91 reply
2/4virtio-balloon: implement balloon resetdrivers/virtio/virtio_balloon.c include/linux/virtio_balloon.h+54 -30 replies
3/4x86: export vmware_platform() symbolarch/x86/kernel/cpu/vmware.c+2 -00 replies
4/4Add VMware memory balloon driverdrivers/misc/Kconfig drivers/misc/Makefile drivers/misc/vmware_balloon.c+640 -03 replies

Reviews trailers per patch

3 of 4 patches have a Reviewed-by or Acked-by.

PatchAlok KatariaShaileshkumar Jain
1/4R-b R-b
2/4R-b
3/4
4/4R-b

Trailers given in replies are filled; those carried in the patches from earlier versions are outlined with dashes.

Read the v1 thread

Cover letter [RFC/PATCH 0/4] VMware balloon driver over virtio

Hi,

VMware would like to get its Linux balloon driver merged into mainline and is considering doing it within virtio framework.

The following is the initial implementation of our ballooning interface as a virtio device. It allows our hypervisor to work in tandem with virtio_balloon driver and inflate and deflate balloon on demand.

Due to the fact that our monitor works a bit differently from KVM some changes are needed in virtio_balloon itself, namely:

- our hypervisor may refuse locking certain pages. This may happen, for example, when target balloon size is changed since guest polled it last time. We expect guest to try locking different page and release refused pages once target balloon size is reached.

- our hypervisor may, in certain situations, reset the balloon. In this case it expects guest to quickly release all memory allocated by by the balloon but to not bother telling the host about pages being released.

There are more differences (adaptive allocation rates, sleeping allocations) which we intend to address at a later date if it is decided that virtio is the proper subsystem to be used for our driver.

Thanks!

Signature · 1 line
Dmitry