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: Thu, 16 Apr 2015 11:40:08 +0100 [thread overview]
Message-ID: <20150416104008.GB25640@arm.com> (raw)
In-Reply-To: <BN3PR0301MB121987D3E12F25B79E8C51EFEAE50@BN3PR0301MB1219.namprd03.prod.outlook.com>
Hi Varun,
Thanks for adding me to Cc.
On Wed, Apr 15, 2015 at 02:18:13PM +0100, Varun Sethi wrote:
> Yes, deviceid=stream id (i.e. ICID + other bits). I am not sure if TBU ID
> would also be forwarded as a part of stream id to GIC. My understanding is
> that TBU ID is forwarded (as a part of the stream ID) to the TCU in case
> of a TBU translation miss. In case of the LS2085 PCIe controller you would
> have to setup the PCIe device ID to stream ID translation table. We may
> have to restrict the number of entries based on the available number of
> contexts.
Unfortunately, I'm having a really hard time parsing this thread (some parts
of it simply don't make sense; others use non-architectural terms and
overall I don't get a feeling for the problem).
Please could you explain your system design step by step so that I can
understand (a) what you've built and (b) why the current design of Linux is
causing you problems?
Sorry if I'm just being thick, but it's important that we get this right.
Cheers,
Will
next prev parent reply other threads:[~2015-04-16 10:40 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 [this message]
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
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=20150416104008.GB25640@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