Re: [PATCH RFC] virtio-mem: check against memhp_get_pluggable_range() which memory we can hotplug

2021-01-21 Thread Anshuman Khandual
On 1/21/21 3:27 PM, David Hildenbrand wrote: > On 18.01.21 14:21, Anshuman Khandual wrote: >> >> >> On 1/18/21 6:43 PM, Anshuman Khandual wrote: >>> From: David Hildenbrand >>> >>> Right now, we only check against MAX_PHYSMEM_BITS - but turns out there >>> are more restrictions of which memory

Re: [PATCH RFC] virtio-mem: check against memhp_get_pluggable_range() which memory we can hotplug

2021-01-21 Thread David Hildenbrand
On 18.01.21 14:21, Anshuman Khandual wrote: > > > On 1/18/21 6:43 PM, Anshuman Khandual wrote: >> From: David Hildenbrand >> >> 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

Re: [PATCH RFC] virtio-mem: check against memhp_get_pluggable_range() which memory we can hotplug

2021-01-19 Thread David Hildenbrand
On 18.01.21 14:21, Anshuman Khandual wrote: > > > On 1/18/21 6:43 PM, Anshuman Khandual wrote: >> From: David Hildenbrand >> >> 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

Re: [PATCH RFC] virtio-mem: check against memhp_get_pluggable_range() which memory we can hotplug

2021-01-18 Thread Anshuman Khandual
On 1/18/21 6:43 PM, Anshuman Khandual wrote: > From: David Hildenbrand > > 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

[PATCH RFC] virtio-mem: check against memhp_get_pluggable_range() which memory we can hotplug

2021-01-18 Thread Anshuman Khandual
From: David Hildenbrand 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(),

Re: [PATCH RFC] virtio-mem: check against memhp_get_pluggable_range() which memory we can hotplug

2021-01-11 Thread Anshuman Khandual
On 1/11/21 6:11 PM, David Hildenbrand wrote: > 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

[PATCH RFC] virtio-mem: check against memhp_get_pluggable_range() which memory we can hotplug

2021-01-11 Thread David Hildenbrand
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.