qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Anthony Liguori <anthony@codemonkey.ws>
To: "Michael S. Tsirkin" <mst@redhat.com>
Cc: Rusty Russell <rusty@rustcorp.com.au>,
	qemu-devel@nongnu.org, Paul Brook <paul@codesourcery.com>
Subject: [Qemu-devel] Re: [PATCH-RFC 0/3] qemu: memory barriers in virtio
Date: Tue, 22 Dec 2009 08:51:43 -0600	[thread overview]
Message-ID: <4B30DCFF.8050305@codemonkey.ws> (raw)
In-Reply-To: <20091222112601.GA16053@redhat.com>

On 12/22/2009 05:26 AM, Michael S. Tsirkin wrote:
> 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?
>    

It's definitely better than what we have.  Rusty mentioned something to 
me a bit ago about the barriers for virtio in the kernel needing some 
work.  I've been meaning to ask him about it in the context of this patch.

Rusty, am I remembering correctly or have I been sipping too much 
eggnog? :-)

Regards,

Anthony Liguori

  reply	other threads:[~2009-12-22 14:51 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 ` [Qemu-devel] " Michael S. Tsirkin
2009-12-22 14:51   ` Anthony Liguori [this message]
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=4B30DCFF.8050305@codemonkey.ws \
    --to=anthony@codemonkey.ws \
    --cc=mst@redhat.com \
    --cc=paul@codesourcery.com \
    --cc=qemu-devel@nongnu.org \
    --cc=rusty@rustcorp.com.au \
    /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).