On 1/25/21 2:55 PM, David Hildenbrand wrote: > On 25.01.21 03:58, Anshuman Khandual wrote: >> This series adds a mechanism allowing platforms to weigh in and prevalidate >> incoming address range before proceeding further with the memory hotplug. >> This helps prevent potential platform errors for the given address range, >> down the hotplug call chain, which inevitably fails the hotplug itself. >> >> This mechanism was suggested by David Hildenbrand during another discussion >> with respect to a memory hotplug fix on arm64 platform. >> >> https://lore.kernel.org/linux-arm-kernel/1600332402-30123-1-git-send-email-anshuman.khandual@xxxxxxx/ >> >> This mechanism focuses on the addressibility aspect and not [sub] section >> alignment aspect. Hence check_hotplug_memory_range() and check_pfn_span() >> have been left unchanged. Wondering if all these can still be unified in >> an expanded memhp_range_allowed() check, that can be called from multiple >> memory hot add and remove paths. >> >> This series applies on v5.11-rc5 and has been tested on arm64. But only >> build tested on s390. >> > > Note that this fails to apply right now to both, -next and Linus' tree. > Do you have a branch with he patches on top I can use for a quick test? > Thanks > Applied all four patches on v5.11-rc5. https://gitlab.arm.com/linux-arm/linux-anshuman/-/tree/mm/hotplug_callback/v4/
