From: Madhavan Srinivasan <maddy@linux.ibm.com>
To: Thomas Gleixner <tglx@linutronix.de>,
Nam Cao <namcao@linutronix.de>,
Michael Ellerman <mpe@ellerman.id.au>,
Nicholas Piggin <npiggin@gmail.com>,
Christophe Leroy <christophe.leroy@csgroup.eu>,
Marc Zyngier <maz@kernel.org>,
Gautam Menghani <gautam@linux.ibm.com>,
linuxppc-dev@lists.ozlabs.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2 0/3] powerpc: Cleanup and convert to MSI parent domain
Date: Sat, 6 Sep 2025 17:18:57 +0530 [thread overview]
Message-ID: <88359a18-7b82-41b5-b000-d4df837efd23@linux.ibm.com> (raw)
In-Reply-To: <87y0qvy6hb.ffs@tglx>
On 9/3/25 7:37 PM, Thomas Gleixner wrote:
> On Mon, Aug 11 2025 at 11:28, Nam Cao wrote:
>
>> The initial implementation of PCI/MSI interrupt domains in the hierarchical
>> interrupt domain model used a shortcut by providing a global PCI/MSI
>> domain.
>>
>> This works because the PCI/MSI[X] hardware is standardized and uniform, but
>> it violates the basic design principle of hierarchical interrupt domains:
>> Each hardware block involved in the interrupt delivery chain should have a
>> separate interrupt domain.
>>
>> For PCI/MSI[X], the interrupt controller is per PCI device and not a global
>> made-up entity.
>>
>> Unsurprisingly, the shortcut turned out to have downsides as it does not
>> allow dynamic allocation of interrupt vectors after initialization and it
>> prevents supporting IMS on PCI. For further details, see:
>>
>> https://lore.kernel.org/lkml/20221111120501.026511281@linutronix.de/
>>
>> The solution is implementing per device MSI domains, this means the
>> entities which provide global PCI/MSI domain so far have to implement MSI
>> parent domain functionality instead.
>>
>> This series:
>>
>> - Untangle XIVE driver from Powernv and Pseries drivers
>>
>> - Convert the Powernv and Pseries drivers to implement MSI parent domain
>> functionality
>
> Polite reminder to the PPC folks. Can we please get this moving so we
> can finally cleanup the pci_msi_create_irq_domain() leftovers?
Yes, sorry for the delay,
Will add this to my next after the test
Maddy
>
> Thanks,
>
> tglx
next prev parent reply other threads:[~2025-09-06 11:49 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-08-11 9:28 Nam Cao
2025-08-11 9:28 ` [PATCH v2 1/3] powerpc/xive: Untangle xive from child interrupt controller drivers Nam Cao
2025-10-07 3:24 ` Ritesh Harjani
2025-10-07 5:24 ` Nam Cao
2025-10-07 15:08 ` Nam Cao
2025-08-11 9:28 ` [PATCH v2 2/3] powerpc/powernv/pci: Switch to use msi_create_parent_irq_domain() Nam Cao
2025-08-11 9:28 ` [PATCH v2 3/3] powerpc/pseries/msi: Switch to msi_create_parent_irq_domain() Nam Cao
2025-09-03 14:07 ` [PATCH v2 0/3] powerpc: Cleanup and convert to MSI parent domain Thomas Gleixner
2025-09-06 11:48 ` Madhavan Srinivasan [this message]
2025-09-12 3:56 ` Madhavan Srinivasan
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=88359a18-7b82-41b5-b000-d4df837efd23@linux.ibm.com \
--to=maddy@linux.ibm.com \
--cc=christophe.leroy@csgroup.eu \
--cc=gautam@linux.ibm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=maz@kernel.org \
--cc=mpe@ellerman.id.au \
--cc=namcao@linutronix.de \
--cc=npiggin@gmail.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®