Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S932871Ab1DNKfy (ORCPT ); Thu, 14 Apr 2011 06:35:54 -0400 Received: from smtp.eu.citrix.com ([62.200.22.115]:27271 "EHLO SMTP.EU.CITRIX.COM" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1758701Ab1DNKfx (ORCPT ); Thu, 14 Apr 2011 06:35:53 -0400 X-IronPort-AV: E=Sophos;i="4.64,210,1301875200"; d="scan'208";a="5300411" Date: Thu, 14 Apr 2011 11:35:28 +0100 From: Stefano Stabellini X-X-Sender: sstabellini@kaball-desktop To: Konrad Rzeszutek Wilk CC: Stefano Stabellini , "linux-kernel@vger.kernel.org" , "xen-devel@lists.xensource.com" , "jeremy@goop.org" , "yinghai@kernel.org" , "hpa@linux.intel.com" , "mingo@elte.hu" Subject: Re: [PATCH 3/4] xen: more debugging in the e820 parsing In-Reply-To: <20110413175404.GA19390@dumpdata.com> Message-ID: References: <1302607192-21355-3-git-send-email-stefano.stabellini@eu.citrix.com> <20110412163957.GA1067@dumpdata.com> <20110413175404.GA19390@dumpdata.com> User-Agent: Alpine 2.00 (DEB 1167 2008-08-23) MIME-Version: 1.0 Content-Type: text/plain; charset="US-ASCII" Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 2670 Lines: 47 On Wed, 13 Apr 2011, Konrad Rzeszutek Wilk wrote: > > 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 > > Ah, so the IOAPIC regions don't show up in the E820. Do they show up in the > E820 printed by the Linux kernel? If I use the Xen E820 output and what the > guest prints for its E820 I seem to get even this "hidden" area. Yes, that's right. However it might be confusing if you are trying to debug the transformations made by xen/setup.c to the e820... In any case I don't feel strongly about this, it is just that I found myself adding these printk's more than once so I thought that it might be good to have them in any case for debugging. On the other hand I add printk's all the time so surely it won't kill me to add these ones too. -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/