On Wed, 03 Sep, at 03:01:31PM, Ard Biesheuvel wrote: > > Tested-by: Ard Biesheuvel <ard.biesheuvel@xxxxxxxxxx> > (on arm64 only) > > +1 for aligning between architectures > +1 for cleaning up the output to make it more readable Thanks Ard. > The only thing I am not entirely convinced about is printing all those > memory attributes: is it really so interesting to know that region X > /can/ be configured as writeback, write through, write combining etc > etc, as most regions seem to support most attributes, yet it tells you > nothing about what the kernel ends up doing with that information. In > the arm64 case, for instance, all MEMORY_WB ranges are mapped > writeback cached, and everything else is mapped uncached. Personally, I think it's good to get an unadulterated version of the firmware memory map (for vicarious debugging) before the kernel has a chance to mess with it. -- Matt Fleming, Intel Open Source Technology Center -- To unsubscribe from this list: send the line "unsubscribe linux-efi" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
