From: "Paul E. McKenney" <paulmck@linux.vnet.ibm.com>
To: linux-kernel@vger.kernel.org, linux-arch@vger.kernel.org,
mingo@kernel.org
Cc: stern@rowland.harvard.edu, parri.andrea@gmail.com,
will.deacon@arm.com, peterz@infradead.org, boqun.feng@gmail.com,
npiggin@gmail.com, dhowells@redhat.com, j.alglave@ucl.ac.uk,
luc.maranget@inria.fr, akiyks@gmail.com
Subject: [PATCH memory-model 0/3] Kernel fixes to spin_is_locked()
Date: Mon, 14 May 2018 16:01:05 -0700 [thread overview]
Message-ID: <20180514230105.GA6421@linux.vnet.ibm.com> (raw)
Hello!
This series contains fixes to the kernel related to the semantics
of spin_is_locked(), all courtesy of Andrea Parri, and all ready for
inclusion in -tip:
1. Document the semantics of spin_is_locked() by adding a docbook
header comment.
2. Remove smp_mb() from arch_spin_is_locked(), given that the
new order-free spin_is_locked() semantics require no such barrier.
3. Clean up comment and #ifndef for {,queued_}spin_is_locked().
The comment was "XXX think about spin_is_locked", and I can
attest that we have now done some serious thinking. ;-)
Thanx, Paul
------------------------------------------------------------------------
next reply other threads:[~2018-05-14 23:01 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-05-14 23:01 Paul E. McKenney [this message]
2018-05-14 23:01 ` [PATCH memory-model 0/3] Kernel fixes to spin_is_locked() Paul E. McKenney
2018-05-14 23:01 ` [PATCH memory-model 1/3] locking: Document the semantics of spin_is_locked() Paul E. McKenney
2018-05-14 23:01 ` Paul E. McKenney
2018-05-14 23:01 ` [PATCH memory-model 2/3] arm64: Remove smp_mb() from arch_spin_is_locked() Paul E. McKenney
2018-05-14 23:01 ` Paul E. McKenney
2018-05-14 23:01 ` [PATCH memory-model 3/3] locking: Clean up comment and #ifndef for {,queued_}spin_is_locked() Paul E. McKenney
2018-05-14 23:01 ` 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=20180514230105.GA6421@linux.vnet.ibm.com \
--to=paulmck@linux.vnet.ibm.com \
--cc=akiyks@gmail.com \
--cc=boqun.feng@gmail.com \
--cc=dhowells@redhat.com \
--cc=j.alglave@ucl.ac.uk \
--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=peterz@infradead.org \
--cc=stern@rowland.harvard.edu \
--cc=will.deacon@arm.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