From: will.deacon@arm•com (Will Deacon)
To: linux-arm-kernel@lists•infradead.org
Subject: [PATCH RFC v1 1/2] documentation/iommu: Add description of Hisilicon System MMU binding
Date: Tue, 24 Jun 2014 15:30:51 +0100 [thread overview]
Message-ID: <20140624143051.GK9121@arm.com> (raw)
In-Reply-To: <a718d22a3ef3414fb6992bc54a0a893f@BL2PR03MB468.namprd03.prod.outlook.com>
On Fri, Jun 20, 2014 at 07:57:03PM +0100, Varun Sethi wrote:
> > > [Sethi Varun-B16395] We should be considering the bus topology i.e.
> > > what if the device is setting behind a bridge? It's possible the
> > > requestor id for the DMA transaction belongs to the bridge. Also, the
> > > iommu group creation should also take in to account the topology.
> >
> > Yeah, as I mentioned above, this assumes that RequesterID == StreamID.
> > Are you simply alluding to a non-transparent PCI bridge, or do you have
> > something different? For non-transparent bridges, I guess we can re-use
> > the code already in the kernel (VFIO handles this with its groups IIUC)?
> Yes, we can use the API from patch posted by Alex Williamson.
> https://lkml.org/lkml/2014/5/10/129
Thanks for the pointer. Looks like I can register a dummy function (return
0;) as the iterator and I should end up with the RequesterID I want. Then DT
can map that to the StreamID.
Will
next prev parent reply other threads:[~2014-06-24 14:30 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-06-05 13:37 [PATCH RFC v1 0/2] Add support for Hisilicon SMMU architecture Zhen Lei
2014-06-05 13:37 ` [PATCH RFC v1 1/2] documentation/iommu: Add description of Hisilicon System MMU binding Zhen Lei
2014-06-05 15:26 ` Mark Rutland
2014-06-06 6:48 ` Arnd Bergmann
2014-06-06 11:07 ` Dave Martin
2014-06-11 8:12 ` leizhen
2014-06-16 16:26 ` Will Deacon
2014-06-16 16:42 ` Arnd Bergmann
2014-06-16 16:45 ` Will Deacon
2014-06-16 17:25 ` Arnd Bergmann
2014-06-16 18:26 ` Will Deacon
2014-06-17 7:14 ` Arnd Bergmann
2014-06-17 11:49 ` Thierry Reding
2014-06-18 11:10 ` Varun Sethi
2014-06-18 12:31 ` Will Deacon
2014-06-20 9:54 ` Varun Sethi
2014-06-20 17:49 ` Will Deacon
2014-06-20 18:57 ` Varun Sethi
2014-06-24 14:30 ` Will Deacon [this message]
2014-06-17 7:57 ` leizhen
2014-06-16 16:44 ` Arnd Bergmann
2014-06-05 13:37 ` [PATCH RFC v1 2/2] iommu/hisilicon: Add support for Hisilicon Ltd. System MMU architecture Zhen Lei
2014-06-05 15:21 ` [PATCH RFC v1 0/2] Add support for Hisilicon SMMU architecture Mark Rutland
2014-06-06 0:21 ` leizhen
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=20140624143051.GK9121@arm.com \
--to=will.deacon@arm$(echo .)com \
--cc=linux-arm-kernel@lists$(echo .)infradead.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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