From: Simon Martin <furryfuttock@gmail.com>
To: Ian Campbell <Ian.Campbell@citrix.com>
Cc: Andrew Cooper <andrew.cooper3@citrix.com>,
Xenbegn developer <xen.begn.dev@gmail.com>,
xen-devel@lists.xen.org,
Stefano Stabellini <stefano.stabellini@eu.citrix.com>
Subject: Re: [Query] Flow of PCI device dedicated to a domU
Date: Tue, 22 Jul 2014 17:06:28 +0100 [thread overview]
Message-ID: <1669742135.20140722170628@gmail.com> (raw)
In-Reply-To: <1406044966.32556.1.camel@kazak.uk.xensource.com>
Hello Ian,
>> If I read this correctly you are saying that the MMIO region is
>> already mapped into my domain by xl? So when I go and read the BAR
>> register from the PCI configuration I can just go and access it
>> directly or do I have to update the VA mapping?
> Stefano meant mapped in the p2m which under ARM or x86 HVM still means
> you need to make a virtual mapping of those PFNs.
> Under X86 PV "mapping" in this context really just means giving
> permission to map the underlying MFNs, so you still need to create a
> virtual mapping but they don't exist in your p2m until you put them
> there.
Thanks Ian, that is what I had understood from the mail that you sent
me on the thread I started about "Consuming PCI device in PV kernel".
Just wanted to confirm. I have just about worked my way up to
implementing the MMIO access now and wanted to make sure before I
carry on.
--
Best regards,
Simon mailto:furryfuttock@gmail.com
next prev parent reply other threads:[~2014-07-22 16:06 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-07-16 6:12 [Query] Flow of PCI device dedicated to a domU Xenbegn developer
2014-07-16 9:50 ` Andrew Cooper
2014-07-17 6:34 ` Xenbegn developer
2014-07-17 9:42 ` Andrew Cooper
2014-07-22 9:43 ` Xenbegn developer
2014-07-22 9:53 ` Andrew Cooper
2014-07-22 10:02 ` Xenbegn developer
2014-07-22 9:50 ` Xenbegn developer
2014-07-22 9:56 ` Andrew Cooper
2014-07-22 10:13 ` Xenbegn developer
2014-07-22 10:33 ` Andrew Cooper
2014-07-22 10:51 ` Xenbegn developer
2014-07-22 11:33 ` Xenbegn developer
2014-07-22 12:44 ` Ian Campbell
2014-07-22 14:11 ` Stefano Stabellini
2014-07-22 15:56 ` Simon Martin
2014-07-22 16:01 ` Simon Martin
2014-07-22 16:02 ` Ian Campbell
2014-07-22 16:06 ` Simon Martin [this message]
2014-07-22 16:06 ` Stefano Stabellini
2014-07-22 16:09 ` Simon Martin
2014-07-24 5:17 ` Xenbegn developer
2014-07-24 10:04 ` Stefano Stabellini
2014-07-24 8:08 ` Xenbegn developer
2014-07-24 9:20 ` Ian Campbell
2014-07-24 10:21 ` Stefano Stabellini
2014-07-16 13:46 ` Konrad Rzeszutek Wilk
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=1669742135.20140722170628@gmail.com \
--to=furryfuttock@gmail.com \
--cc=Ian.Campbell@citrix.com \
--cc=andrew.cooper3@citrix.com \
--cc=stefano.stabellini@eu.citrix.com \
--cc=xen-devel@lists.xen.org \
--cc=xen.begn.dev@gmail.com \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).