From: "Paul E. McKenney" <paulmck@kernel.org>
To: Akira Yokosawa <akiyks@gmail.com>
Cc: perfbook@vger.kernel.org
Subject: Re: [PATCH -perfbook 2/2] memorder: Fix typo
Date: Wed, 28 Sep 2022 10:46:11 -0700 [thread overview]
Message-ID: <20220928174611.GA4196@paulmck-ThinkPad-P17-Gen-1> (raw)
In-Reply-To: <3ca9e48c-3049-1845-a849-d8484c47d645@gmail.com>
On Wed, Sep 28, 2022 at 11:30:40PM +0900, Akira Yokosawa wrote:
> Signed-off-by: Akira Yokosawa <akiyks@gmail.com>
Good catches, queued and pushed both, thank you!
Thanx, Paul
> ---
> Hi Paul,
>
> I don't see any smp_store_release() in P1().
> It must be P0(). :-)
>
> Thanks, Akira
> --
> memorder/memorder.tex | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/memorder/memorder.tex b/memorder/memorder.tex
> index f85cfe6ca702..a0a87d0a8bca 100644
> --- a/memorder/memorder.tex
> +++ b/memorder/memorder.tex
> @@ -2372,7 +2372,7 @@ The only code difference is that
> has an additional \co{P2()} that does an \co{smp_store_release()} to
> the \co{x2} variable that \co{P0()} releases and \co{P1()} acquires.
> The \co{exists} clause is also adjusted to exclude executions in which
> -\co{P2()}'s \co{smp_store_release()} precedes that of \co{P1()}.
> +\co{P2()}'s \co{smp_store_release()} precedes that of \co{P0()}.
>
> Running the litmus test in
> \cref{lst:memorder:A Release-Acquire Chain With Added Store (Ordering?)}
> --
> 2.25.1
>
>
prev parent reply other threads:[~2022-09-28 17:46 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-09-28 14:28 [PATCH -perfbook 1/2] memorder: Put \FloatBarrier in front of Section 15.3 Akira Yokosawa
2022-09-28 14:30 ` [PATCH -perfbook 2/2] memorder: Fix typo Akira Yokosawa
2022-09-28 17:46 ` Paul E. McKenney [this message]
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=20220928174611.GA4196@paulmck-ThinkPad-P17-Gen-1 \
--to=paulmck@kernel.org \
--cc=akiyks@gmail.com \
--cc=perfbook@vger.kernel.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 read-only IMAP folder(s) and NNTP newsgroup(s).