Re: [PATCH 2/2] mm/memory_hotplug: define find_{smallest|biggest}_section_pfn as unsigned long

2017-09-18 Thread Michal Hocko
On Fri 15-09-17 22:53:49, YASUAKI ISHIMATSU wrote: > find_{smallest|biggest}_section_pfn()s find the smallest/biggest section > and return the pfn of the section. But the functions are defined as int. > So the functions always return 0x - 0x. It means > if memory address is over

Re: [PATCH 2/2] mm/memory_hotplug: define find_{smallest|biggest}_section_pfn as unsigned long

2017-09-18 Thread Michal Hocko
On Fri 15-09-17 22:53:49, YASUAKI ISHIMATSU wrote: > find_{smallest|biggest}_section_pfn()s find the smallest/biggest section > and return the pfn of the section. But the functions are defined as int. > So the functions always return 0x - 0x. It means > if memory address is over

[PATCH 2/2] mm/memory_hotplug: define find_{smallest|biggest}_section_pfn as unsigned long

2017-09-15 Thread YASUAKI ISHIMATSU
find_{smallest|biggest}_section_pfn()s find the smallest/biggest section and return the pfn of the section. But the functions are defined as int. So the functions always return 0x - 0x. It means if memory address is over 16TB, the functions does not work correctly. To handle 64

[PATCH 2/2] mm/memory_hotplug: define find_{smallest|biggest}_section_pfn as unsigned long

2017-09-15 Thread YASUAKI ISHIMATSU
find_{smallest|biggest}_section_pfn()s find the smallest/biggest section and return the pfn of the section. But the functions are defined as int. So the functions always return 0x - 0x. It means if memory address is over 16TB, the functions does not work correctly. To handle 64