Re: [PATCH 3/4] xen: more debugging in the e820 parsing

[Stefano Stabellini]

On Tue, 12 Apr 2011, Konrad Rzeszutek Wilk wrote:
> On Tue, Apr 12, 2011 at 12:19:51PM +0100, stefano.stabellini@xxxxxxxxxxxxx wrote:
> > From: Stefano Stabellini <stefano.stabellini@xxxxxxxxxxxxx>
> > 
> > Signed-off-by: Stefano Stabellini <stefano.stabellini@xxxxxxxxxxxxx>
> 
> I am not entirely sure if we need these. You get all of this data by looking
> at the Xen E820 and the guest E820 (to see the xen_extra_mem):
> 
> (XEN) Xen-e820 RAM map:
> (XEN)  0000000000000000 - 000000000009f800 (usable)
> (XEN)  000000000009f800 - 00000000000a0000 (reserved)
> (XEN)  00000000000f0000 - 0000000000100000 (reserved)
> (XEN)  0000000000100000 - 00000000cf5e0000 (usable)
> (XEN)  00000000cf5e0000 - 00000000cf5e3000 (ACPI NVS)
> (XEN)  00000000cf5e3000 - 00000000cf5f0000 (ACPI data)
> (XEN)  00000000cf5f0000 - 00000000cf600000 (reserved)
> (XEN)  00000000e0000000 - 00000000f0000000 (reserved)
> (XEN)  00000000fec00000 - 0000000100000000 (reserved)
> (XEN)  0000000100000000 - 0000000130000000 (usable)
> ..
> 
> [    0.000000] BIOS-provided physical RAM map:
> .. snip..
> [    0.000000]  Xen: 0000000100000000 - 00000001a19e0000 (usable)
> 
> And your patch adds this:
> 
> [    0.000000] e820_region: type=1 start=0000000000000000 end=000000000009f800
> [    0.000000] e820_region: type=2 start=000000000009f800 end=00000000000a0000
> [    0.000000] e820_region: type=2 start=00000000000f0000 end=0000000000100000
> [    0.000000] e820_region: type=1 start=0000000000100000 end=00000000cf5e0000
> [    0.000000] e820_region: type=4 start=00000000cf5e0000 end=00000000cf5e3000
> [    0.000000] e820_region: type=3 start=00000000cf5e3000 end=00000000cf5f0000
> [    0.000000] e820_region: type=2 start=00000000cf5f0000 end=00000000cf600000
> [    0.000000] e820_region: type=2 start=00000000e0000000 end=00000000f0000000
> [    0.000000] e820_region: type=2 start=00000000fec00000 end=0000000100000000
> [    0.000000] e820_region: type=1 start=0000000100000000 end=0000000130000000
> [    0.000000] released 0 pages of unused memory
> [    0.000000] extra e820 region: start=0000000100000000 end=00000001a19e0000

I have a machine here in which the e820 printed by Xen and the e820
in dom0 *before* any modifications differs:

(XEN) Xen-e820 RAM map:
(XEN)  0000000000000000 - 000000000009fc00 (usable)
(XEN)  000000000009fc00 - 00000000000a0000 (reserved)
(XEN)  00000000000e0000 - 0000000000100000 (reserved)
(XEN)  0000000000100000 - 00000000beb96000 (usable)
(XEN)  00000000beb96000 - 00000000bed97000 (ACPI NVS)
(XEN)  00000000bed97000 - 00000000bf651000 (usable)
(XEN)  00000000bf651000 - 00000000bf6e9000 (ACPI NVS)
(XEN)  00000000bf6e9000 - 00000000bf6ec000 (usable)
(XEN)  00000000bf6ec000 - 00000000bf6ff000 (ACPI data)
(XEN)  00000000bf6ff000 - 00000000bf700000 (usable)

[    0.000000] e820_region: type=1 start=0000000000000000 end=000000000009fc00
[    0.000000] e820_region: type=2 start=000000000009fc00 end=00000000000a0000
[    0.000000] e820_region: type=2 start=00000000000e0000 end=0000000000100000
[    0.000000] e820_region: type=1 start=0000000000100000 end=00000000beb96000
[    0.000000] e820_region: type=4 start=00000000beb96000 end=00000000bed97000
[    0.000000] e820_region: type=1 start=00000000bed97000 end=00000000bf651000
[    0.000000] e820_region: type=4 start=00000000bf651000 end=00000000bf6e9000
[    0.000000] e820_region: type=1 start=00000000bf6e9000 end=00000000bf6ec000
[    0.000000] e820_region: type=3 start=00000000bf6ec000 end=00000000bf6ff000
[    0.000000] e820_region: type=1 start=00000000bf6ff000 end=00000000bf700000
[    0.000000] e820_region: type=2 start=00000000fec00000 end=00000000fec01000
[    0.000000] e820_region: type=2 start=00000000fee00000 end=00000000fee01000
--
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/