From: Akira Yokosawa <akiyks@gmail.com>
To: paulmck@kernel.org
Cc: linux-kernel@vger.kernel.org, linux-arch@vger.kernel.org,
kernel-team@meta.com, mingo@kernel.org,
stern@rowland.harvard.edu, parri.andrea@gmail.com,
will@kernel.org, peterz@infradead.org, boqun.feng@gmail.com,
npiggin@gmail.com, dhowells@redhat.com, j.alglave@ucl.ac.uk,
luc.maranget@inria.fr, Marco Elver <elver@google.com>,
Daniel Lustig <dlustig@nvidia.com>,
Joel Fernandes <joel@joelfernandes.org>,
Akira Yokosawa <akiyks@gmail.com>
Subject: Re: [PATCH memory-model 3/3] tools/memory-model: Add KCSAN LF mentorship session citation
Date: Sat, 8 Jun 2024 08:38:12 +0900 [thread overview]
Message-ID: <3c5a53e2-b5a9-4197-97a3-247abb7f3061@gmail.com> (raw)
In-Reply-To: <f11f7230-7c16-45a3-83be-9aba32e10a3b@paulmck-laptop>
On 2024/06/05 13:02, Paul E. McKenney wrote:
> On Wed, Jun 05, 2024 at 10:57:27AM +0900, Akira Yokosawa wrote:
>> On Tue, 4 Jun 2024 15:14:19 -0700, Paul E. McKenney wrote:
>>> Add a citation to Marco's LF mentorship session presentation entitled
>>> "The Kernel Concurrency Sanitizer"
>>>
>>> [ paulmck: Apply Marco Elver feedback. ]
>>>
>>> Reported-by: Marco Elver <elver@google.com>
>>> Signed-off-by: Paul E. McKenney <paulmck@kernel.org>
>>> Cc: Alan Stern <stern@rowland.harvard.edu>
>>> Cc: Andrea Parri <parri.andrea@gmail.com>
>>> Cc: Will Deacon <will@kernel.org>
>>> Cc: Peter Zijlstra <peterz@infradead.org>
>>> Cc: Boqun Feng <boqun.feng@gmail.com>
>>> Cc: Nicholas Piggin <npiggin@gmail.com>
>>> Cc: David Howells <dhowells@redhat.com>
>>> Cc: Jade Alglave <j.alglave@ucl.ac.uk>
>>> Cc: Luc Maranget <luc.maranget@inria.fr>
>>> Cc: Akira Yokosawa <akiyks@gmail.com>
>>
>> Paul,
>>
>> While reviewing this, I noticed that
>> tools/memory-model/Documentation/README has no mention of
>> access-marking.txt.
>>
>> It has no mention of glossary.txt or locking.txt, either.
>>
>> I'm not sure where are the right places in README for them.
>> Can you update it in a follow-up change?
>>
>> Anyway, for this change,
>>
>> Reviewed-by: Akira Yokosawa <akiyks@gmail.com>
>
> Thank you, and good catch! Does the patch below look appropriate?
Well, I must say this is not what I expected.
Please see below.
>
> Thanx, Paul
>
> ------------------------------------------------------------------------
>
> commit 834b22ba762fb59024843a64554d38409aaa82ec
> Author: Paul E. McKenney <paulmck@kernel.org>
> Date: Tue Jun 4 20:59:35 2024 -0700
>
> tools/memory-model: Add access-marking.txt to README
>
> Given that access-marking.txt exists, this commit makes it easier to find.
>
> Reported-by: Akira Yokosawa <akiyks@gmail.com>
> Signed-off-by: Paul E. McKenney <paulmck@kernel.org>
>
> diff --git a/tools/memory-model/Documentation/README b/tools/memory-model/Documentation/README
> index db90a26dbdf40..304162743a5b8 100644
> --- a/tools/memory-model/Documentation/README
> +++ b/tools/memory-model/Documentation/README
> @@ -47,6 +47,10 @@ DESCRIPTION OF FILES
> README
> This file.
>
> +access-marking.txt
> + Guidelines for marking intentionally concurrent accesses to
> + shared memory.
> +
> cheatsheet.txt
> Quick-reference guide to the Linux-kernel memory model.
>
What I expected was an entry in the bullet list in the upper half
of README which mentions access-marking.txt along with the update of
alphabetical list of files.
Updating the latter wouldn't worth bothering you.
And you are missing another comment WRT glossary.txt and locking.txt. ;-)
Let me suggest an idea of their positions in the bullet list where the
ordering is important. Looks reasonable to you ?
o simple.txt
o ordering.txt
o locking.txt <--new
o litmus-test.txt
o recipes.txt
o control-dependencies.txt
o access-marking.txt <--new
o cheatsheet.txt
o explanation.txt
o references.txt
o glossary.txt <--new
Have I made my point clear enough?
Thanks, Akira
next prev parent reply other threads:[~2024-06-07 23:38 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-06-04 22:14 [PATCH memory-model 0/3] LKMM updates for v6.11 Paul E. McKenney
2024-06-04 22:14 ` [PATCH memory-model 1/3] tools/memory-model: Add atomic_and()/or()/xor() and add_negative Paul E. McKenney
2024-06-05 0:27 ` Akira Yokosawa
2024-06-05 4:06 ` Paul E. McKenney
2024-06-04 22:14 ` [PATCH memory-model 2/3] tools/memory-model: Add atomic_andnot() with its variants Paul E. McKenney
2024-06-04 22:14 ` [PATCH memory-model 3/3] tools/memory-model: Add KCSAN LF mentorship session citation Paul E. McKenney
2024-06-04 23:11 ` Andrea Parri
2024-06-05 4:02 ` Paul E. McKenney
2024-06-05 1:57 ` Akira Yokosawa
2024-06-05 4:02 ` Paul E. McKenney
2024-06-07 23:38 ` Akira Yokosawa [this message]
2024-06-08 15:48 ` Paul E. McKenney
2024-06-09 0:04 ` Akira Yokosawa
2024-06-09 3:10 ` Paul E. McKenney
2024-06-05 7:52 ` Marco Elver
2024-06-05 17:57 ` Paul E. McKenney
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=3c5a53e2-b5a9-4197-97a3-247abb7f3061@gmail.com \
--to=akiyks@gmail.com \
--cc=boqun.feng@gmail.com \
--cc=dhowells@redhat.com \
--cc=dlustig@nvidia.com \
--cc=elver@google.com \
--cc=j.alglave@ucl.ac.uk \
--cc=joel@joelfernandes.org \
--cc=kernel-team@meta.com \
--cc=linux-arch@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=luc.maranget@inria.fr \
--cc=mingo@kernel.org \
--cc=npiggin@gmail.com \
--cc=parri.andrea@gmail.com \
--cc=paulmck@kernel.org \
--cc=peterz@infradead.org \
--cc=stern@rowland.harvard.edu \
--cc=will@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