From mboxrd@z Thu Jan  1 00:00:00 1970
From: =?ISO-8859-1?Q?Roger_Pau_Monn=E9?= <roger.pau@citrix.com>
Subject: Re: [V10 PATCH 0/4] pvh dom0 patches...
Date: Fri, 2 May 2014 16:06:26 +0200
Message-ID: <5363A662.30407@citrix.com>
References: <1398820008-9005-1-git-send-email-mukesh.rathor@oracle.com>
	<5361049B.7040409@citrix.com>
	<20140430111216.2bef8e60@mantra.us.oracle.com>
	<20140430181923.68d75467@mantra.us.oracle.com>
	<53637BF3.2000502@citrix.com>
	<5363AC29020000780000E784@mail.emea.novell.com>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Return-path: <xen-devel-bounces@lists.xen.org>
Received: from mail6.bemta3.messagelabs.com ([195.245.230.39])
	by lists.xen.org with esmtp (Exim 4.72)
	(envelope-from <roger.pau@citrix.com>) id 1WgE6j-0004MF-RD
	for xen-devel@lists.xenproject.org; Fri, 02 May 2014 14:06:34 +0000
In-Reply-To: <5363AC29020000780000E784@mail.emea.novell.com>
List-Unsubscribe: <http://lists.xen.org/cgi-bin/mailman/options/xen-devel>,
	<mailto:xen-devel-request@lists.xen.org?subject=unsubscribe>
List-Post: <mailto:xen-devel@lists.xen.org>
List-Help: <mailto:xen-devel-request@lists.xen.org?subject=help>
List-Subscribe: <http://lists.xen.org/cgi-bin/mailman/listinfo/xen-devel>,
	<mailto:xen-devel-request@lists.xen.org?subject=subscribe>
Sender: xen-devel-bounces@lists.xen.org
Errors-To: xen-devel-bounces@lists.xen.org
To: Jan Beulich <JBeulich@suse.com>
Cc: George.Dunlap@eu.citrix.com, xen-devel@lists.xenproject.org, keir.xen@gmail.com, tim@xen.org
List-Id: xen-devel@lists.xenproject.org

On 02/05/14 14:31, Jan Beulich wrote:
>>>> On 02.05.14 at 13:05, <roger.pau@citrix.com> wrote:
>> With the patch applied I can boot fine, no error messages at all. I've
>> printed the address that's causing the vioapic_range call, it's
>> 0x1073741824, which according to the e820 map passed by Xen falls into a
>> region marked as valid memory:
>>
>> SMAP type=01 base=0000000000100000 len=000000003ff6e000
> 
> If the number in the text above really was represented in hex, it very
> clearly is outside the range you show. Assuming it was in fact decimal,
> its hex representation being 0x40000000 also makes clear that this is
> outside the shown range. But it's also rather strange an address for an
> IO-APIC to live at. So in the end I'm only confused.

My bad, I've incorrectly printed this as 0x%lu instead of %lx, the
following output is correct:

SMAP type=01 base=0000000000000000 len=0000000000092400
SMAP type=02 base=00000000000f0000 len=0000000000010000
SMAP type=01 base=0000000000100000 len=000000003ff6e000
SMAP type=04 base=00000000dfdf9c00 len=0000000000052000
SMAP type=03 base=00000000dfe4bc00 len=0000000000002000
SMAP type=02 base=00000000dfe4dc00 len=00000000001b2400
SMAP type=02 base=00000000f8000000 len=0000000005000000
SMAP type=02 base=00000000fe000000 len=0000000000d00400
SMAP type=02 base=00000000fee00000 len=0000000000100000
SMAP type=02 base=00000000ffb00000 len=0000000000500000
SMAP type=02 base=0000000100000000 len=00000000a0000000
(XEN) Trying to access 0x40000000 <- Printed from vioapic_range.

In this case 0x40000000 falls in range reported as usable RAM by Xen:

SMAP type=01 base=0000000000100000 len=000000003ff6e000

Which goes from

[0x100000, 0x4006e000]

Roger.