mirror of
https://github.com/edk2-porting/linux-next.git
synced 2024-12-23 20:53:53 +08:00
6b35e40767
After discussions with Anthony Liguori, it seems that the virtio balloon can be made even simpler. Here's my attempt. The device configuration tells the driver how much memory it should take from the guest (ie. balloon size). The guest feeds the page numbers it has taken via one virtqueue. A second virtqueue feeds the page numbers the driver wants back: if the device has the VIRTIO_BALLOON_F_MUST_TELL_HOST bit, then this queue is compulsory, otherwise it's advisory (and the guest can simply fault the pages back in). This driver can be enhanced later to deflate the balloon via a shrinker, oom callback or we could even go for a complete set of in-guest regulators. Signed-off-by: Rusty Russell <rusty@rustcorp.com.au>
19 lines
493 B
C
19 lines
493 B
C
#ifndef _LINUX_VIRTIO_BALLOON_H
|
|
#define _LINUX_VIRTIO_BALLOON_H
|
|
#include <linux/virtio_config.h>
|
|
|
|
/* The ID for virtio_balloon */
|
|
#define VIRTIO_ID_BALLOON 5
|
|
|
|
/* The feature bitmap for virtio balloon */
|
|
#define VIRTIO_BALLOON_F_MUST_TELL_HOST 0 /* Tell before reclaiming pages */
|
|
|
|
struct virtio_balloon_config
|
|
{
|
|
/* Number of pages host wants Guest to give up. */
|
|
__le32 num_pages;
|
|
/* Number of pages we've actually got in balloon. */
|
|
__le32 actual;
|
|
};
|
|
#endif /* _LINUX_VIRTIO_BALLOON_H */
|