From: Pekka Riikonen <priikone@iki.fi>
To: anatoly.burakov@intel.com
Cc: Dev <dev@dpdk.org>
Subject: [PATCH v2] bus/pci: fix automatic interrupt type selection
Date: Fri, 20 Jun 2025 15:50:27 +0300 [thread overview]
Message-ID: <d612fb276b9c8b173a5e476ca75b0460@iki.fi> (raw)
Check if kernel returns 0 interrupt vectors and try another interrupt
type in that case. Failing to check the vector count can select an
interrupt type that's unusable.
Signed-off-by: Pekka Riikonen <priikone@iki.fi>
---
drivers/bus/pci/linux/pci_vfio.c | 4 ++++
1 file changed, 4 insertions(+)
diff --git a/drivers/bus/pci/linux/pci_vfio.c
b/drivers/bus/pci/linux/pci_vfio.c
index 5317170231..02e7d7e40b 100644
--- a/drivers/bus/pci/linux/pci_vfio.c
+++ b/drivers/bus/pci/linux/pci_vfio.c
@@ -237,6 +237,10 @@ pci_vfio_setup_interrupts(struct rte_pci_device
*dev, int vfio_dev_fd)
continue;
}
+ /* If no vectors, try another one */
+ if (irq.count == 0)
+ continue;
+
/* Reallocate the efds and elist fields of intr_handle based
* on PCI device MSIX size.
*/
--
2.34.1
reply other threads:[~2025-06-20 12:50 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=d612fb276b9c8b173a5e476ca75b0460@iki.fi \
--to=priikone@iki.fi \
--cc=anatoly.burakov@intel.com \
--cc=dev@dpdk.org \
/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).