linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Nilay Shroff <nilay@linux.ibm.com>
To: Nam Cao <namcao@linutronix.de>
Cc: linuxppc-dev@lists.ozlabs.org, maddy@linux.ibm.com,
	mpe@ellerman.id.au, npiggin@gmail.com,
	christophe.leroy@csgroup.eu, tglx@linutronix.de, maz@kernel.org,
	gautam@linux.ibm.com, Gregory Joyce <gjoyce@ibm.com>
Subject: Re: [bug report] powerpc: per device MSI irq domain
Date: Thu, 4 Dec 2025 22:54:50 +0530	[thread overview]
Message-ID: <f82d1224-509f-446c-8dee-13e28429b52b@linux.ibm.com> (raw)
In-Reply-To: <87qztawmiv.fsf@yellow.woof>



On 12/4/25 4:18 PM, Nam Cao wrote:
> Hi Nilay,
> 
> Nilay Shroff <nilay@linux.ibm.com> writes:
>> I have been using an NVMe disk on my PowerPC system that supports up to
>> 129 MSI-X interrupt vectors. Everything worked fine until Linux kernel
>> v6.18, after which the NVMe driver stopped detecting the disk because
>> the driver probe now fails.
>>
>> After further investigation, I found that the probe failure in v6.18
>> occurs during PCI/MSI-X vector allocation. A git bisect identified
>> commit daaa574aba6f (“powerpc/pseries/msi: Switch to msi_create_parent_
>> irq_domain()”) as the first bad commit.
> 
> Thanks for the report. I can (kind of) reproduce the problem with QEMU.
> 
> I think moving rtas_prepare_msi_irqs() into pseries_irq_domain_alloc()
> should resolve the problem. But I'm not sure because I don't understand
> how RTAS works.
> 
> Does IBM have some documentation describing the RTAS API? I failed to
> google it.

Yes you can find the architecture document here: 
https://github.com/linuxppc/public-docs/blob/main/LoPAPR/LoPAR-20200812.pdf

You may refer section 7 in the above document, which describes RTAS API.

Thanks,--Nilay


  reply	other threads:[~2025-12-04 17:26 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-12-02 11:17 [bug report] powerpc: per device MSI irq domain Nilay Shroff
2025-12-04 10:48 ` Nam Cao
2025-12-04 17:24   ` Nilay Shroff [this message]
2025-12-06 14:38     ` Nam Cao
2025-12-08 12:03       ` Nilay Shroff

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=f82d1224-509f-446c-8dee-13e28429b52b@linux.ibm.com \
    --to=nilay@linux.ibm.com \
    --cc=christophe.leroy@csgroup.eu \
    --cc=gautam@linux.ibm.com \
    --cc=gjoyce@ibm.com \
    --cc=linuxppc-dev@lists.ozlabs.org \
    --cc=maddy@linux.ibm.com \
    --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;
as well as URLs for NNTP newsgroup(s).