From: Julien Grall <julien.grall@linaro.org>
To: "Roger Pau Monné" <roger.pau@citrix.com>
Cc: edgar.iglesias@xilinx.com,
Stefano Stabellini <sstabellini@kernel.org>,
Jan Beulich <JBeulich@suse.com>, Wei Chen <Wei.Chen@arm.com>,
Steve Capper <Steve.Capper@arm.com>,
Manish Jaggi <mjaggi@caviumnetworks.com>,
manish.jaggi@caviumnetworks.com,
Punit Agrawal <punit.agrawal@arm.com>,
vikrams@qti.qualcomm.com, okaya@qti.qualcomm.com, "Goel,
Sameer" <sgoel@qti.qualcomm.com>,
Andre Przywara <andre.przywara@arm.com>,
xen-devel <xen-devel@lists.xenproject.org>,
Dave P Martin <Dave.Martin@arm.com>,
Vijaya Kumar K <Vijaya.Kumar@caviumnetworks.com>
Subject: Re: Notes from PCI Passthrough design discussion at Xen Summit
Date: Thu, 20 Jul 2017 12:52:14 +0100 [thread overview]
Message-ID: <481ccd87-d6a2-f3e6-63cc-1f1ac91e0756@linaro.org> (raw)
In-Reply-To: <20170720110539.3ylhgmotcbq7kzru@dhcp-3-128.uk.xensource.com>
On 20/07/17 12:06, Roger Pau Monné wrote:
> On Thu, Jul 20, 2017 at 11:47:04AM +0100, Julien Grall wrote:
>>>> Slide 18 shows only for DomU ?
>>>
>>> ARM folks believe this is not needed for Dom0 in the ARM case, I don't
>>> have an opinion, I know it's certainly mandatory for x86 PVH Dom0.
>>
>> That was 8 months ago, you managed to convince me we should also trap for
>> DOM0 last time we met at the Haymakers :).
>
> Right, my bad. I was indeed confused. We spoke during the design
> session about ARM not needing to trap MSI/MSI-X probably (which x86
> must do).
It will depend on the MSI controllers. For GICv3 ITS, it will not need
to trap them for Dom0 because we expose the same number of controllers
as the host and the MSIs will be configured directly via the virtual
interrupt controller.
This might be different for other controllers, but I haven't yet fully
looked at them yet.
Cheers,
--
Julien Grall
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xen.org
https://lists.xen.org/xen-devel
next prev parent reply other threads:[~2017-07-20 11:52 UTC|newest]
Thread overview: 35+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-05-26 17:14 [RFC] ARM PCI Passthrough design document Julien Grall
2017-05-29 2:30 ` Manish Jaggi
2017-05-29 18:14 ` Julien Grall
2017-05-30 5:53 ` Manish Jaggi
2017-05-30 9:33 ` Julien Grall
2017-05-30 7:53 ` Roger Pau Monné
2017-05-30 9:42 ` Julien Grall
2017-05-30 7:40 ` Roger Pau Monné
2017-05-30 9:54 ` Julien Grall
2017-06-16 0:31 ` Stefano Stabellini
2017-06-16 0:23 ` Stefano Stabellini
2017-06-20 0:19 ` Vikram Sethi
2017-06-28 15:22 ` Julien Grall
2017-06-29 15:17 ` Vikram Sethi
2017-07-03 14:35 ` Julien Grall
2017-07-04 8:30 ` roger.pau
2017-07-06 20:55 ` Vikram Sethi
2017-07-07 8:49 ` Roger Pau Monné
2017-07-07 21:50 ` Stefano Stabellini
2017-07-07 23:40 ` Vikram Sethi
2017-07-08 7:34 ` Roger Pau Monné
2018-01-19 10:34 ` Manish Jaggi
2017-07-19 14:41 ` Notes from PCI Passthrough design discussion at Xen Summit Punit Agrawal
2017-07-20 3:54 ` Manish Jaggi
2017-07-20 8:24 ` Roger Pau Monné
2017-07-20 9:32 ` Manish Jaggi
2017-07-20 10:29 ` Roger Pau Monné
2017-07-20 10:47 ` Julien Grall
2017-07-20 11:06 ` Roger Pau Monné
2017-07-20 11:52 ` Julien Grall [this message]
2017-07-20 11:02 ` Manish Jaggi
2017-07-20 10:41 ` Julien Grall
2017-07-20 11:00 ` Manish Jaggi
2017-07-20 12:24 ` Julien Grall
2018-01-22 11:10 ` [RFC] ARM PCI Passthrough design document Manish Jaggi
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=481ccd87-d6a2-f3e6-63cc-1f1ac91e0756@linaro.org \
--to=julien.grall@linaro.org \
--cc=Dave.Martin@arm.com \
--cc=JBeulich@suse.com \
--cc=Steve.Capper@arm.com \
--cc=Vijaya.Kumar@caviumnetworks.com \
--cc=Wei.Chen@arm.com \
--cc=andre.przywara@arm.com \
--cc=edgar.iglesias@xilinx.com \
--cc=manish.jaggi@caviumnetworks.com \
--cc=mjaggi@caviumnetworks.com \
--cc=okaya@qti.qualcomm.com \
--cc=punit.agrawal@arm.com \
--cc=roger.pau@citrix.com \
--cc=sgoel@qti.qualcomm.com \
--cc=sstabellini@kernel.org \
--cc=vikrams@qti.qualcomm.com \
--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).