Re: [Qemu-devel] [PATCH RFC] s390x/sclp: remove memory hotplug support

>> As migration support is not working, this change cannot really break >> migration. As the memory hotplug device was always created, we can >> simply continue faking support for SCLP_FC_ASSIGN_ATTACH_READ_STOR and >> expose the same information just as if no maxmem and slots parameter was >>

Re: [Qemu-devel] [PATCH RFC] s390x/sclp: remove memory hotplug support

On Mon, 19 Feb 2018 15:33:41 +0100 David Hildenbrand wrote: > From an architecture point of view, nothing can be mapped into the address > space on s390x. All there is is memory. Therefore there is also not really > an interface to communicate such information to the guest. All

[Qemu-devel] [PATCH RFC] s390x/sclp: remove memory hotplug support

>From an architecture point of view, nothing can be mapped into the address space on s390x. All there is is memory. Therefore there is also not really an interface to communicate such information to the guest. All we can do is specify the maximum ram address and guests can probe in that range if