From: Alvise Rigo <a.rigo@virtualopensystems.com>
To: qemu-devel@nongnu.org, a.motakis@virtualopensystems.com,
eric.auger@st.com, kim.phillips@linaro.org
Cc: Alex Williamson <alex.williamson@redhat.com>,
tech@virtualopensystems.com,
Alvise Rigo <a.rigo@virtualopensystems.com>
Subject: [Qemu-devel] [RFC v2 4/4] Always use eventfd as notifying mechanism
Date: Sun, 11 May 2014 19:13:35 +0200 [thread overview]
Message-ID: <1399828415-13007-5-git-send-email-a.rigo@virtualopensystems.com> (raw)
In-Reply-To: <1399828415-13007-1-git-send-email-a.rigo@virtualopensystems.com>
When eventfd is not configured the method event_notifier_init fallbacks
to the pipe/pipe2 system call, causing an error in VFIO_DEVICE_SET_IRQS
since we pass to the kernel a file descriptor which is not created by
eventfd.
Signed-off-by: Alvise Rigo <a.rigo@virtualopensystems.com>
---
hw/vfio/platform.c | 5 +++++
1 file changed, 5 insertions(+)
diff --git a/hw/vfio/platform.c b/hw/vfio/platform.c
index ec6a29e..40109c6 100644
--- a/hw/vfio/platform.c
+++ b/hw/vfio/platform.c
@@ -324,6 +324,11 @@ static int vfio_enable_intp(VFIODevice *vdev, unsigned int index)
sysbus_init_irq(sbdev, &intp->qemuirq);
ret = event_notifier_init(&intp->interrupt, 0);
+ if (!ret && (intp->interrupt.rfd != intp->interrupt.wfd)) {
+ /* event_notifier_init created a pipe instead of eventfd */
+ ret = -1;
+ }
+
if (ret) {
error_report("vfio: Error: event_notifier_init failed ");
return ret;
--
1.9.1
prev parent reply other threads:[~2014-05-11 17:14 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-05-11 17:13 [Qemu-devel] [RFC v2 0/4] AMBA platform device passthrough Alvise Rigo
2014-05-11 17:13 ` [Qemu-devel] [RFC v2 1/4] Add EXEC_FLAG to VFIO DMA mappings Alvise Rigo
2014-05-23 8:40 ` Eric Auger
2014-05-11 17:13 ` [Qemu-devel] [RFC v2 2/4] Add AMBA devices support to VFIO Alvise Rigo
2014-05-11 17:13 ` [Qemu-devel] [RFC v2 3/4] MemoryRegion with EOI callbacks for VFIO Platform devices Alvise Rigo
2014-05-11 17:13 ` Alvise Rigo [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=1399828415-13007-5-git-send-email-a.rigo@virtualopensystems.com \
--to=a.rigo@virtualopensystems.com \
--cc=a.motakis@virtualopensystems.com \
--cc=alex.williamson@redhat.com \
--cc=eric.auger@st.com \
--cc=kim.phillips@linaro.org \
--cc=qemu-devel@nongnu.org \
--cc=tech@virtualopensystems.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).