Re: [RFC V2 1/3] mm/hotplug: Prevalidate the address range being added with platform

2020-12-02 Thread Anshuman Khandual
On 12/2/20 2:50 PM, David Hildenbrand wrote: > On 30.11.20 04:29, Anshuman Khandual wrote: >> This introduces memhp_range_allowed() which can be called in various memory >> hotplug paths to prevalidate the address range which is being added, with >> the platform. Then memhp_range_allowed() calls

Re: [RFC V2 1/3] mm/hotplug: Prevalidate the address range being added with platform

2020-12-02 Thread David Hildenbrand
On 30.11.20 04:29, Anshuman Khandual wrote: > This introduces memhp_range_allowed() which can be called in various memory > hotplug paths to prevalidate the address range which is being added, with > the platform. Then memhp_range_allowed() calls memhp_get_pluggable_range() > which provides

[RFC V2 1/3] mm/hotplug: Prevalidate the address range being added with platform

2020-11-29 Thread Anshuman Khandual
This introduces memhp_range_allowed() which can be called in various memory hotplug paths to prevalidate the address range which is being added, with the platform. Then memhp_range_allowed() calls memhp_get_pluggable_range() which provides applicable address range depending on whether linear