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

Re: [Xen-devel] Limitation in HVM physmap

On 18/10/13 16:04, Wei Liu wrote:
On Fri, Oct 18, 2013 at 03:59:10PM +0100, Ian Campbell wrote:
During OVMF initialization:

(d28) PciBus: Resource Map for Root Bridge PciRoot(0x0)
(d28) Type =   Io16; Base = 0xC000;     Length = 0x1000;        Alignment = 
(d28)  Base = 0xC000;   Length = 0x100; Alignment = 0xFF;       Owner = PCI  
(d28)  Base = 0xC100;   Length = 0x100; Alignment = 0xFF;       Owner = PCI  
(d28)  Base = 0xC200;   Length = 0x10;  Alignment = 0xF;        Owner = PCI  
(d28) Type =  Mem32; Base = 0x80000000; Length = 0x3100000;     Alignment = 
(d28)  Base = 0x80000000;       Length = 0x2000000;     Alignment = 0x1FFFFFF;  
(d28) |02|00:10]

Later when Linux loads EFIFB driver:
[    2.628264] efifb: framebuffer at 0x80000000, mapped to
0xffffc90000100000, using 1876k, total 1875k
[    2.646827] efifb: mode is 800x600x32, linelength=3200, pages=1
[    2.658833] efifb: scrolling: redraw
[    2.666342] efifb: Truecolor: size=8:8:8:8, shift=24:16:8:0

0xf0000000 is mapped by:
What hardware is backing the framebuffer at 0x80000000? It doesn't
appear to be this cirrus device.

Looking that the "Resource Map for Root Bridge" 0x8000000 is backed by
00:02:00 (trancated above) and 00:02.0 is also owned by Cirrus Logic

xentrace -e all should give you a record of all calls to set_p2m_entry(), as well as any MMIO / PIO, so you should be able to verify the remapping / double mapping happening from the other direction.


Xen-devel mailing list



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