From mboxrd@z Thu Jan 1 00:00:00 1970 From: Konrad Rzeszutek Wilk Subject: Re: difference between xen hypervisor and common kernel on handling BIOS's e820 map ? Date: Tue, 30 Aug 2011 10:00:31 -0400 Message-ID: <20110830140030.GG11346@dumpdata.com> References: <1314681899.56694.YahooMailNeo@web122110.mail.ne1.yahoo.com> Mime-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: quoted-printable Return-path: Content-Disposition: inline In-Reply-To: <1314681899.56694.YahooMailNeo@web122110.mail.ne1.yahoo.com> List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: xen-devel-bounces@lists.xensource.com Errors-To: xen-devel-bounces@lists.xensource.com To: Lin-bao Zhang Cc: "xen-devel@lists.xensource.com" List-Id: xen-devel@lists.xenproject.org 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: >=20 > title Red Hat Enterprise Linux Server (2.6.18-268.el5xen) > root (hd0,0) > kernel /boot/xen.gz-2.6.18-268.el5 =A0loglvl=3Dall guest_loglvl=3Dall s= ync_console console_to_ring com1=3D115200,8n1 console=3Dcom1 > module /boot/vmlinuz-2.6.18-268.el5xen ro root=3DLABEL=3D/1 console=3Dh= vc0 earlyprintk=3Dxen nomodeset You don't need nomodeset on '2.6.18' kernels. > module /boot/initrd-2.6.18-268.el5xen.img >=20 > title Red Hat Enterprise Linux Server (2.6.18-268.el5) > =A0 =A0 =A0 =A0 root (hd0,0) > =A0 =A0 =A0 =A0 kernel /boot/vmlinuz-2.6.18-268.el5 ro root=3DLABEL=3D/= 1 console=3Dtty0 console=3DttyS0,115200 > =A0 =A0 =A0 =A0 initrd /boot/initrd-2.6.18-268.el5.img >=20 > -------------- > but I found difference about e820map from the two kernels : >=20 > common kernel: -------------------------------- > BIOS-provided physical RAM map: > =A0BIOS-e820: 0000000000010000 - 0000000000090400 (usable) > =A0BIOS-e820: 0000000000090400 - 0000000000a0000 (reserved) > =A0BIOS-e820: 00000000000f0000 - 0000000000100000 (reserved) > =A0BIOS-e820: 0000000000100000 - 000000007f5f0000 (usable) > =A0BIOS-e820: 000000007f5f0000 - 000000007f62c000 (ACPI data) > =A0BIOS-e820: 000000007f62c000 - 000000007f62d000 (usable) > =A0BIOS-e82: 000000007f62d000 - 00000000779d000 (reserved) > =A0BIOS-e820: 0000000779d000 - 000000007f7a0000 (ACPI data) > =A0BIOS-e0: 00000007f7a0000 - 0000000090000000 (reserved) > =A0BIOS-e820: 00000000fec00000 - 00000000fee10000 (reserved) > =A0BIOS-e820: 00000000ff800000 - 0000000100000000 (eservd) > =A0BIOS-e820: 0000000100000000 -0000000480000000 (usable) > =A0BIOS-e820: 0000002000000000 - 0000002400000000 (usable) > =A0BIOS-e820: 0000004000000000 - 0000004400000000 (usable) > =A0BIOS-e820: 0000006000000000 - 00000600000000 (usable) >=20 > xen-kernel: > =A0Xen-e820 RAM map: > (XEN) =A00000000000000000 - 0000000000090400 (usable) > (XEN) =A00000000000090400 - 00000000000a0000 (reserved) > (XEN) =A000000000000f0000 - 0000000000100000 (reserved) > (XEN) =A00000000000100000 - 000000007f5f0000 (usable) > (XEN) =A0000000007f5f0000 - 000000007f62c000 (ACPI data) > (XEN) =A0000000007f62c000 - 000000007f62d000 (usable) > (XEN) =A0000000007f62d000 - 000000007f79d000 (reserved) > (XEN) =A0000000007f79d000 - 000000007f7a0000 (ACPI data) > (XEN) =A0000000007f7a0000 - 0000000090000000 (reserved) > (XEN) =A000000000fec00000 - 00000000fee10000 (reserved) > (XEN) =A000000000ff800000 - 0000000100000000 (reserved) > (XEN) =A00000000100000000 - 0000000480000000 (usable) > (XEN) =A00000002000000000 - 0000002400000000 (usable) > (XEN) =A00000004000000000 - 0000004400000000 (usable) > (XEN) =A00000006000000000 - 0000006400000000 (usable) =A0 =A0 =A0 > (XEN) System RAM: 65525MB (67098116kB) >=20 > I diff them in a picture : Huh? Can you just do a diff of the two texts or just do <=3D=3D=3D on the email to point to it? >=20 >=20 > 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 .=A0 > but why xen-kernel's e820 map is different from that of common-kernel. >=20 > _______________________________________________ > Xen-devel mailing list > Xen-devel@lists.xensource.com > http://lists.xensource.com/xen-devel