From: Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>
To: Lin-bao Zhang <zhang.linbao@yahoo.com>
Cc: "xen-devel@lists.xensource.com" <xen-devel@lists.xensource.com>
Subject: Re: difference between xen hypervisor and common kernel on handling BIOS's e820 map ?
Date: Tue, 30 Aug 2011 10:00:31 -0400 [thread overview]
Message-ID: <20110830140030.GG11346@dumpdata.com> (raw)
In-Reply-To: <1314681899.56694.YahooMailNeo@web122110.mail.ne1.yahoo.com>
On Mon, Aug 29, 2011 at 10:24:59PM -0700, Lin-bao Zhang wrote:
> in a same , I have xen-kernel and common kernel installed ,
> in grub.conf , just like this:
>
> title Red Hat Enterprise Linux Server (2.6.18-268.el5xen)
> root (hd0,0)
> kernel /boot/xen.gz-2.6.18-268.el5 loglvl=all guest_loglvl=all sync_console console_to_ring com1=115200,8n1 console=com1
> module /boot/vmlinuz-2.6.18-268.el5xen ro root=LABEL=/1 console=hvc0 earlyprintk=xen nomodeset
You don't need nomodeset on '2.6.18' kernels.
> module /boot/initrd-2.6.18-268.el5xen.img
>
> title Red Hat Enterprise Linux Server (2.6.18-268.el5)
> root (hd0,0)
> kernel /boot/vmlinuz-2.6.18-268.el5 ro root=LABEL=/1 console=tty0 console=ttyS0,115200
> initrd /boot/initrd-2.6.18-268.el5.img
>
> --------------
> but I found difference about e820map from the two kernels :
>
> common kernel: --------------------------------
> BIOS-provided physical RAM map:
> BIOS-e820: 0000000000010000 - 0000000000090400 (usable)
> BIOS-e820: 0000000000090400 - 0000000000a0000 (reserved)
> BIOS-e820: 00000000000f0000 - 0000000000100000 (reserved)
> BIOS-e820: 0000000000100000 - 000000007f5f0000 (usable)
> BIOS-e820: 000000007f5f0000 - 000000007f62c000 (ACPI data)
> BIOS-e820: 000000007f62c000 - 000000007f62d000 (usable)
> BIOS-e82: 000000007f62d000 - 00000000779d000 (reserved)
> BIOS-e820: 0000000779d000 - 000000007f7a0000 (ACPI data)
> BIOS-e0: 00000007f7a0000 - 0000000090000000 (reserved)
> BIOS-e820: 00000000fec00000 - 00000000fee10000 (reserved)
> BIOS-e820: 00000000ff800000 - 0000000100000000 (eservd)
> BIOS-e820: 0000000100000000 -0000000480000000 (usable)
> BIOS-e820: 0000002000000000 - 0000002400000000 (usable)
> BIOS-e820: 0000004000000000 - 0000004400000000 (usable)
> BIOS-e820: 0000006000000000 - 00000600000000 (usable)
>
> xen-kernel:
> Xen-e820 RAM map:
> (XEN) 0000000000000000 - 0000000000090400 (usable)
> (XEN) 0000000000090400 - 00000000000a0000 (reserved)
> (XEN) 00000000000f0000 - 0000000000100000 (reserved)
> (XEN) 0000000000100000 - 000000007f5f0000 (usable)
> (XEN) 000000007f5f0000 - 000000007f62c000 (ACPI data)
> (XEN) 000000007f62c000 - 000000007f62d000 (usable)
> (XEN) 000000007f62d000 - 000000007f79d000 (reserved)
> (XEN) 000000007f79d000 - 000000007f7a0000 (ACPI data)
> (XEN) 000000007f7a0000 - 0000000090000000 (reserved)
> (XEN) 00000000fec00000 - 00000000fee10000 (reserved)
> (XEN) 00000000ff800000 - 0000000100000000 (reserved)
> (XEN) 0000000100000000 - 0000000480000000 (usable)
> (XEN) 0000002000000000 - 0000002400000000 (usable)
> (XEN) 0000004000000000 - 0000004400000000 (usable)
> (XEN) 0000006000000000 - 0000006400000000 (usable)
> (XEN) System RAM: 65525MB (67098116kB)
>
> I diff them in a picture :
Huh? Can you just do a diff of the two texts or just
do <=== on the email to point to it?
>
>
> as my existing knowledge , e820 map information is provided by BIOS ,it should be same for all OS(windows and linux) , OS just use it .
> but why xen-kernel's e820 map is different from that of common-kernel.
>
> _______________________________________________
> Xen-devel mailing list
> Xen-devel@lists.xensource.com
> http://lists.xensource.com/xen-devel
next prev parent reply other threads:[~2011-08-30 14:00 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-08-30 5:24 difference between xen hypervisor and common kernel on handling BIOS's e820 map ? Lin-bao Zhang
2011-08-30 7:44 ` Lin-bao Zhang
2011-08-30 14:00 ` Konrad Rzeszutek Wilk [this message]
2011-08-30 15:30 ` Lin-bao Zhang
2011-08-30 16:10 ` Konrad Rzeszutek Wilk
2011-08-31 7:44 ` Lin-bao Zhang
2011-08-31 7:54 ` Keir Fraser
2011-09-01 8:02 ` Ian Campbell
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=20110830140030.GG11346@dumpdata.com \
--to=konrad.wilk@oracle.com \
--cc=xen-devel@lists.xensource.com \
--cc=zhang.linbao@yahoo.com \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.