From: Julien Grall <julien.grall@arm.com>
To: Manish Jaggi <mjaggi@caviumnetworks.com>,
"xen-devel@lists.xenproject.org" <xen-devel@lists.xenproject.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>,
"Goel, Sameer" <sgoel@qti.qualcomm.com>,
nd@arm.com, Charles Garcia-Tobin <Charles.Garcia-Tobin@arm.com>
Subject: Re: [RFC] [PATCH] arm-acpi: Hide SMMU from IORT for hardware domain
Date: Fri, 9 Jun 2017 11:43:05 +0100 [thread overview]
Message-ID: <72a09daa-5fdf-e56e-a41d-cd9dedd37862@arm.com> (raw)
In-Reply-To: <1a231d22-f212-d18f-04c4-a8ed1c98fb08@caviumnetworks.com>
On 09/06/17 11:02, Manish Jaggi wrote:
>>
>>>> SMMU 0
>>>> // Note that range of StreamIDs that map to DeviceIDs excludes
>>>> // the NIC 0 DeviceID as it does not generate MSIs
>>>> // Input ID --> Output reference: Output ID
>>>> 0x0000-0x01ff --> ITS GROUP 0 : 0x10000->0x101ff
>>>> 0x0200-0xffff --> ITS GROUP 0 : 0x20000->0x207ff
>>>>
>>> It can be from 2 different RC's and not from same RC.
>>
>> It is not my point in this example. My point is same RC with split
>> DeviceID mapping.
> ok, I will add that as well.
> The current code parses all entries in pci_rc id_array and patches
> output reference and output_base.
> The only assumption was on Number of ids in pci_rc id_array element and
> the matching smmu id_array element be same.
> I can remove the assumption, will that be ok?
The only thing I care is that you don't have *any* assumption of how the
IORT is designed.
>
> So,One ID Mapping element (Input_base, num_ids, out_base) can translate
> into two or more id_array entries of smmu node.
Which is basically solution 1) below... Anyway, I will wait the next
version hoping that you will handle properly the IORT generation.
Cheers,
--
Julien Grall
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xen.org
https://lists.xen.org/xen-devel
prev parent reply other threads:[~2017-06-09 10:43 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-06-08 12:38 [RFC] [PATCH] arm-acpi: Hide SMMU from IORT for hardware domain Manish Jaggi
2017-06-08 13:09 ` Julien Grall
2017-06-09 7:13 ` Manish Jaggi
2017-06-09 9:23 ` Julien Grall
2017-06-09 10:02 ` Manish Jaggi
2017-06-09 10:43 ` Julien Grall [this message]
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=72a09daa-5fdf-e56e-a41d-cd9dedd37862@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@qti.qualcomm.com \
--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).