Re: [PATCH] x86: fix the initialization of physnode_map

2014-02-01 Thread Dave Hansen
On 02/01/2014 04:13 AM, Petr Tesarik wrote: >> > Just curious, but >> > what the heck kind of 32-bit NUMA hardware is still in the wild? Did >> > someon buy a NUMA-Q on eBay? :) > In fact, this is a patch that has been floating around in SUSE > Enterprise kernels for some time. It was originally a

Re: [PATCH] x86: fix the initialization of physnode_map

2014-02-01 Thread Petr Tesarik
On Fri, 31 Jan 2014 13:14:29 -0800 Dave Hansen wrote: > On 01/31/2014 02:05 AM, Petr Tesarik wrote: > > With DISCONTIGMEM, the mapping between a pfn and its owning node is > > initialized using data provided by the BIOS or from the command line. > > However, the initialization may fail if the ext

Re: [PATCH] x86: fix the initialization of physnode_map

2014-01-31 Thread Dave Hansen
On 01/31/2014 02:05 AM, Petr Tesarik wrote: > With DISCONTIGMEM, the mapping between a pfn and its owning node is > initialized using data provided by the BIOS or from the command line. > However, the initialization may fail if the extents are not aligned > to section boundary (64M). So is this a

Re: [PATCH] x86: fix the initialization of physnode_map

2014-01-31 Thread David Rientjes
On Fri, 31 Jan 2014, Petr Tesarik wrote: > With DISCONTIGMEM, the mapping between a pfn and its owning node is > initialized using data provided by the BIOS or from the command line. > However, the initialization may fail if the extents are not aligned > to section boundary (64M). > > The symptom

[PATCH] x86: fix the initialization of physnode_map

2014-01-31 Thread Petr Tesarik
With DISCONTIGMEM, the mapping between a pfn and its owning node is initialized using data provided by the BIOS or from the command line. However, the initialization may fail if the extents are not aligned to section boundary (64M). The symptom of this bug is an early boot failure in pfn_to_page()