From: Mark Rutland <mark.rutland@arm.com>
To: mingo@kernel.org
Cc: linux-kernel@vger.kernel.org, akpm@linux-foundation.org,
anders.roxell@linaro.org, boqun.feng@gmail.com,
mark.rutland@arm.com, naresh.kamboju@linaro.org,
peterz@infradead.org, will.deacon@arm.com
Subject: [PATCH 0/2] locking/atomics: fix and improvement
Date: Mon, 10 Dec 2018 17:50:33 +0000 [thread overview]
Message-ID: <20181210175035.45096-1-mark.rutland@arm.com> (raw)
Hi Ingo,
I hope that these atomic scripting patches address your concerns with
the atomics scripting infrastructure. These are based on the tip
locking/core branch, leaving the headers checked-in.
The primary improvement is using a hash to detect when the headers have
been erroneously modified, meaning check-atomics.sh takes ~0.15s, which
I believe should be palatable.
It also turns out that some people are building without coreutils, so
I've picked up Anders' fix for this. Since sha1sum is part of coreutils,
the checks are skipped when this isn't present, on the assumption that
anyone actually sending patches will have a working coreutils.
Are you happy to pick these up?
Thanks,
Mark.
Anders Roxell (1):
locking/atomics: Change 'fold' to 'grep'
Mark Rutland (1):
locking/atomics: Check atomic headers with sha1sum
include/asm-generic/atomic-instrumented.h | 1 +
include/asm-generic/atomic-long.h | 1 +
include/linux/atomic-fallback.h | 1 +
scripts/atomic/atomic-tbl.sh | 2 +-
scripts/atomic/check-atomics.sh | 26 ++++++++++++++++++++------
scripts/atomic/gen-atomics.sh | 20 ++++++++++++++++++++
6 files changed, 44 insertions(+), 7 deletions(-)
create mode 100755 scripts/atomic/gen-atomics.sh
--
2.11.0
next reply other threads:[~2018-12-10 17:50 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-12-10 17:50 Mark Rutland [this message]
2018-12-10 17:50 ` [PATCH 1/2] locking/atomics: Change 'fold' to 'grep' Mark Rutland
2018-12-10 19:01 ` Will Deacon
2018-12-10 17:50 ` [PATCH 2/2] locking/atomics: Check atomic headers with sha1sum Mark Rutland
2018-12-10 19:03 ` Will Deacon
2018-12-12 10:18 ` [PATCH 0/2] locking/atomics: fix and improvement Mark Rutland
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=20181210175035.45096-1-mark.rutland@arm.com \
--to=mark.rutland@arm.com \
--cc=akpm@linux-foundation.org \
--cc=anders.roxell@linaro.org \
--cc=boqun.feng@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@kernel.org \
--cc=naresh.kamboju@linaro.org \
--cc=peterz@infradead.org \
--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
all inboxes | Powered by JetHome®