From: Julien Grall <julien.grall@arm.com>
To: Manish Jaggi <mjaggi@caviumnetworks.com>,
shankerd@codeaurora.org, xen-devel@lists.xen.org
Cc: Stefano Stabellini <sstabellini@kernel.org>,
Steve Capper <Steve.Capper@arm.com>,
Andre Przywara <andre.przywara@arm.com>,
Jiandi An <anjiandi@codeaurora.org>,
Punit Agrawal <punit.agrawal@arm.com>,
Sameer Goel <sgoel@codeaurora.org>,
nd@arm.com, Charles Garcia-Tobin <Charles.Garcia-Tobin@arm.com>
Subject: Re: xen/arm: Hiding SMMUs from Dom0 when using ACPI on Xen
Date: Thu, 18 May 2017 21:09:31 +0100 [thread overview]
Message-ID: <e7abc302-49a7-1521-82d5-56c13f1c375e@arm.com> (raw)
In-Reply-To: <02795d5b-39e9-3b20-6337-fb3941c20cef@caviumnetworks.com>
On 18/05/2017 21:02, Manish Jaggi wrote:
> In the IORT table using the PCI-RC node, SMMU node and ITS node,
> RID->StreamID->Device-ID mapping can be generated.
> As per IORT spec toady, same RID can be mapped to different StreamIDs
> using two ID Array elements with same RID range but different output
> reference.
> There exists no use case for such a scenario hence a clarification is
> required in IORT spec which states that RID range cannot overlap in the
> ID array.
I understand that.
>
> with this clarification in place, it is straight-forward to map RID to a
> device-ID by replacing output of SMMU to output of RCI-RC
I am not sure to follow your suggestion here. But I will wait a patch
before commenting.
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-05-18 20:09 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-02-22 14:10 xen/arm: Hiding SMMUs from Dom0 when using ACPI on Xen Julien Grall
2017-02-27 13:23 ` Vijay Kilari
2017-02-27 14:12 ` Julien Grall
2017-02-27 16:58 ` Shanker Donthineni
2017-02-27 18:12 ` Julien Grall
2017-05-18 11:59 ` Manish Jaggi
2017-05-18 14:57 ` Julien Grall
2017-05-18 20:02 ` Manish Jaggi
2017-05-18 20:09 ` Julien Grall [this message]
2017-06-08 12:38 ` 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=e7abc302-49a7-1521-82d5-56c13f1c375e@arm.com \
--to=julien.grall@arm.com \
--cc=Charles.Garcia-Tobin@arm.com \
--cc=Steve.Capper@arm.com \
--cc=andre.przywara@arm.com \
--cc=anjiandi@codeaurora.org \
--cc=mjaggi@caviumnetworks.com \
--cc=nd@arm.com \
--cc=punit.agrawal@arm.com \
--cc=sgoel@codeaurora.org \
--cc=shankerd@codeaurora.org \
--cc=sstabellini@kernel.org \
--cc=xen-devel@lists.xen.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).