From: Ladi Prosek <lprosek@redhat.com>
To: qemu-devel@nongnu.org
Cc: pbonzini@redhat.com, armbru@redhat.com,
marcandre.lureau@redhat.com, geoff@hostfission.com,
eblake@redhat.com
Subject: [Qemu-devel] [PATCH v4 0/4] ivshmem: MSI bug fixes
Date: Mon, 11 Dec 2017 08:21:06 +0100 [thread overview]
Message-ID: <20171211072110.9058-1-lprosek@redhat.com> (raw)
Fixes bugs in the ivshmem device implementation uncovered with the new
Windows ivshmem driver:
https://github.com/virtio-win/kvm-guest-drivers-windows/tree/master/ivshmem
v1->v2:
* Patch 1 - added reproducer info to commit message (Markus)
* Patch 2 - restructured conditionals, fixed comment formatting (Markus)
* Patch 3 - added reproducer info to commit message (Markus)
v2->v3:
* Added patch 4
v3->v4:
* Added forward decl of ivshmem_disable_irqfd() instead of moving
ivshmem_reset() (Eric, Markus)
Ladi Prosek (4):
ivshmem: Don't update non-existent MSI routes
ivshmem: Always remove irqfd notifiers
ivshmem: Improve MSI irqfd error handling
ivshmem: Disable irqfd on device reset
hw/misc/ivshmem.c | 81 ++++++++++++++++++++++++++++++++++++++++++-------------
1 file changed, 62 insertions(+), 19 deletions(-)
--
2.13.6
next reply other threads:[~2017-12-11 7:21 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-12-11 7:21 Ladi Prosek [this message]
2017-12-11 7:21 ` [Qemu-devel] [PATCH v4 1/4] ivshmem: Don't update non-existent MSI routes Ladi Prosek
2017-12-11 7:21 ` [Qemu-devel] [PATCH v4 2/4] ivshmem: Always remove irqfd notifiers Ladi Prosek
2017-12-11 7:21 ` [Qemu-devel] [PATCH v4 3/4] ivshmem: Improve MSI irqfd error handling Ladi Prosek
2017-12-11 7:21 ` [Qemu-devel] [PATCH v4 4/4] ivshmem: Disable irqfd on device reset Ladi Prosek
2017-12-11 19:02 ` Markus Armbruster
2018-01-30 18:30 ` [Qemu-devel] [PATCH v4 0/4] ivshmem: MSI bug fixes Markus Armbruster
2018-01-30 19:52 ` Paolo Bonzini
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=20171211072110.9058-1-lprosek@redhat.com \
--to=lprosek@redhat.com \
--cc=armbru@redhat.com \
--cc=eblake@redhat.com \
--cc=geoff@hostfission.com \
--cc=marcandre.lureau@redhat.com \
--cc=pbonzini@redhat.com \
--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).