[Zesty][PATCH 0/6] Allow memory-hotplug with 16G hugepages

[Kleber Souza]

On 10/26/17 14:52, Kleber Souza wrote:
> On 10/17/17 12:52, Victor Aoqui wrote:
>> BugLink: http://bugs.launchpad.net/bugs/1724120
>>
>> These patches are required to allow memory-hotplug with 16G hugepages 
>>
>> Aneesh Kumar K.V (6):
>>   powerpc/mm/hugetlb: Filter out hugepage size not supported by page
>>     table layout
>>   mm/hugetlb: clean up ARCH_HAS_GIGANTIC_PAGE
>>   powerpc/mm/hugetlb: add support for 1G huge pages
>>   mm/hugetlb: Allow arch to override and call the weak function
>>   powerpc/mm/hugetlb: Add support for reserving gigantic huge pages via
>>     kernel command line
>>   powerpc/mm/hugetlb: Allow runtime allocation of 16G.
>>
>>  arch/arm64/Kconfig                            |   2 +-
>>  arch/arm64/include/asm/hugetlb.h              |   4 +
>>  arch/powerpc/include/asm/book3s/64/hugetlb.h  |   8 ++
>>  arch/powerpc/include/asm/book3s/64/mmu-hash.h |   2 +-
>>  arch/powerpc/include/asm/hugetlb.h            |  14 --
>>  arch/powerpc/kernel/setup-common.c            |   7 -
>>  arch/powerpc/mm/hash_utils_64.c               |   2 +-
>>  arch/powerpc/mm/hugetlbpage.c                 | 198 ++++++--------------------
>>  arch/powerpc/mm/init_32.c                     |   2 -
>>  arch/powerpc/platforms/Kconfig.cputype        |   1 +
>>  arch/s390/Kconfig                             |   2 +-
>>  arch/s390/include/asm/hugetlb.h               |   3 +
>>  arch/x86/Kconfig                              |   2 +-
>>  arch/x86/include/asm/hugetlb.h                |   4 +
>>  include/linux/hugetlb.h                       |   1 +
>>  mm/hugetlb.c                                  |  11 +-
>>  16 files changed, 72 insertions(+), 191 deletions(-)
>>
> 
> Hi,
> 
> These patches also touch code that can have an impact on other
> architectures. Could you please elaborate on the regression potential of
> these patches and if they have been tested with other architectures?
> Please add this information also to the Lauchpad bug.
> 

Additionally, could you please also format the bug text to follow the
SRU guidelines? That would mean having the report formatted as the
following template:


[SRU Justification]

Impact: <what wrong now>

Fix: <refer to patches, where do those come from>

Testcase: <if possible how can the fix be checked quickly>

Regression Risk: <how likely / how much impact>


Thank you,
Kleber