Can't post this part yet because it uses things in an upcoming[*] ACPI, UEFI,
or some
other four-letter-ending-in-I standard. So just imagine a call someplace early
in startup that reads information about mirrored address ranges and does:
+ for (...) {
+ start = ...;
+ size = ...;
+ if (it looks mirrored)
+ memblock_mark_mirror(start, size);
+ }
Whole patch is pretty tiny:
3 files changed, 19 insertions(+)
How much damage could I possibly do in just 19 lines?
-Tony
[*] very soon, I'm told
--
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/
