From: will.deacon@arm.com (Will Deacon)
To: linux-arm-kernel@lists.infradead.org
Subject: [Ksummit-2013-discuss] [ARM ATTEND] Describing complex, non-probable system topologies
Date: Fri, 2 Aug 2013 13:01:15 +0100 [thread overview]
Message-ID: <20130802120115.GO2465@mudshark.cambridge.arm.com> (raw)
In-Reply-To: <CAErSpo7yUDMsaVSR6kcy4Jeb0naVpPPfpzFZQ2MP0NLDH1aAFg@mail.gmail.com>
On Thu, Aug 01, 2013 at 11:26:30PM +0100, Bjorn Helgaas wrote:
> On Thu, Aug 1, 2013 at 12:35 PM, Will Deacon <will.deacon@arm.com> wrote:
>
> > ... For example, interfacing
> > a PCIe device with an SMMU requires knowledge of both the requester id
> > associated with the device and how that maps to incoming stream ids
> > (based off the AXI bus id) on the SMMU.
>
> Tangent: We're trying to hash out a way for IOMMU drivers to use a PCI
> interface to discover the requester IDs associated with a device. We
> currently only have one users (intel-iommu.c), and it would be awesome
> to have another user to help make things generic. Please chime in if
> you have opinions.
>
> https://lkml.kernel.org/r/20130711210326.1701.56478.stgit at bling.home
Ooh, yes, thanks Bjorn. I'll find some time to take a look at that.
Cheers,
Will
prev parent reply other threads:[~2013-08-02 12:01 UTC|newest]
Thread overview: 41+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-08-01 18:35 [ARM ATTEND] Describing complex, non-probable system topologies Will Deacon
2013-08-01 18:42 ` Dave Martin
2013-08-01 22:41 ` [Ksummit-2013-discuss] " David Brown
2013-08-01 19:27 ` Greg KH
2013-08-01 19:39 ` Russell King - ARM Linux
2013-08-01 20:15 ` Greg KH
2013-08-01 20:18 ` Russell King - ARM Linux
2013-08-01 20:36 ` Greg KH
2013-08-01 20:45 ` Russell King - ARM Linux
2013-08-01 21:04 ` Greg KH
2013-08-01 21:48 ` James Bottomley
2013-08-01 23:16 ` Mark Brown
2013-08-02 9:03 ` Tony Lindgren
2013-08-02 9:32 ` Greg KH
2013-08-02 12:34 ` Tony Lindgren
2013-08-02 14:14 ` Greg KH
2013-08-02 15:26 ` Dave Martin
2013-08-02 16:45 ` Will Deacon
2013-08-05 6:55 ` Tony Lindgren
2013-08-05 7:11 ` Greg KH
2013-08-05 7:37 ` Tony Lindgren
2013-08-05 8:02 ` Greg KH
2013-08-05 8:21 ` Tony Lindgren
2013-08-05 8:51 ` Greg KH
2013-08-05 9:14 ` Tony Lindgren
2013-08-08 16:50 ` Kevin Hilman
2013-08-02 11:53 ` Will Deacon
2013-08-02 12:37 ` Tony Lindgren
2013-08-02 14:16 ` Greg KH
2013-08-02 14:20 ` Greg KH
2013-08-02 16:09 ` Will Deacon
2013-08-02 22:32 ` Greg KH
2013-08-03 5:16 ` Olof Johansson
2013-08-05 6:47 ` Tony Lindgren
2013-08-07 1:52 ` Will Deacon
2013-08-20 6:59 ` Hiroshi Doyu
2013-08-07 1:49 ` Will Deacon
2013-08-01 21:41 ` James Bottomley
2013-08-02 17:08 ` Will Deacon
2013-08-01 22:26 ` Bjorn Helgaas
2013-08-02 12:01 ` Will Deacon [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=20130802120115.GO2465@mudshark.cambridge.arm.com \
--to=will.deacon@arm.com \
--cc=linux-arm-kernel@lists.infradead.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).