On Wed, 9 Dec 2015 12:19:37 +0900 Taku Izumi <izumi.taku@xxxxxxxxxxxxxx> wrote: > This patch extends existing "kernelcore" option and > introduces kernelcore=mirror option. By specifying > "mirror" instead of specifying the amount of memory, > non-mirrored (non-reliable) region will be arranged > into ZONE_MOVABLE. > > v1 -> v2: > - Refine so that the following case also can be > handled properly: > > Node X: |MMMMMM------MMMMMM--------| > (legend) M: mirrored -: not mirrrored > > In this case, ZONE_NORMAL and ZONE_MOVABLE are > arranged like bellow: > > Node X: |MMMMMM------MMMMMM--------| > |ooooooxxxxxxooooooxxxxxxxx| ZONE_NORMAL > |ooooooxxxxxxoooooooo| ZONE_MOVABLE > (legend) o: present x: absent > > v2 -> v3: > - change the option name from kernelcore=reliable > into kernelcore=mirror > - documentation fix so that users can understand > nn[KMS] and mirror are exclusive My earlier concern with this approach is the assumption that *all* of the mirrored memory will be used to kernelcore. The user might want to use half the machine's mirrored memory for kernelcore and half for regular memory but cannot do so. However I think what I'm seeing from the discussion is that in this case, the user can alter the amount of mirrored memory via EFI to achieve the same effect. Is this correct? If so, should we document this somewhere and provide our users with instructions on how to make the required EFI changes? Or is this all so totally obvious to them that there is no need? -- To unsubscribe, send a message with 'unsubscribe linux-mm' in the body to majordomo@xxxxxxxxx. For more info on Linux MM, see: http://www.linux-mm.org/ . Don't email: <a href=mailto:"dont@xxxxxxxxx";> email@xxxxxxxxx </a>