Re: [RFC][PATCH] x86: nit: wrong page size in init_memory_mapping() printks

2015-02-11 Thread Borislav Petkov
On Tue, Feb 10, 2015 at 01:20:30PM -0800, Dave Hansen wrote: > > From: Dave Hansen > > With 32-bit non-PAE kernels, we have 2 page sizes available > (at most): 4k and 4M. > > Enabling PAE replaces that 4M size with a 2M one (which 64-bit > systems use too). > > But, when booting a 32-bit

Re: [RFC][PATCH] x86: nit: wrong page size in init_memory_mapping() printks

2015-02-11 Thread Borislav Petkov
On Tue, Feb 10, 2015 at 01:20:30PM -0800, Dave Hansen wrote: From: Dave Hansen dave.han...@linux.intel.com With 32-bit non-PAE kernels, we have 2 page sizes available (at most): 4k and 4M. Enabling PAE replaces that 4M size with a 2M one (which 64-bit systems use too). But, when

[RFC][PATCH] x86: nit: wrong page size in init_memory_mapping() printks

2015-02-10 Thread Dave Hansen
From: Dave Hansen With 32-bit non-PAE kernels, we have 2 page sizes available (at most): 4k and 4M. Enabling PAE replaces that 4M size with a 2M one (which 64-bit systems use too). But, when booting a 32-bit non-PAE kernel, in one of our early-boot printouts, we say: [0.00]

[RFC][PATCH] x86: nit: wrong page size in init_memory_mapping() printks

2015-02-10 Thread Dave Hansen
From: Dave Hansen dave.han...@linux.intel.com With 32-bit non-PAE kernels, we have 2 page sizes available (at most): 4k and 4M. Enabling PAE replaces that 4M size with a 2M one (which 64-bit systems use too). But, when booting a 32-bit non-PAE kernel, in one of our early-boot printouts, we