From: Kevin Wolf <kwolf@redhat.com>
To: Keith Busch <keith.busch@intel.com>
Cc: qemu-block@nongnu.org, qemu-devel@nongnu.org,
Max Reitz <mreitz@redhat.com>, Guenter Roeck <linux@roeck-us.net>
Subject: Re: [Qemu-devel] [PATCH] nvme: Fix spurious interrupts
Date: Mon, 26 Nov 2018 18:38:38 +0100 [thread overview]
Message-ID: <20181126173838.GD6612@localhost.localdomain> (raw)
In-Reply-To: <20181126171745.4673-1-keith.busch@intel.com>
Am 26.11.2018 um 18:17 hat Keith Busch geschrieben:
> The code had asserted an interrupt every time it was requested to check
> for new completion queue entries.This can result in spurious interrupts
> seen by the guest OS.
>
> Fix this by asserting an interrupt only if there are un-acknowledged
> completion queue entries available.
>
> Reported-by: Guenter Roeck <linux@roeck-us.net>
> Signed-off-by: Keith Busch <keith.busch@intel.com>
Thanks, applied to the block branch.
Kevin
prev parent reply other threads:[~2018-11-26 17:38 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-11-26 17:17 [Qemu-devel] [PATCH] nvme: Fix spurious interrupts Keith Busch
2018-11-26 17:28 ` Guenter Roeck
2018-11-26 17:38 ` Kevin Wolf [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=20181126173838.GD6612@localhost.localdomain \
--to=kwolf@redhat.com \
--cc=keith.busch@intel.com \
--cc=linux@roeck-us.net \
--cc=mreitz@redhat.com \
--cc=qemu-block@nongnu.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.