All of lore.kernel.org
 help / color / mirror / Atom feed
From: Marc Zyngier <marc.zyngier@arm.com>
To: Thomas Gleixner <tglx@linutronix.de>
Cc: Jiang Liu <jiang.liu@linux.intel.com>,
	Jason Cooper <jason@lakedaemon.net>, Ma Jun <majun258@huawei.com>,
	linux-arm-kernel@lists.infradead.org, linux-pci@vger.kernel.org,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH RFC 0/7] Adding core support for wire-MSI bridges
Date: Thu, 05 Nov 2015 12:22:08 +0000	[thread overview]
Message-ID: <563B49F0.7040000@arm.com> (raw)
In-Reply-To: <alpine.DEB.2.11.1511041348060.4032@nanos>

On 04/11/15 13:34, Thomas Gleixner wrote:
> Marc,
> 
> On Fri, 16 Oct 2015, Marc Zyngier wrote:
>> On 16/10/15 02:55, Jiang Liu wrote:
>>> 	There's a working to enable Intel VMD storage device, which
>>> has the similar requirement. Basically a PCIe hierarchy is hidden
>>> behind a parent PCIe device, so we need to use the PCIe irqs on parent
>>> to de-multiple PCIe IRQs from hidden PCIe devices. Seems a chance for
>>> consolidation here.
>>
>> Do you know if there is a 1-1 mapping between the interrupts seen by the
>> parent device and those seen by the hidden devices? Or is it a case of
>> having to demultiplex the MSIs? Looks like the former, but I'd like to
>> be sure.
> 
> Yes, it's a demultiplexer. No 1:1 mapping.

Right. This doesn't exactly fit the scheme I have so far (there is a 1:1
mapping between the wired interrupt and the MSI), but once we are able
to expose an MSI domain, it could be possible to construct the MSI
demultiplexer on top. That's a lot of layers! ;-)

>> Sure, will do when I repost this (probably in a few weeks), and assuming
>> this fits the bill for Thomas and the MBIGEN folks.
> 
> It doesn't look that bad and the resulting mbigen stuff is way less
> horrible than it was before. So I agree this is a possible solution to
> the problem.

Cool. I'll revisit that after the merge window.

Thanks,

	M.
-- 
Jazz is not dead. It just smells funny...

WARNING: multiple messages have this Message-ID (diff)
From: marc.zyngier@arm.com (Marc Zyngier)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH RFC 0/7] Adding core support for wire-MSI bridges
Date: Thu, 05 Nov 2015 12:22:08 +0000	[thread overview]
Message-ID: <563B49F0.7040000@arm.com> (raw)
In-Reply-To: <alpine.DEB.2.11.1511041348060.4032@nanos>

On 04/11/15 13:34, Thomas Gleixner wrote:
> Marc,
> 
> On Fri, 16 Oct 2015, Marc Zyngier wrote:
>> On 16/10/15 02:55, Jiang Liu wrote:
>>> 	There's a working to enable Intel VMD storage device, which
>>> has the similar requirement. Basically a PCIe hierarchy is hidden
>>> behind a parent PCIe device, so we need to use the PCIe irqs on parent
>>> to de-multiple PCIe IRQs from hidden PCIe devices. Seems a chance for
>>> consolidation here.
>>
>> Do you know if there is a 1-1 mapping between the interrupts seen by the
>> parent device and those seen by the hidden devices? Or is it a case of
>> having to demultiplex the MSIs? Looks like the former, but I'd like to
>> be sure.
> 
> Yes, it's a demultiplexer. No 1:1 mapping.

Right. This doesn't exactly fit the scheme I have so far (there is a 1:1
mapping between the wired interrupt and the MSI), but once we are able
to expose an MSI domain, it could be possible to construct the MSI
demultiplexer on top. That's a lot of layers! ;-)

>> Sure, will do when I repost this (probably in a few weeks), and assuming
>> this fits the bill for Thomas and the MBIGEN folks.
> 
> It doesn't look that bad and the resulting mbigen stuff is way less
> horrible than it was before. So I agree this is a possible solution to
> the problem.

Cool. I'll revisit that after the merge window.

Thanks,

	M.
-- 
Jazz is not dead. It just smells funny...

  reply	other threads:[~2015-11-05 12:22 UTC|newest]

Thread overview: 64+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-10-15 15:39 [PATCH RFC 0/7] Adding core support for wire-MSI bridges Marc Zyngier
2015-10-15 15:39 ` Marc Zyngier
2015-10-15 15:39 ` [PATCH RFC 1/7] platform-msi: Allow MSIs to be allocated in chunks Marc Zyngier
2015-10-15 15:39   ` Marc Zyngier
2015-10-15 15:39 ` [PATCH RFC 2/7] platform-msi: Factor out allocation/free of private data Marc Zyngier
2015-10-15 15:39   ` Marc Zyngier
2015-10-16  5:46   ` Jiang Liu
2015-10-16  5:46     ` Jiang Liu
2015-10-16  8:50     ` Marc Zyngier
2015-10-16  8:50       ` Marc Zyngier
2015-10-15 15:39 ` [PATCH RFC 3/7] irqdomain: Make irq_domain_alloc_irqs_recursive available Marc Zyngier
2015-10-15 15:39   ` Marc Zyngier
2015-10-15 15:39 ` [PATCH RFC 4/7] genirq/msi: Make the .prepare callback reusable Marc Zyngier
2015-10-15 15:39   ` Marc Zyngier
2015-10-15 17:24   ` Gabriele Paoloni
2015-10-15 17:24     ` Gabriele Paoloni
2015-10-15 17:24     ` Gabriele Paoloni
2015-10-15 17:39     ` Marc Zyngier
2015-10-15 17:39       ` Marc Zyngier
2015-10-16 13:07       ` Gabriele Paoloni
2015-10-16 13:07         ` Gabriele Paoloni
2015-10-16 13:07         ` Gabriele Paoloni
2015-10-16  5:45   ` Jiang Liu
2015-10-16  5:45     ` Jiang Liu
2015-10-16  8:48     ` Marc Zyngier
2015-10-16  8:48       ` Marc Zyngier
2015-10-15 15:39 ` [PATCH RFC 5/7] genirq/msi: Add msi_domain_populate_irqs Marc Zyngier
2015-10-15 15:39   ` Marc Zyngier
2015-10-15 15:39 ` [PATCH RFC 6/7] platform-msi: Allow creation of a MSI-based stacked irq domain Marc Zyngier
2015-10-15 15:39   ` Marc Zyngier
2015-10-15 15:39 ` [PATCH RFC 7/7] irqchip: [Example] dummy wired interrupt/MSI bridge driver Marc Zyngier
2015-10-15 15:39   ` Marc Zyngier
2015-11-04  8:00   ` majun (F)
2015-11-04  8:00     ` majun (F)
2015-11-04  9:03     ` Marc Zyngier
2015-11-04  9:03       ` Marc Zyngier
2015-11-05  8:25       ` Gabriele Paoloni
2015-11-05  8:25         ` Gabriele Paoloni
2015-11-05  8:25         ` Gabriele Paoloni
2015-11-05  9:35         ` Marc Zyngier
2015-11-05  9:35           ` Marc Zyngier
2015-11-05  9:43           ` Gabriele Paoloni
2015-11-05  9:43             ` Gabriele Paoloni
2015-11-05  9:43             ` Gabriele Paoloni
2015-10-15 15:46 ` [PATCH RFC 0/7] Adding core support for wire-MSI bridges Arnd Bergmann
2015-10-15 15:46   ` Arnd Bergmann
2015-10-15 16:01   ` Marc Zyngier
2015-10-15 16:01     ` Marc Zyngier
2015-10-15 19:16     ` Arnd Bergmann
2015-10-15 19:16       ` Arnd Bergmann
2015-10-16  8:03       ` Marc Zyngier
2015-10-16  8:03         ` Marc Zyngier
2015-10-16  8:45         ` Arnd Bergmann
2015-10-16  8:45           ` Arnd Bergmann
2015-10-16  1:55 ` Jiang Liu
2015-10-16  1:55   ` Jiang Liu
2015-10-16  8:48   ` Marc Zyngier
2015-10-16  8:48     ` Marc Zyngier
2015-11-04 13:34     ` Thomas Gleixner
2015-11-04 13:34       ` Thomas Gleixner
2015-11-05 12:22       ` Marc Zyngier [this message]
2015-11-05 12:22         ` Marc Zyngier
2015-11-05 12:25         ` Thomas Gleixner
2015-11-05 12:25           ` Thomas Gleixner

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=563B49F0.7040000@arm.com \
    --to=marc.zyngier@arm.com \
    --cc=jason@lakedaemon.net \
    --cc=jiang.liu@linux.intel.com \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-pci@vger.kernel.org \
    --cc=majun258@huawei.com \
    --cc=tglx@linutronix.de \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.