Re: [PATCH] x86: tidy e820 output

From: H. Peter Anvin
Date: Wed Sep 22 2010 - 14:28:29 EST


On 09/22/2010 11:20 AM, Bjorn Helgaas wrote:
>
> These E820 ranges should be easily comparable with similar ranges we
> print elsewhere. Currently we have things like this:
>
> BIOS-e820: 0000000000000000 - 000000000009f400 (usable)
> BIOS-e820: 000000000009f400 - 00000000000a0000 (reserved)
> BIOS-e820: 00000000fffbc000 - 0000000100000000 (reserved)
> pci_root PNP0A03:00: host bridge window [mem 0x000a0000-0x000bffff]
> pci_root PNP0A03:00: host bridge window [mem 0xe0000000-0xfebfffff]
> pci 0000:00:02.0: reg 10: [mem 0xf0000000-0xf1ffffff pref]
> reserve RAM buffer: 000000000009f400 - 000000000009ffff
> pnp 00:07: [mem 0xfed00000-0xfed003ff]
>
> It would be easier to integrate the E820 information with the ACPI
> and PCI window and BAR information if they looked similar.
>
> We currently have a mix of some with "0x" prefix, some without;
> some with eight hex digits, some with sixteen; some with spaces
> around the internal "-", some without; some with type (io/mem/etc),
> some without; some with uppercase hex (MTRR), most with lowercase;
> some including the end address, some not; and even some in PFNs
> and most in addresses. It just makes it harder than it needs
> to be to debug issues in this area.
>

Yes, but I think you can also see why I really don't like the thought of
the numbers in the BIOS-e820: block not even lining up anymore.

-hpa

--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/