On Mon, Apr 23, 2018 at 08:40:59PM +0300, Michael S. Tsirkin wrote: > On Mon, Apr 23, 2018 at 06:51:15PM +0200, David Hildenbrand wrote: > > Right now we can only map PCDIMM/NVDIMM into guest address space. In the > > future, we might want to do the same for virtio devices - e.g. > > virtio-pmem or virtio-mem. Especially, they should be able to live side > > by side to each other. > > > > E.g. the virto based memory devices regions will not be exposed via ACPI > > and friends. They will be detected just like other virtio devices and > > indicate the applicable memory region. This makes it possible to also use > > them on architectures without memory device detection support (e.g. s390x). > > > > Let's factor out the memory device code into a MemoryDevice interface. > > > > Please note that the "slots" assignment code is not relevant for memory > > devices that will not be exposed via ACPI or similar. That's why that > > part won't be exposed. KVM/vhost "slots" for memory regions are still > > necessary but don't have to be manually specified (e.g. the slot number > > doesn't mather). > > > > So we are basically converting the hotplug memory region to a memory device > > region. I have patches that also set up such a region for s390x. > > Reviewed-by: Michael S. Tsirkin <m...@redhat.com> > > Who's merging this? Eduardo?
I just queued it. Thanks! -- Eduardo