From: Paolo Bonzini <pbonzini@redhat.com>
To: Richard Henderson <richard.henderson@linaro.org>, qemu-devel@nongnu.org
Cc: fangying1@huawei.com, stefanha@redhat.com
Subject: Re: [PATCH 2/5] atomics: update documentation
Date: Tue, 7 Apr 2020 17:52:59 +0200 [thread overview]
Message-ID: <bfec4cbd-bbbc-40ec-554b-53b0ffa38ba0@redhat.com> (raw)
In-Reply-To: <25ba1237-510d-cf4a-2b4f-c5fa1d715976@linaro.org>
On 07/04/20 17:25, Richard Henderson wrote:
> On 4/7/20 7:07 AM, Paolo Bonzini wrote:
>> +- release operations will appear to happen, with respect to the other
>> + components of the system, after all the LOAD or STORE operations
>> + specified afterwards.
> "specified before", not after for release.
Not the only one such pasto (e.g. "operations coming after
``atomic_store_release()`` can still be reordered before it", the text
said "after"). I have fixed all of them.
Paolo
next prev parent reply other threads:[~2020-04-07 16:03 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-04-07 14:07 [RFC PATCH 0/4] async: fix hangs on weakly-ordered architectures Paolo Bonzini
2020-04-07 14:07 ` [PATCH 1/5] atomics: convert to reStructuredText Paolo Bonzini
2020-04-07 16:49 ` Alex Bennée
2020-04-07 14:07 ` [PATCH 2/5] atomics: update documentation Paolo Bonzini
2020-04-07 15:25 ` Richard Henderson
2020-04-07 15:52 ` Paolo Bonzini [this message]
2020-04-07 14:07 ` [PATCH 3/5] rcu: do not mention atomic_mb_read/set in documentation Paolo Bonzini
2020-04-07 17:19 ` Richard Henderson
2020-04-07 14:07 ` [PATCH 4/5] aio-wait: delegate polling of main AioContext if BQL not held Paolo Bonzini
2020-04-07 14:07 ` [PATCH 5/5] async: use explicit memory barriers Paolo Bonzini
2020-04-09 6:22 ` Ying Fang
2020-04-08 9:12 ` [RFC PATCH 0/4] async: fix hangs on weakly-ordered architectures Ying Fang
2020-04-08 15:05 ` Paolo Bonzini
2020-04-09 6:54 ` Ying Fang
2020-04-09 15:17 ` 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=bfec4cbd-bbbc-40ec-554b-53b0ffa38ba0@redhat.com \
--to=pbonzini@redhat.com \
--cc=fangying1@huawei.com \
--cc=qemu-devel@nongnu.org \
--cc=richard.henderson@linaro.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).