From: Dave Jiang <dave.jiang@intel.com>
To: Koichiro Den <den@valinux.co.jp>, Jon Mason <jdmason@kudzu.us>,
Allen Hubbe <allenbh@gmail.com>,
Jerome Brunet <jbrunet@baylibre.com>, Frank Li <Frank.Li@nxp.com>,
Kishon Vijay Abraham I <kishon@kernel.org>,
Bjorn Helgaas <bhelgaas@google.com>,
Lorenzo Pieralisi <lpieralisi@kernel.org>
Cc: ntb@lists.linux.dev, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 0/2] NTB: epf: Fix ntb_hw_epf ISR issues
Date: Wed, 18 Mar 2026 12:51:39 -0700 [thread overview]
Message-ID: <d931ce45-b3c8-4cb7-80ec-7acadf26a22d@intel.com> (raw)
In-Reply-To: <wzv676qh2bahuptnzhhyywt2ihuz7xn2j7mcm6heqoweqz564v@mx66vyni2vyd>
On 3/16/26 8:01 PM, Koichiro Den wrote:
> On Wed, Mar 04, 2026 at 05:30:26PM +0900, Koichiro Den wrote:
>> ntb_hw_epf handles doorbell interrupts using multiple MSI/MSI-X vectors.
>> This small patch series is to address two issues in the interrupt
>> setup/handler path:
>>
>> 1) ntb_epf_init_isr() does not unwind already requested IRQs when
>> request_irq() fails part-way through the vector loop.
>>
>> 2) ntb_epf_vec_isr() calls pci_irq_vector() in hardirq context to
>> derive the vector number. pci_irq_vector() performs an MSI domain
>> lookup (msi_get_virq()) that takes a mutex, which can trigger
>> "scheduling while atomic" splats.
>>
>> Patch 1 fixes the request_irq() unwind path.
>> Patch 2 caches the Linux IRQ number for vector 0 and uses it as a base in
>> the ISR, avoiding pci_irq_vector() from hardirq context.
>>
>> Both patches are Cc'd to stable (v5.12+).
>>
>> Best regards,
>> Koichiro
>>
>> Koichiro Den (2):
>> NTB: epf: Fix request_irq() unwind in ntb_epf_init_isr()
>> NTB: epf: Avoid pci_irq_vector() from hardirq context
>
> Jon or Dave,
>
> Gentle ping on this series.
> I would appreciate it if you could take a look when you have a chance.
For the series, LGTM
Reviewed-by: Dave Jiang <dave.jiang@intel.com>
>
> Best regards,
> Koichiro
>
>>
>> drivers/ntb/hw/epf/ntb_hw_epf.c | 14 +++++++-------
>> 1 file changed, 7 insertions(+), 7 deletions(-)
>>
>> --
>> 2.51.0
>>
>>
prev parent reply other threads:[~2026-03-18 19:51 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-03-04 8:30 [PATCH 0/2] NTB: epf: Fix ntb_hw_epf ISR issues Koichiro Den
2026-03-04 8:30 ` [PATCH 1/2] NTB: epf: Fix request_irq() unwind in ntb_epf_init_isr() Koichiro Den
2026-03-04 8:30 ` [PATCH 2/2] NTB: epf: Avoid pci_irq_vector() from hardirq context Koichiro Den
2026-03-17 3:01 ` [PATCH 0/2] NTB: epf: Fix ntb_hw_epf ISR issues Koichiro Den
2026-03-18 19:51 ` Dave Jiang [this message]
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=d931ce45-b3c8-4cb7-80ec-7acadf26a22d@intel.com \
--to=dave.jiang@intel.com \
--cc=Frank.Li@nxp.com \
--cc=allenbh@gmail.com \
--cc=bhelgaas@google.com \
--cc=den@valinux.co.jp \
--cc=jbrunet@baylibre.com \
--cc=jdmason@kudzu.us \
--cc=kishon@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=lpieralisi@kernel.org \
--cc=ntb@lists.linux.dev \
/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