From: Maciej Szwed <maciej.szwed@intel.com>
To: dev@dpdk.org
Cc: hkalra@marvell.com, anatoly.burakov@intel.com, jia.guo@intel.com,
david.marchand@redhat.com, Maciej Szwed <maciej.szwed@intel.com>
Subject: [dpdk-dev] [PATCH v6] eal: fix: read data buffer on RTE_INTR_HANDLE_VFIO_REQ
Date: Tue, 19 Oct 2021 12:06:57 +0200 [thread overview]
Message-ID: <20211019100657.692706-1-maciej.szwed@intel.com> (raw)
In-Reply-To: <BL0PR11MB29484DF93707E906EDFABEAD97C49@BL0PR11MB2948.namprd11.prod.outlook.com>
We should call read() on RTE_INTR_HANDLE_VFIO_REQ event
to confirm that event.
Signed-off-by: Maciej Szwed <maciej.szwed@intel.com>
---
lib/eal/linux/eal_interrupts.c | 9 +++------
1 file changed, 3 insertions(+), 6 deletions(-)
diff --git a/lib/eal/linux/eal_interrupts.c b/lib/eal/linux/eal_interrupts.c
index 22b3b7bcd9..7c716a3812 100644
--- a/lib/eal/linux/eal_interrupts.c
+++ b/lib/eal/linux/eal_interrupts.c
@@ -918,17 +918,14 @@ eal_intr_process_interrupts(struct epoll_event *events, int nfds)
bytes_read = sizeof(buf.timerfd_num);
break;
#ifdef VFIO_PRESENT
+#ifdef HAVE_VFIO_DEV_REQ_INTERFACE
+ case RTE_INTR_HANDLE_VFIO_REQ:
+#endif
case RTE_INTR_HANDLE_VFIO_MSIX:
case RTE_INTR_HANDLE_VFIO_MSI:
case RTE_INTR_HANDLE_VFIO_LEGACY:
bytes_read = sizeof(buf.vfio_intr_count);
break;
-#ifdef HAVE_VFIO_DEV_REQ_INTERFACE
- case RTE_INTR_HANDLE_VFIO_REQ:
- bytes_read = 0;
- call = true;
- break;
-#endif
#endif
case RTE_INTR_HANDLE_VDEV:
case RTE_INTR_HANDLE_EXT:
--
2.27.0
next prev parent reply other threads:[~2021-10-19 10:42 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-08-23 14:17 [dpdk-dev] [PATCH v2] eal: " Szwed, Maciej
2021-08-24 9:26 ` [dpdk-dev] [PATCH v3] " Maciej Szwed
2021-08-24 9:55 ` [dpdk-dev] [PATCH v4] " Maciej Szwed
2021-10-14 13:06 ` David Marchand
2021-10-19 9:51 ` [dpdk-dev] [PATCH v5] eal: fix: " Maciej Szwed
2021-10-19 10:06 ` Maciej Szwed [this message]
2021-10-19 11:52 ` [dpdk-dev] [PATCH v6] " David Marchand
2021-11-08 17:29 ` David Marchand
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=20211019100657.692706-1-maciej.szwed@intel.com \
--to=maciej.szwed@intel.com \
--cc=anatoly.burakov@intel.com \
--cc=david.marchand@redhat.com \
--cc=dev@dpdk.org \
--cc=hkalra@marvell.com \
--cc=jia.guo@intel.com \
/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).