[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Xen-devel] [V10 PATCH 0/4] pvh dom0 patches...

On 02/05/14 14:31, Jan Beulich wrote:
>>>> On 02.05.14 at 13:05, <roger.pau@xxxxxxxxxx> 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]


Xen-devel mailing list



Lists.xenproject.org is hosted with RackSpace, monitoring our
servers 24x7x365 and backed by RackSpace's Fanatical Support®.