On 2015/10/9 18:36, Xishi Qiu wrote: > On 2015/10/9 17:24, Kamezawa Hiroyuki wrote: > >> On 2015/10/09 15:46, Xishi Qiu wrote: >>> On 2015/10/9 22:56, 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 memory from reliable region. >>>> >>>> My requirement is: >>>> - allocate kernel memory from reliable region >>>> - allocate user memory from non-reliable region >>>> >>>> In order to meet my requirement, ZONE_MOVABLE is useful. >>>> By arranging non-reliable range into ZONE_MOVABLE, >>>> reliable memory is only used for kernel allocations. >>>>
Hi, If we reuse the movable zone, we should set appropriate size of mirrored memory region(normal zone) and non-mirrored memory region(movable zone). In some cases, kernel will take more memory than user, e.g. some apps run in kernel space, like module. I think user can set the size in BIOS interface, right? Thanks, Xishi Qiu -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
