From: "Michael S. Tsirkin" <mst@redhat.com>
To: qemu-devel@nongnu.org, Anthony Liguori <anthony@codemonkey.ws>,
Paul Brook <paul@codesourcery.com>
Subject: [Qemu-devel] Re: [PATCH-RFC 0/3] qemu: memory barriers in virtio
Date: Tue, 22 Dec 2009 13:26:01 +0200 [thread overview]
Message-ID: <20091222112601.GA16053@redhat.com> (raw)
In-Reply-To: <20091208161818.GA32188@redhat.com>
On Tue, Dec 08, 2009 at 06:18:18PM +0200, Michael S. Tsirkin wrote:
> The following fixes a class of long-standing bugs in qemu:
> when kvm is enabled, guest might access device structures
> in memory while they are updated by qemu on another CPU.
> In this scenario, memory barriers are necessary to prevent
> host CPU from reordering memory accesses, which might confuse
> the guest.
>
> This patch only fixes virtio, but other emulated devices
> might have a similar bug. They'll need to be discovered
> and addressed case by case.
>
> This is still under test ... meanwhile: any early feedback/flames?
>
Any comments on this one?
The patch works fine in my testing, and even though
it did not fix a crash that I hoped it will fix,
it seems required for correctness... Right?
> Michael S. Tsirkin (3):
> qemu: add barriers.h header
> virtio: use a real wmb
> virtio: add missing barriers
>
> hw/barriers.h | 131 +++++++++++++++++++++++++++++++++++++++++++++++++++++++++
> hw/virtio.c | 18 ++++----
> 2 files changed, 139 insertions(+), 10 deletions(-)
> create mode 100644 hw/barriers.h
>
next prev parent reply other threads:[~2009-12-22 11:29 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-12-08 16:18 [Qemu-devel] [PATCH-RFC 0/3] qemu: memory barriers in virtio Michael S. Tsirkin
2009-12-22 11:26 ` Michael S. Tsirkin [this message]
2009-12-22 14:51 ` [Qemu-devel] " Anthony Liguori
2009-12-22 16:25 ` Paul Brook
2009-12-22 16:34 ` Michael S. Tsirkin
2009-12-22 22:58 ` Paul Brook
2009-12-22 17:28 ` Avi Kivity
[not found] ` <200912231704.19449.rusty@rustcorp.com.au>
[not found] ` <20091223163600.GD6588@redhat.com>
2010-01-04 2:07 ` Rusty Russell
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=20091222112601.GA16053@redhat.com \
--to=mst@redhat.com \
--cc=anthony@codemonkey.ws \
--cc=paul@codesourcery.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).