[PATCH v5 0/7] Add support for memmap on memory feature on ppc64

[David Hildenbrand]

On 25.07.23 12:02, Aneesh Kumar K.V wrote:
> This patch series update memmap on memory feature to fall back to
> memmap allocation outside the memory block if the alignment rules are
> not met. This makes the feature more useful on architectures like
> ppc64 where alignment rules are different with 64K page size.
> 
> This patch series is dependent on dax vmemmap optimization series
> posted here
> https://lore.kernel.org/linux-mm/20230718022934.90447-1-aneesh.kumar@linux.ibm.com/
> 
> Changes from v4:
> * Use altmap.free instead of altmap.reserve
> * Address review feedback
> 
> Changes from v3:
> * Extend the module parameter memmap_on_memory to force allocation even
>    though we can waste hotplug memory.
> 
> Changes from v2:
> * Rebase to latest linus tree
> * Redo the series based on review feedback. Multiple changes to the patchset.
> 
> Changes from v1:
> * update the memblock to store vmemmap_altmap details. This is required
> so that when we remove the memory we can find the altmap details which
> is needed on some architectures.
> * rebase to latest linus tree
> 
> 
> 
> Aneesh Kumar K.V (7):
>    mm/hotplug: Simplify ARCH_MHP_MEMMAP_ON_MEMORY_ENABLE kconfig
>    mm/hotplug: Allow memmap on memory hotplug request to fallback
>    mm/hotplug: Allow architecture to override memmap on memory support
>      check
>    mm/hotplug: Support memmap_on_memory when memmap is not aligned to
>      pageblocks
>    powerpc/book3s64/memhotplug: Enable memmap on memory for radix
>    mm/hotplug: Embed vmem_altmap details in memory block
>    mm/hotplug: Enable runtime update of memmap_on_memory parameter

Nit for all patches: we use "mm/memory_hotplug" as prefix. (I somehow 
missed that earlier :D )

-- 
Cheers,

David / dhildenb