qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: "Richard W.M. Jones" <rjones@redhat.com>
To: Paolo Bonzini <pbonzini@redhat.com>
Cc: Paul.Leveille@stratus.com, lersek@redhat.com,
	qemu-devel@nongnu.org, stefanha@redhat.com
Subject: Re: [Qemu-devel] [PATCH] aio: strengthen memory barriers for bottom half scheduling
Date: Wed, 8 Apr 2015 11:15:02 +0100	[thread overview]
Message-ID: <20150408101502.GA10777@redhat.com> (raw)
In-Reply-To: <1428419779-26062-1-git-send-email-pbonzini@redhat.com>

On Tue, Apr 07, 2015 at 05:16:19PM +0200, Paolo Bonzini wrote:
> This bug is, most likely, also the cause of failures in the libguestfs
> testsuite on AArch64.

I'm afraid I have to agree with Laszlo, that this patch unfortunately
does not cure the aarch64 race.

The test case I'm using is:
http://git.annexia.org/?p=rhbz1184405.git;a=tree

Note: This does not mean this patch is bad!  Just that it doesn't cure
the long-standing aarch64 race that we've been trying to fix forever,
which is what we were hoping.

Rich.

-- 
Richard Jones, Virtualization Group, Red Hat http://people.redhat.com/~rjones
Read my programming and virtualization blog: http://rwmj.wordpress.com
virt-builder quickly builds VMs from scratch
http://libguestfs.org/virt-builder.1.html

  parent reply	other threads:[~2015-04-08 10:15 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-04-07 15:16 [Qemu-devel] [PATCH] aio: strengthen memory barriers for bottom half scheduling Paolo Bonzini
2015-04-07 18:20 ` Leveille, Paul
2015-04-08  9:53   ` Laszlo Ersek
2015-04-08 10:15 ` Richard W.M. Jones [this message]
2015-04-08 10:34   ` Laszlo Ersek
2015-04-08 15:06 ` Stefan Hajnoczi
  -- strict thread matches above, loose matches on Subject: below --
2015-04-09  9:21 Paolo Bonzini
2015-04-09  9:29 ` Stefan Hajnoczi

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=20150408101502.GA10777@redhat.com \
    --to=rjones@redhat.com \
    --cc=Paul.Leveille@stratus.com \
    --cc=lersek@redhat.com \
    --cc=pbonzini@redhat.com \
    --cc=qemu-devel@nongnu.org \
    --cc=stefanha@redhat.com \
    /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).