From: Stefan Hajnoczi <stefanha@gmail.com>
To: Bug 1771042 <1771042@bugs.launchpad.net>
Cc: qemu-devel@nongnu.org, Paolo Bonzini <pbonzini@redhat.com>
Subject: Re: [Qemu-devel] [Bug 1771042] Re: dataplane interrupt handler doesn't support msi
Date: Mon, 14 May 2018 15:06:06 +0100 [thread overview]
Message-ID: <20180514140606.GF5182@stefanha-x1.localdomain> (raw)
In-Reply-To: <152626684503.26828.16869042301439556281.malone@chaenomeles.canonical.com>
[-- Attachment #1: Type: text/plain, Size: 997 bytes --]
On Mon, May 14, 2018 at 03:00:44AM -0000, eric hoffman wrote:
> diff --git a/hw/block/dataplane/virtio-blk.c b/hw/block/dataplane/virtio-blk.c
> index 101f32c..31d9eb8 100644
> --- a/hw/block/dataplane/virtio-blk.c
> +++ b/hw/block/dataplane/virtio-blk.c
> @@ -73,7 +73,7 @@ static void notify_guest_bh(void *opaque)
> unsigned i = j + ctzl(bits);
> VirtQueue *vq = virtio_get_queue(s->vdev, i);
>
> - virtio_notify_irqfd(s->vdev, vq);
> + virtio_notify(s->vdev, vq);
>
> bits &= bits - 1; /* clear right-most bit */
> }
Please send patches to qemu-devel@nongnu.org. Guidelines for submitting
patches are here:
https://wiki.qemu.org/Contribute/SubmitAPatch
The issue with this approach is that hw/pci/msi.c:msi_send_message()
invokes device emulation outside the QEMU global mutex (it calls into
the APIC to send MSIs). I've CCed Paolo Bonzini to check whether doing
this is thread-safe.
Stefan
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 455 bytes --]
next prev parent reply other threads:[~2018-05-14 14:06 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-05-14 0:13 [Qemu-devel] [Bug 1771042] [NEW] dataplane interrupt handler doesn't support msi eric hoffman
2018-05-14 3:00 ` [Qemu-devel] [Bug 1771042] " eric hoffman
2018-05-14 14:06 ` Stefan Hajnoczi [this message]
2018-05-14 3:48 ` eric hoffman
2018-05-14 18:30 ` eric hoffman
2020-11-24 16:27 ` Thomas Huth
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=20180514140606.GF5182@stefanha-x1.localdomain \
--to=stefanha@gmail.com \
--cc=1771042@bugs.launchpad.net \
--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).