qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: "Alex Bennée" <alex.bennee@linaro.org>
To: Paolo Bonzini <pbonzini@redhat.com>
Cc: qemu-devel@nongnu.org, cota@braap.org
Subject: Re: [Qemu-devel] [PATCH 0/5] More thread sanitizer fixes and atomic.h improvements
Date: Fri, 21 Oct 2016 18:38:13 +0100	[thread overview]
Message-ID: <877f91fvqy.fsf@linaro.org> (raw)
In-Reply-To: <1476107947-31430-1-git-send-email-pbonzini@redhat.com>


Paolo Bonzini <pbonzini@redhat.com> writes:

> See each patch.  My attempt at fixing whatever I did when I obviously
> didn't know enough^W about the C11 memory model, and at setting a
> better example for future generations...

Are you posting a v2 of this? Alternatively I can slurp them into my
next patch set as I've got a whole bunch more tsan related fixes that
are not directly MTTCG related currently in my MTTCG tree:

  https://github.com/stsquad/qemu/commits/mttcg/base-patches-v5

>
> Paolo Bonzini (5):
>   atomic: introduce smp_mb_acquire and smp_mb_release
>   cpus: use atomic_read to read seqlock-protected variables
>   qemu-thread: use acquire/release to clarify semantics of QemuEvent
>   rcu: simplify memory barriers
>   atomic: base mb_read/mb_set on load-acquire and store-release
>
>  cpus.c                   |   9 +--
>  docs/atomics.txt         |  84 ++++++++++++++++------------
>  include/qemu/atomic.h    | 139 ++++++++++++++++++++---------------------------
>  util/qemu-thread-posix.c |  15 ++++-
>  util/qemu-thread-win32.c |  15 ++++-
>  util/rcu.c               |  11 ++--
>  6 files changed, 143 insertions(+), 130 deletions(-)


--
Alex Bennée

  parent reply	other threads:[~2016-10-21 17:38 UTC|newest]

Thread overview: 26+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-10-10 13:59 [Qemu-devel] [PATCH 0/5] More thread sanitizer fixes and atomic.h improvements Paolo Bonzini
2016-10-10 13:59 ` [Qemu-devel] [PATCH 1/5] atomic: introduce smp_mb_acquire and smp_mb_release Paolo Bonzini
2016-10-10 15:29   ` Eric Blake
2016-10-10 16:38     ` Paolo Bonzini
2016-10-10 13:59 ` [Qemu-devel] [PATCH 2/5] cpus: use atomic_read to read seqlock-protected variables Paolo Bonzini
2016-10-12  8:44   ` Alex Bennée
2016-10-13 19:20   ` Emilio G. Cota
2016-10-13 20:45     ` Paolo Bonzini
2016-10-10 13:59 ` [Qemu-devel] [PATCH 3/5] qemu-thread: use acquire/release to clarify semantics of QemuEvent Paolo Bonzini
2016-10-12  9:21   ` Alex Bennée
2016-10-12  9:31     ` Paolo Bonzini
2016-10-10 13:59 ` [Qemu-devel] [PATCH 4/5] rcu: simplify memory barriers Paolo Bonzini
2016-10-10 13:59 ` [Qemu-devel] [PATCH 5/5] atomic: base mb_read/mb_set on load-acquire and store-release Paolo Bonzini
2016-10-12  9:28   ` Alex Bennée
2016-10-12  9:30     ` Paolo Bonzini
2016-10-20 18:36   ` Pranith Kumar
2016-10-10 16:53 ` [Qemu-devel] [PATCH 0/5] More thread sanitizer fixes and atomic.h improvements no-reply
2016-10-11 19:21 ` no-reply
2016-10-12 11:32 ` Alex Bennée
2016-10-12 11:34   ` Paolo Bonzini
2016-10-12 22:45 ` Emilio G. Cota
2016-10-13  7:39   ` Paolo Bonzini
2016-10-13 19:29     ` Emilio G. Cota
2016-10-14  9:55       ` Paolo Bonzini
2016-10-21 17:38 ` Alex Bennée [this message]
2016-10-22  9:10   ` Paolo Bonzini

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=877f91fvqy.fsf@linaro.org \
    --to=alex.bennee@linaro.org \
    --cc=cota@braap.org \
    --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).