From: Damien Le Moal <dlemoal@kernel.org>
To: linux-nvme@lists.infradead.org, Keith Busch <kbusch@kernel.org>,
Christoph Hellwig <hch@lst.de>, Sagi Grimberg <sagi@grimberg.me>,
Chaitanya Kulkarni <kch@nvidia.com>
Subject: [PATCH v2 0/5] nvmet pci-epf fixes
Date: Fri, 9 May 2025 08:24:59 +0900 [thread overview]
Message-ID: <20250508232504.437470-1-dlemoal@kernel.org> (raw)
Five patches to fix and improve IRQ handling in the PCI endpoint target
driver. The issues fixed by the first 2 patches where discovered with
testing with polling queues set on the host side. The following 2
patches are small improvements/cleanup in the same IRQ handling area.
The last patch removes dead code.
Changes from v1:
- Fixed typos in patch 1 and 2
- Removed Fixes tag from patch 2 as a backport to 6.14 would lead to
compilation errors
- Added Review tags to patch 3 and 4
- Added patch 5
Damien Le Moal (5):
nvmet: pci-epf: Clear completion queue IRQ flag on delete
nvmet: pci-epf: Do not fall back to using INTX if not supported
nvmet: pci-epf: Cleanup nvmet_pci_epf_raise_irq()
nvmet: pci-epf: Improve debug message
nvmet: pci-epf: Remove NVMET_PCI_EPF_Q_IS_SQ
drivers/nvme/target/pci-epf.c | 39 +++++++++++++++++++++--------------
1 file changed, 23 insertions(+), 16 deletions(-)
--
2.49.0
next reply other threads:[~2025-05-08 23:26 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-05-08 23:24 Damien Le Moal [this message]
2025-05-08 23:25 ` [PATCH v2 1/5] nvmet: pci-epf: Clear completion queue IRQ flag on delete Damien Le Moal
2025-05-08 23:25 ` [PATCH v2 2/5] nvmet: pci-epf: Do not fall back to using INTX if not supported Damien Le Moal
2025-05-08 23:25 ` [PATCH v2 3/5] nvmet: pci-epf: Cleanup nvmet_pci_epf_raise_irq() Damien Le Moal
2025-05-08 23:25 ` [PATCH v2 4/5] nvmet: pci-epf: Improve debug message Damien Le Moal
2025-05-08 23:25 ` [PATCH v2 5/5] nvmet: pci-epf: Remove NVMET_PCI_EPF_Q_IS_SQ Damien Le Moal
2025-05-09 4:58 ` [PATCH v2 0/5] nvmet pci-epf fixes Christoph Hellwig
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=20250508232504.437470-1-dlemoal@kernel.org \
--to=dlemoal@kernel.org \
--cc=hch@lst.de \
--cc=kbusch@kernel.org \
--cc=kch@nvidia.com \
--cc=linux-nvme@lists.infradead.org \
--cc=sagi@grimberg.me \
/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