From: "Paul E. McKenney" <paulmck@kernel.org>
To: Akira Yokosawa <akiyks@gmail.com>
Cc: Zhouyi Zhou <zhouzhouyi@gmail.com>,
perfbook@vger.kernel.org, luyang.co@gmail.com
Subject: Re: [PATCH -perfbook] memorder: fix a typo in Listing 15.25's caption
Date: Thu, 20 Oct 2022 16:44:28 -0700 [thread overview]
Message-ID: <20221020234428.GE5600@paulmck-ThinkPad-P17-Gen-1> (raw)
In-Reply-To: <fdb0fd83-5cbc-eda2-c127-3d4a26ded8ad@gmail.com>
On Wed, Oct 19, 2022 at 09:47:11PM +0900, Akira Yokosawa wrote:
> Hi,
>
> On Wed, 19 Oct 2022 16:44:42 +0800, Zhouyi Zhou wrote:
> > Caption of Listing 15.25 should be "Z6.2 Release-Acquire Chain (Ordering?)"
> > instead of "Z6.0 Release-Acquire Chain (Ordering?)"
> >
> > Signed-off-by: Zhouyi Zhou <zhouzhouyi@gmail.com>
> > ---
> > Hi Paul and Akira:
> >
> > I guess there is a typo in caption of listing 15.25
>
> Nice catch!
>
> Reviewed-by: Akira Yokosawa <akiyks@gmail.com>
Queued, thank you both!
Thanx, Paul
> > Many thanks
> > Zhouyi
> > --
> > memorder/memorder.tex | 8 ++++----
> > 1 file changed, 4 insertions(+), 4 deletions(-)
> >
> > diff --git a/memorder/memorder.tex b/memorder/memorder.tex
> > index 28319bfb..0c96d43b 100644
> > --- a/memorder/memorder.tex
> > +++ b/memorder/memorder.tex
> > @@ -2325,14 +2325,14 @@ prevents the \co{exists} clause on \clnref{exists} from triggering.
> >
> > \begin{listing}
> > \input{CodeSamples/formal/litmus/C-Z6.2+o-r+a-o+o-mb-o@whole.fcv}
> > -\caption{Z6.0 Release-Acquire Chain (Ordering?)}
> > -\label{lst:memorder:Z6.0 Release-Acquire Chain (Ordering?)}
> > +\caption{Z6.2 Release-Acquire Chain (Ordering?)}
> > +\label{lst:memorder:Z6.2 Release-Acquire Chain (Ordering?)}
> > \end{listing}
> >
> > \QuickQuiz{
> > Suppose we have a short release-acquire chain along with one
> > load-to-store link and one store-to-store link, like that shown in
> > - \cref{lst:memorder:Z6.0 Release-Acquire Chain (Ordering?)}.
> > + \cref{lst:memorder:Z6.2 Release-Acquire Chain (Ordering?)}.
> > Given that there is only one of each type of non-store-to-load
> > link, the \co{exists} cannot trigger, right?
> > }\QuickQuizAnswer{
> > @@ -2345,7 +2345,7 @@ prevents the \co{exists} clause on \clnref{exists} from triggering.
> > thereof, it is necessary to have at least one full barrier
> > (\co{smp_mb()} or better) between each non-store-to-load link.
> > In
> > - \cref{lst:memorder:Z6.0 Release-Acquire Chain (Ordering?)},
> > + \cref{lst:memorder:Z6.2 Release-Acquire Chain (Ordering?)},
> > preventing the \co{exists} clause from triggering therefore requires
> > an additional full barrier between either \co{P0()}'s or
> > \co{P1()}'s accesses.
prev parent reply other threads:[~2022-10-20 23:44 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-19 8:44 [PATCH -perfbook] memorder: fix a typo in Listing 15.25's caption Zhouyi Zhou
2022-10-19 12:47 ` Akira Yokosawa
2022-10-20 23:44 ` 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=20221020234428.GE5600@paulmck-ThinkPad-P17-Gen-1 \
--to=paulmck@kernel.org \
--cc=akiyks@gmail.com \
--cc=luyang.co@gmail.com \
--cc=perfbook@vger.kernel.org \
--cc=zhouzhouyi@gmail.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 read-only IMAP folder(s) and NNTP newsgroup(s).