From: "Roger Pau Monné" <roger.pau@citrix.com>
To: Jan Beulich <JBeulich@suse.com>
Cc: xen-devel@lists.xenproject.org,
Julien Grall <julien.grall@linaro.org>,
Stefano Stabellini <stefano.stabellini@citrix.com>,
Ian Campbell <Ian.Campbell@citrix.com>, Tim Deegan <tim@xen.org>
Subject: Re: [PATCH] xen/arm: Implement domain_get_maximum_gpfn
Date: Wed, 2 Jul 2014 12:51:40 +0200 [thread overview]
Message-ID: <53B3E43C.2090603@citrix.com> (raw)
In-Reply-To: <53B3FB89020000780001F6C5@mail.emea.novell.com>
On 02/07/14 12:31, Jan Beulich wrote:
>>>> On 02.07.14 at 12:19, <roger.pau@citrix.com> wrote:
>> For PVH guests there's still no MMIO hole (or any other kind of hole) at
>> all, the hole(s) is only there for Dom0.
>
> So where would passed through devices get their MMIO BARs located?
> (I realize pass-through isn't supported yet for PVH, but I didn't expect
> such fundamental things to be missing.)
We could always add a MMIO region to a PVH guest in backwards compatible
way, the only requirement is to make sure the e820 provided to the guest
has this hole set up, but I see no reason to add it before having this
functionality, or to add it unconditionally to guests even if no devices
are passed through.
Also, shouldn't PVH guests use pcifront/pciback, which means it won't
have any BARs mapped directly?
Roger.
next prev parent reply other threads:[~2014-07-02 10:51 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-07-01 14:57 [PATCH] xen/arm: Implement domain_get_maximum_gpfn Julien Grall
2014-07-01 16:57 ` Stefano Stabellini
2014-07-01 18:36 ` Julien Grall
2014-07-01 18:53 ` Andrew Cooper
2014-07-09 11:38 ` Julien Grall
2014-07-16 16:02 ` Ian Campbell
2014-07-16 18:17 ` Julien Grall
2014-09-01 21:32 ` Julien Grall
2014-09-03 8:44 ` Ian Campbell
2014-09-03 9:00 ` Tamas K Lengyel
2014-09-08 20:43 ` Julien Grall
2014-09-08 20:47 ` Tamas K Lengyel
2014-09-09 12:50 ` Tamas K Lengyel
2014-09-09 13:09 ` Andrew Cooper
2014-09-09 14:01 ` Tamas K Lengyel
2014-09-10 11:21 ` Tamas K Lengyel
2014-07-02 9:12 ` Ian Campbell
2014-07-02 9:19 ` Julien Grall
2014-07-02 9:22 ` Ian Campbell
2014-07-02 9:37 ` Julien Grall
2014-07-02 9:41 ` Ian Campbell
2014-07-02 9:50 ` Jan Beulich
2014-07-02 9:52 ` Ian Campbell
2014-07-02 10:19 ` Roger Pau Monné
2014-07-02 10:31 ` Jan Beulich
2014-07-02 10:51 ` Roger Pau Monné [this message]
2014-07-02 10:52 ` Ian Campbell
2014-07-02 10:58 ` Andrew Cooper
2014-07-02 11:21 ` Ian Campbell
2014-07-02 13:44 ` 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=53B3E43C.2090603@citrix.com \
--to=roger.pau@citrix.com \
--cc=Ian.Campbell@citrix.com \
--cc=JBeulich@suse.com \
--cc=julien.grall@linaro.org \
--cc=stefano.stabellini@citrix.com \
--cc=tim@xen.org \
--cc=xen-devel@lists.xenproject.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 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).