From: Eric Auger <eric.auger@linaro.org>
To: eric.auger@st.com, eric.auger@linaro.org, qemu-devel@nongnu.org,
alex.williamson@redhat.com
Cc: christoffer.dall@linaro.org, patches@linaro.org
Subject: [Qemu-devel] [PATCH v2 0/3] hw/vfio/platform: irqfd setup changes
Date: Thu, 24 Sep 2015 21:08:36 +0100 [thread overview]
Message-ID: <1443125319-16691-1-git-send-email-eric.auger@linaro.org> (raw)
This series fixes a bug related to irqfd setup for edge sensitive IRQs
and proposes a new startup sequence for irqfd signaling.
The current startup sequence brings some issues with respect to the
oncoming ARM IRQ forwarding support. The new startup sequence starts
either irqfd signaling or eventfd signaling and there is no risk the
IRQ is active nor masked when irqfd/IRQ forwarding is setup.
---
v1 -> v2:
- add "hw/vfio/platform: change interrupt/unmask fields into pointer"
- introduce vfio_irq_is_automasked helper function and for edge-sensitive
IRQs, do not allocate/initialize unmask EventNotifier nor call
vfio_set_resample_eventfd
Eric Auger (3):
hw/vfio/platform: irqfd setup sequence update
hw/vfio/platform: change interrupt/unmask fields into pointer
hw/vfio/platform: do not set resamplefd for edge-sensitive IRQS
hw/vfio/platform.c | 116 ++++++++++++++++++++++++----------------
include/hw/vfio/vfio-platform.h | 4 +-
trace-events | 4 +-
3 files changed, 75 insertions(+), 49 deletions(-)
--
1.8.3.2
next reply other threads:[~2015-09-24 20:08 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-09-24 20:08 Eric Auger [this message]
2015-09-24 20:08 ` [Qemu-devel] [PATCH v2 1/3] hw/vfio/platform: irqfd setup sequence update Eric Auger
2015-09-24 20:08 ` [Qemu-devel] [PATCH v2 2/3] hw/vfio/platform: change interrupt/unmask fields into pointer Eric Auger
2015-09-24 20:08 ` [Qemu-devel] [PATCH v2 3/3] hw/vfio/platform: do not set resamplefd for edge-sensitive IRQS Eric Auger
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=1443125319-16691-1-git-send-email-eric.auger@linaro.org \
--to=eric.auger@linaro.org \
--cc=alex.williamson@redhat.com \
--cc=christoffer.dall@linaro.org \
--cc=eric.auger@st.com \
--cc=patches@linaro.org \
--cc=qemu-devel@nongnu.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).