RE: [PATCH v2 0/2] mm: Introduce kernelcore=reliable option

2015-12-08 Thread Izumi, Taku
Dear Tony, > > Which do you think is beter ? > >- change into kernelcore="mirrored" > >- keep kernelcore="reliable" and minmal printk fix > > UEFI came up with the "reliable" wording (as a more generic term ... > as Andrew said > it could cover differences in ECC modes, or some alternat

Re: [PATCH v2 0/2] mm: Introduce kernelcore=reliable option

2015-12-08 Thread Tony Luck
On Tue, Dec 8, 2015 at 12:07 AM, Izumi, Taku wrote: > Which do you think is beter ? >- change into kernelcore="mirrored" >- keep kernelcore="reliable" and minmal printk fix UEFI came up with the "reliable" wording (as a more generic term ... as Andrew said it could cover differences in E

RE: [PATCH v2 0/2] mm: Introduce kernelcore=reliable option

2015-12-08 Thread Izumi, Taku
Dear Tony, Thanks for testing! Dear Andrew, > > Xeon E7 v3 based systems supports Address Range Mirroring > > and UEFI BIOS complied with UEFI spec 2.5 can notify which > > ranges are reliable (mirrored) via EFI memory map. > > Now Linux kernel utilize its information and allocates > > boot t

Re: [PATCH v2 0/2] mm: Introduce kernelcore=reliable option

2015-12-07 Thread Andrew Morton
On Sat, 28 Nov 2015 00:03:55 +0900 Taku Izumi wrote: > Xeon E7 v3 based systems supports Address Range Mirroring > and UEFI BIOS complied with UEFI spec 2.5 can notify which > ranges are reliable (mirrored) via EFI memory map. > Now Linux kernel utilize its information and allocates > boot time m

Re: [PATCH v2 0/2] mm: Introduce kernelcore=reliable option

2015-12-07 Thread Tony Luck
Sorry for the slow turnaround testing this. This version seems to do better with my quirky system. Summary of /proc/zoneinfo now looks like this: $ ./zoneinfo Node Normal Movable DMA DMA32 017090.0485687.43 14.93 1677.41

[PATCH v2 0/2] mm: Introduce kernelcore=reliable option

2015-11-26 Thread Taku Izumi
Xeon E7 v3 based systems supports Address Range Mirroring and UEFI BIOS complied with UEFI spec 2.5 can notify which ranges are reliable (mirrored) via EFI memory map. Now Linux kernel utilize its information and allocates boot time memory from reliable region. My requirement is: - allocate kern