From: Julien Grall <julien.grall@linaro.org>
To: Manish Jaggi <mjaggi@caviumnetworks.com>,
"xen-devel@lists.xenproject.org" <xen-devel@lists.xenproject.org>,
Andre Przywara <andre.przywara@arm.com>,
Julien Grall <julien.grall@arm.com>,
Sameer Goel <sgoel@codeaurora.org>,
Stefano Stabellini <sstabellini@kernel.org>,
"Nowicki, Tomasz" <Tomasz.Nowicki@cavium.com>
Subject: Re: [RFC] [Draft Design v2] ACPI/IORT Support in Xen.
Date: Thu, 16 Nov 2017 11:37:23 +0000 [thread overview]
Message-ID: <568ba5e3-1998-b9bc-5a27-b4a4adb4ba7c@linaro.org> (raw)
In-Reply-To: <5fa16d9e-227f-d0ce-15b6-7c55dd58cb81@caviumnetworks.com>
On 16/11/17 07:39, Manish Jaggi wrote:
> On 11/14/2017 6:53 PM, Julien Grall wrote:
>>> 3. IORT for Dom0
>>> -----------------
>>> IORT for Dom0 is based on host iort. Few nodes could be removed or
>>> modified.
>>> For instance
>>> - Host SMMU nodes should not be present as Xen should only touch it.
>>> - platform nodes (named components) may be controlled by xen command
>>> line.
>>
>> I am not sure where does this example come from? As I said, there are
>> no plan to support Platform Device passthrough with ACPI. A better
>> example here would removing PMCG.
>>
> It came from review comments on my previous IORT SMMU hiding patch.
> Andre suggested that Platform Nodes are needed.
>
> After some brainstorming with Julien we found two problems:
> 1) This only covers RC nodes, but not "named components" (platform
> devices), which we will need. ...
>
> From: https://www.mail-archive.com/xen-devel@lists.xen.org/msg123434.html
I think you misunderstood my comment here... What I call "device
passthrough" is giving access to a device to a domain other than the
Hardware Domain
There are no plan for supporting platform device-passthrough on ACPI and
I don't understand why you would like to control that using the command
line.
What Andre was saying is your series was not covering the "named
components" for the Hardware Domain.
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-11-16 11:37 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-11-08 14:38 [RFC] [Draft Design v2] ACPI/IORT Support in Xen Manish Jaggi
2017-11-14 13:23 ` Julien Grall
2017-11-16 7:39 ` Manish Jaggi
2017-11-16 11:37 ` Julien Grall [this message]
2017-11-16 11:46 ` Manish Jaggi
2017-11-16 11:53 ` Julien Grall
2017-11-16 12:39 ` Manish Jaggi
2017-11-16 13:38 ` Julien Grall
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=568ba5e3-1998-b9bc-5a27-b4a4adb4ba7c@linaro.org \
--to=julien.grall@linaro.org \
--cc=Tomasz.Nowicki@cavium.com \
--cc=andre.przywara@arm.com \
--cc=julien.grall@arm.com \
--cc=mjaggi@caviumnetworks.com \
--cc=sgoel@codeaurora.org \
--cc=sstabellini@kernel.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).