From: Stefano Stabellini <stefano.stabellini@eu.citrix.com>
To: Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>
Cc: Stefano Stabellini <Stefano.Stabellini@eu.citrix.com>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"xen-devel@lists.xensource.com" <xen-devel@lists.xensource.com>,
"jeremy@goop.org" <jeremy@goop.org>,
"yinghai@kernel.org" <yinghai@kernel.org>,
"hpa@linux.intel.com" <hpa@linux.intel.com>,
"mingo@elte.hu" <mingo@elte.hu>
Subject: Re: [PATCH 3/4] xen: more debugging in the e820 parsing
Date: Wed, 13 Apr 2011 11:24:23 +0100 [thread overview]
Message-ID: <alpine.DEB.2.00.1104131118180.22672@kaball-desktop> (raw)
In-Reply-To: <20110412163957.GA1067@dumpdata.com>
On Tue, 12 Apr 2011, Konrad Rzeszutek Wilk wrote:
> On Tue, Apr 12, 2011 at 12:19:51PM +0100, stefano.stabellini@eu.citrix.com wrote:
> > From: Stefano Stabellini <stefano.stabellini@eu.citrix.com>
> >
> > Signed-off-by: Stefano Stabellini <stefano.stabellini@eu.citrix.com>
>
> 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
next prev parent reply other threads:[~2011-04-13 10:24 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-04-12 11:16 [PATCH 0/4] xen: critical bug fixes for 2.6.39-rc3 Stefano Stabellini
2011-04-12 11:19 ` [PATCH 1/4] xen: mask_rw_pte mark RO all pagetable pages up to pgt_buf_top stefano.stabellini
2011-04-12 16:47 ` Konrad Rzeszutek Wilk
2011-04-13 10:24 ` Stefano Stabellini
2011-04-12 11:19 ` [PATCH 2/4] x86,xen: introduce x86_init.mapping.pagetable_reserve stefano.stabellini
2011-04-12 11:50 ` [Xen-devel] [PATCH 2/4] x86, xen: " Jan Beulich
2011-04-12 17:41 ` Stefano Stabellini
2011-04-12 17:40 ` [PATCH 2/4] x86,xen: " Yinghai Lu
2011-04-13 10:35 ` Stefano Stabellini
2011-04-13 18:28 ` H. Peter Anvin
2011-04-14 11:05 ` Stefano Stabellini
2011-04-13 18:03 ` Konrad Rzeszutek Wilk
2011-04-13 18:35 ` H. Peter Anvin
2011-04-13 20:19 ` Konrad Rzeszutek Wilk
2011-04-13 18:26 ` H. Peter Anvin
2011-04-14 11:30 ` Stefano Stabellini
2011-04-14 14:49 ` Stefano Stabellini
2011-04-14 14:52 ` H. Peter Anvin
2011-04-14 18:09 ` Stefano Stabellini
2011-04-18 14:09 ` Stefano Stabellini
2011-04-18 14:42 ` H. Peter Anvin
2011-04-18 17:21 ` Stefano Stabellini
2011-04-20 16:50 ` Jeremy Fitzhardinge
2011-04-12 11:19 ` [PATCH 3/4] xen: more debugging in the e820 parsing stefano.stabellini
2011-04-12 16:39 ` Konrad Rzeszutek Wilk
2011-04-13 10:24 ` Stefano Stabellini [this message]
2011-04-13 17:54 ` Konrad Rzeszutek Wilk
2011-04-14 10:35 ` Stefano Stabellini
2011-04-12 11:19 ` [PATCH 4/4] xen: do not create the extra e820 region at an addr lower than 4G stefano.stabellini
2011-04-12 16:48 ` Konrad Rzeszutek Wilk
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=alpine.DEB.2.00.1104131118180.22672@kaball-desktop \
--to=stefano.stabellini@eu.citrix.com \
--cc=hpa@linux.intel.com \
--cc=jeremy@goop.org \
--cc=konrad.wilk@oracle.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=xen-devel@lists.xensource.com \
--cc=yinghai@kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®