linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: will.deacon@arm.com (Will Deacon)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 1/2] irqchip/gicv3-its: Support share device ID
Date: Mon, 27 Apr 2015 18:04:23 +0100	[thread overview]
Message-ID: <20150427170423.GC3310@arm.com> (raw)
In-Reply-To: <BN1PR0301MB0627CD95FC31B221DAA644EDEAE90@BN1PR0301MB0627.namprd03.prod.outlook.com>

On Mon, Apr 27, 2015 at 02:08:10PM +0100, Varun Sethi wrote:
> > >>> In the SMMU/GIC-500-ITS world the iommu isolation ID (the stream ID)
> > >>> and the GIC-ITS device ID are in fact the same ID.
> > >>
> > >> The DeviceID is the "MSI group" you mention. This is what provides
> > >> isolation at the ITS level.
> > >>
> > > [varun] True, in case of a transparent host bridge device Id won't
> > > provide the necessary isolation.
> > 
> > Well, it depends how you look at it. How necessary is this isolation, since
> > we've already established that you couldn't distinguish between these
> > devices at the IOMMU level?
> > 
> [varun] Yes, the devices would fall in the same IOMMU group. So, devices
> would end up sharing the interrupt?

Well, I think that's the crux of the issue here. If IOMMU groups are also
needed to relay constraints to the IRQ subsystem, then perhaps we need a
more general notion of device grouping and ID transformations between
the different levels of group hierarchy.

Will

  reply	other threads:[~2015-04-27 17:04 UTC|newest]

Thread overview: 37+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-04-15  9:49 [PATCH] irqchip/gicv3-its: Decrease page size when needed Minghuan Lian
2015-04-15  9:49 ` [PATCH 1/2] irqchip/gicv3-its: Support share device ID Minghuan Lian
2015-04-15 11:08   ` Varun Sethi
2015-04-15 11:38     ` Minghuan.Lian at freescale.com
2015-04-15 13:18       ` Varun Sethi
2015-04-16 10:40         ` Will Deacon
2015-04-17 14:19           ` Stuart Yoder
2015-04-17 17:57             ` Varun Sethi
2015-04-22 17:07             ` Will Deacon
2015-04-22 18:40               ` Varun Sethi
2015-04-22 19:41               ` Stuart Yoder
2015-04-24 16:18                 ` Will Deacon
2015-04-24 16:44                   ` Marc Zyngier
2015-04-24 18:18                     ` Stuart Yoder
2015-04-25 10:39                       ` Marc Zyngier
2015-04-26 18:20                         ` Varun Sethi
2015-04-27  7:58                           ` Marc Zyngier
2015-04-27 13:08                             ` Varun Sethi
2015-04-27 17:04                               ` Will Deacon [this message]
2015-05-01 15:23                                 ` Stuart Yoder
2015-05-01 15:26                                   ` Will Deacon
2015-04-27 17:17                               ` Marc Zyngier
2015-04-24 19:24                     ` Stuart Yoder
2015-04-24 18:09                   ` Stuart Yoder
2015-04-26 18:26                 ` Varun Sethi
2015-04-15 16:36   ` Marc Zyngier
2015-04-16  2:57     ` Minghuan.Lian at freescale.com
2015-04-16 10:04       ` Marc Zyngier
2015-04-16 10:57         ` Minghuan.Lian at freescale.com
2015-04-16 11:50           ` Marc Zyngier
2015-04-16 18:38             ` Varun Sethi
2015-04-17  2:34               ` Minghuan.Lian at freescale.com
2015-04-15  9:49 ` [PATCH 2/2] pci/layerscape: Add LS2085A MSI support Minghuan Lian
2015-04-15 11:51 ` [PATCH] irqchip/gicv3-its: Decrease page size when needed Jason Cooper
2015-04-15 14:17   ` Marc Zyngier
2015-04-16  1:15     ` Minghuan.Lian at freescale.com
2015-04-15 16:31 ` Marc Zyngier

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=20150427170423.GC3310@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).