From: Peter Zijlstra <peterz@infradead.org>
To: Uros Bizjak <ubizjak@gmail.com>
Cc: x86@kernel.org, linux-kernel@vger.kernel.org,
Thomas Gleixner <tglx@linutronix.de>,
Ingo Molnar <mingo@redhat.com>, Borislav Petkov <bp@alien8.de>,
Dave Hansen <dave.hansen@linux.intel.com>,
"H. Peter Anvin" <hpa@zytor.com>, Will Deacon <will@kernel.org>,
Boqun Feng <boqun.feng@gmail.com>,
Mark Rutland <mark.rutland@arm.com>,
"Paul E. McKenney" <paulmck@kernel.org>,
Marco Elver <elver@google.com>
Subject: Re: [PATCH v3 0/2] locking/atomic/x86: Introduce arch_try_cmpxchg64
Date: Mon, 16 May 2022 10:12:14 +0200 [thread overview]
Message-ID: <YoIHXlmsso70rxne@hirez.programming.kicks-ass.net> (raw)
In-Reply-To: <20220515184205.103089-1-ubizjak@gmail.com>
On Sun, May 15, 2022 at 08:42:02PM +0200, Uros Bizjak wrote:
> Uros Bizjak (2):
> locking/atomic: Add generic try_cmpxchg64 support
> locking/atomic/x86: Introduce arch_try_cmpxchg64
>
> arch/x86/include/asm/cmpxchg_32.h | 21 ++++++
> arch/x86/include/asm/cmpxchg_64.h | 6 ++
> include/linux/atomic/atomic-arch-fallback.h | 72 ++++++++++++++++++++-
> include/linux/atomic/atomic-instrumented.h | 40 +++++++++++-
> scripts/atomic/gen-atomic-fallback.sh | 31 +++++----
> scripts/atomic/gen-atomic-instrumented.sh | 2 +-
> 6 files changed, 156 insertions(+), 16 deletions(-)
Thanks!
prev parent reply other threads:[~2022-05-16 8:12 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-05-15 18:42 [PATCH v3 0/2] locking/atomic/x86: Introduce arch_try_cmpxchg64 Uros Bizjak
2022-05-15 18:42 ` [PATCH v3 1/2] locking/atomic: Add generic try_cmpxchg64 support Uros Bizjak
2022-05-17 22:21 ` [tip: locking/core] " tip-bot2 for Uros Bizjak
2022-05-15 18:42 ` [PATCH v3 2/2] locking/atomic/x86: Introduce arch_try_cmpxchg64 Uros Bizjak
2022-05-17 22:21 ` [tip: locking/core] " tip-bot2 for Uros Bizjak
2022-05-16 8:12 ` Peter Zijlstra [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=YoIHXlmsso70rxne@hirez.programming.kicks-ass.net \
--to=peterz@infradead.org \
--cc=boqun.feng@gmail.com \
--cc=bp@alien8.de \
--cc=dave.hansen@linux.intel.com \
--cc=elver@google.com \
--cc=hpa@zytor.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mark.rutland@arm.com \
--cc=mingo@redhat.com \
--cc=paulmck@kernel.org \
--cc=tglx@linutronix.de \
--cc=ubizjak@gmail.com \
--cc=will@kernel.org \
--cc=x86@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