Re: [Xen-devel] Limitation in HVM physmap

[Wei Liu <wei.liu2@xxxxxxxxxx>]

On Fri, Nov 01, 2013 at 02:12:32PM +0000, Ian Campbell wrote:
> On Fri, 2013-11-01 at 14:08 +0000, Wei Liu wrote:
> > It didn't print out base address by default. I added my own debug patch
> > and confirmed that base address was set correctly by hvmloader.
> > 
> > (d9) PciBus: Discovered PCI @ [00|02|00]
> > (d9)    BAR[0]: Type = PMem32; Alignment = 0x1FFFFFF;   Length = 0x2000000; 
> >     Offset = 0x10        BaseAddress = 0xF0000000
> > (d9)    BAR[1]: Type =  Mem32; Alignment = 0xFFF;       Length = 0x1000; 
> > Offset = 0x14   BaseAddress = 0xF3020000
> > 
> > Sorry about the confusion.
> 
> OK, so even OVMF thinks the Cirrus memory range is at 0xf0000000, so
> where did efifb get 0x80000000 from?
> 

A few lines later in log

 (d1) PciBus: HostBridge->NotifyPhase(AllocateResources) - Success

EDK2 (not OVMF-specific as this is in generic PCI code) allocates
resources for devices.

Wei.

> Ian.

_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxx
http://lists.xen.org/xen-devel