From: "Michael S. Tsirkin" <mst@redhat.com>
To: Davide Libenzi <davidel@xmailserver.org>,
"Michael S. Tsirkin" <mst@redhat.com>,
Avi Kivity <avi@redhat.com>,
kvm@vger.kernel.org,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: [PATCH 0/2] kvm: fix spurious interrupt with irqfd
Date: Wed, 13 Jan 2010 19:12:22 +0200 [thread overview]
Message-ID: <20100113171222.GA19798@redhat.com> (raw)
Deassigning irqfd and assigning back caused spurious interrupt. fix this
by clearing the counter on deassign. This is on top of davidel's patch
which makes clearing eventfd counter from modules possible.
Michael S. Tsirkin (2):
kvm: fix spurious interrupt with irqfd
kvm: do not store wqh in irqfd
virt/kvm/eventfd.c | 6 ++----
1 files changed, 2 insertions(+), 4 deletions(-)
next reply other threads:[~2010-01-13 17:15 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-01-13 17:12 Michael S. Tsirkin [this message]
2010-01-17 12:42 ` [PATCH 0/2] kvm: fix spurious interrupt with irqfd Avi Kivity
2010-01-19 14:52 ` Michael S. Tsirkin
2010-01-20 14:10 ` Avi Kivity
2010-01-20 14:58 ` Michael S. Tsirkin
2010-01-20 15:09 ` Avi Kivity
2010-01-20 15:09 ` Michael S. Tsirkin
2010-01-20 17:19 ` Davide Libenzi
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=20100113171222.GA19798@redhat.com \
--to=mst@redhat.com \
--cc=avi@redhat.com \
--cc=davidel@xmailserver.org \
--cc=kvm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.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