xen-devel.lists.xenproject.org archive mirror
 help / color / mirror / Atom feed
From: Julien Grall <julien.grall@linaro.org>
To: Manish Jaggi <mjaggi@caviumnetworks.com>,
	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>,
	xen-devel <xen-devel@lists.xenproject.org>
Subject: Re: [RFC] [Draft Design v2] ACPI/IORT Support in Xen.
Date: Thu, 16 Nov 2017 11:53:11 +0000	[thread overview]
Message-ID: <2b9b3f63-90c9-039d-1e9b-c80ba93df325@linaro.org> (raw)
In-Reply-To: <cab84cc1-601e-6b9f-d466-ff861ac7a824@caviumnetworks.com>

Hi Manish,

On 16/11/17 11:46, Manish Jaggi wrote:
> 
> 
> On 11/16/2017 5:07 PM, Julien Grall wrote:
>>
>>
>> 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.
> 
> The section 3 is IORT for Dom0, where I mentioned that  some platform 
> devices can be hidden from dom0.
> So your comment on Platform device Passthrough might not be valid then 
> as it is for domU's only.
> 
> Regarding the visibility of a platform device for dom0, I took cue from 
> your comment below

Where did I ever mention the command line solution? Please stop trying 
to put words in my mouth.

There are other reason than passthrough to hide device from the Hardware 
Domain.

> 
> This has two benefits:
> 
> ...
> 3) We could decide in a finer grain which devices (e.g platform 
> device)Dom0 can see.
> From: https://www.mail-archive.com/xen-devel@lists.xen.org/msg124534.html
> 
>>
>> Cheers,
>>
> 

-- 
Julien Grall

_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xen.org
https://lists.xen.org/xen-devel

  reply	other threads:[~2017-11-16 11:53 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
2017-11-16 11:46       ` Manish Jaggi
2017-11-16 11:53         ` Julien Grall [this message]
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=2b9b3f63-90c9-039d-1e9b-c80ba93df325@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).