[If you choose to not CC the same set of people on all patches - which
is sometimes a legit thing to do - then please cc them to the cover
letter at least.]
On Fri 13-04-18 15:16:24, David Hildenbrand wrote:
> I am right now working on a paravirtualized memory device ("virtio-mem").
> These devices control a memory region and the amount of memory available
> via it. Memory will not be indicated via ACPI and friends, the device
> driver is responsible for it.
How does this compare to other ballooning solutions? And why your driver
cannot simply use the existing sections and maintain subsections on top?
--
Michal Hocko
SUSE Labs
