From: George Dunlap <george.dunlap@eu.citrix.com>
To: Wei Liu <wei.liu2@citrix.com>, Ian Campbell <Ian.Campbell@citrix.com>
Cc: keir@xen.org,
Stefano Stabellini <stefano.stabellini@eu.citrix.com>,
Tim Deegan <tim@xen.org>, Jan Beulich <JBeulich@suse.com>,
xen-devel@lists.xen.org
Subject: Re: Limitation in HVM physmap
Date: Fri, 18 Oct 2013 16:06:01 +0100 [thread overview]
Message-ID: <52614E59.50103@eu.citrix.com> (raw)
In-Reply-To: <20131018150417.GF20185@zion.uk.xensource.com>
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 = 0xFFF
>>> (d28) Base = 0xC000; Length = 0x100; Alignment = 0xFF; Owner = PCI [00|04|
>>> (d28) Base = 0xC100; Length = 0x100; Alignment = 0xFF; Owner = PCI [00|03|
>>> (d28) Base = 0xC200; Length = 0x10; Alignment = 0xF; Owner = PCI [00|01|
>>> (d28) Type = Mem32; Base = 0x80000000; Length = 0x3100000; Alignment = 0x1FFFFF
>>> (d28) Base = 0x80000000; Length = 0x2000000; Alignment = 0x1FFFFFF; Owne
>>> (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
> driver...
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.
-George
next prev parent reply other threads:[~2013-10-18 15:06 UTC|newest]
Thread overview: 36+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-10-18 14:20 Limitation in HVM physmap Wei Liu
2013-10-18 14:26 ` George Dunlap
2013-10-18 15:12 ` Paul Durrant
2013-10-18 14:28 ` Tim Deegan
2013-10-18 14:36 ` Wei Liu
2013-10-18 14:41 ` Tim Deegan
2013-10-18 14:56 ` Wei Liu
2013-10-18 14:59 ` Ian Campbell
2013-10-18 15:00 ` Ian Campbell
2013-10-18 15:04 ` Wei Liu
2013-10-18 15:06 ` George Dunlap [this message]
2013-10-18 15:07 ` Wei Liu
2013-10-18 15:09 ` Ian Campbell
2013-10-18 15:14 ` Stefano Stabellini
2013-10-18 14:47 ` Jan Beulich
2013-10-18 15:01 ` Wei Liu
2013-10-18 15:07 ` Ian Campbell
2013-10-18 15:30 ` Wei Liu
2013-10-18 15:09 ` Jan Beulich
2013-11-01 12:21 ` Wei Liu
2013-11-01 12:26 ` George Dunlap
2013-11-01 12:33 ` Ian Campbell
2013-11-01 12:45 ` Wei Liu
2013-11-01 12:49 ` Ian Campbell
2013-11-01 14:08 ` Wei Liu
2013-11-01 14:12 ` Ian Campbell
2013-11-01 14:19 ` Wei Liu
2013-11-01 14:31 ` Ian Campbell
2013-11-01 14:55 ` Wei Liu
2013-11-01 15:04 ` Ian Campbell
2013-11-04 9:28 ` Fabio Fantoni
2013-11-04 11:42 ` Wei Liu
2013-11-04 12:05 ` Fabio Fantoni
2013-11-04 12:17 ` Wei Liu
2013-11-04 14:08 ` Fabio Fantoni
2013-11-04 14:14 ` Wei Liu
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=52614E59.50103@eu.citrix.com \
--to=george.dunlap@eu.citrix.com \
--cc=Ian.Campbell@citrix.com \
--cc=JBeulich@suse.com \
--cc=keir@xen.org \
--cc=stefano.stabellini@eu.citrix.com \
--cc=tim@xen.org \
--cc=wei.liu2@citrix.com \
--cc=xen-devel@lists.xen.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.