Messages in this thread | | | Subject | Re: [PATCH RFC] virtio-mem: check against memhp_get_pluggable_range() which memory we can hotplug | From | David Hildenbrand <> | Date | Tue, 19 Jan 2021 13:27:53 +0100 |
| |
On 18.01.21 14:21, Anshuman Khandual wrote: > > > On 1/18/21 6:43 PM, Anshuman Khandual wrote: >> From: David Hildenbrand <david@redhat.com> >> >> Right now, we only check against MAX_PHYSMEM_BITS - but turns out there >> are more restrictions of which memory we can actually hotplug, especially >> om arm64 or s390x once we support them: we might receive something like >> -E2BIG or -ERANGE from add_memory_driver_managed(), stopping device >> operation. >> >> So, check right when initializing the device which memory we can add, >> warning the user. Try only adding actually pluggable ranges: in the worst >> case, no memory provided by our device is pluggable. >> >> In the usual case, we expect all device memory to be pluggable, and in >> corner cases only some memory at the end of the device-managed memory >> region to not be pluggable. >> >> Cc: "Michael S. Tsirkin" <mst@redhat.com> >> Cc: Jason Wang <jasowang@redhat.com> >> Cc: Pankaj Gupta <pankaj.gupta.linux@gmail.com> >> Cc: Michal Hocko <mhocko@kernel.org> >> Cc: Oscar Salvador <osalvador@suse.de> >> Cc: Wei Yang <richard.weiyang@linux.alibaba.com> >> Cc: Andrew Morton <akpm@linux-foundation.org> >> Cc: catalin.marinas@arm.com >> Cc: teawater <teawaterz@linux.alibaba.com> >> Cc: Anshuman Khandual <anshuman.khandual@arm.com> >> Cc: Pankaj Gupta <pankaj.gupta@cloud.ionos.com> >> Cc: Jonathan Cameron <Jonathan.Cameron@huawei.com> >> Cc: hca@linux.ibm.com >> Cc: Vasily Gorbik <gor@linux.ibm.com> >> Cc: Will Deacon <will@kernel.org> >> Cc: Ard Biesheuvel <ardb@kernel.org> >> Cc: Mark Rutland <mark.rutland@arm.com> >> Cc: Heiko Carstens <hca@linux.ibm.com> >> Cc: Michal Hocko <mhocko@kernel.org> >> Signed-off-by: David Hildenbrand <david@redhat.com> >> Signed-off-by: Anshuman Khandual <anshuman.khandual@arm.com> > > Hello David, > > As your original patch was in the RFC state, I have just maintained > the same here as well. But once you test this patch along with the > new series, please do let me know if this needs to be converted to > a normal PATCH instead. Thank you.
I'll give it a churn on x86-64, where not that much should change. It will be interesting to test with arm64 in such corner cases in the future.
Thanks
-- Thanks,
David / dhildenb
| |