From: Peter Zijlstra <peterz@infradead.org>
To: Uros Bizjak <ubizjak@gmail.com>
Cc: x86@kernel.org, linux-kernel@vger.kernel.org,
kvm@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] locking/atomic/x86: Introduce try_cmpxchg64
Date: Fri, 13 May 2022 11:10:34 +0200 [thread overview]
Message-ID: <20220513091034.GH76023@worktop.programming.kicks-ass.net> (raw)
In-Reply-To: <20220510154217.5216-1-ubizjak@gmail.com>
On Tue, May 10, 2022 at 05:42:17PM +0200, Uros Bizjak wrote:
For the Changelog I would focus on the 64bit improvement and leave 32bit
as a side-note.
> ---
> arch/x86/include/asm/cmpxchg_32.h | 43 ++++++++++++++++++++++
> arch/x86/include/asm/cmpxchg_64.h | 6 +++
> include/linux/atomic/atomic-instrumented.h | 40 +++++++++++++++++++-
> scripts/atomic/gen-atomic-instrumented.sh | 2 +-
> 4 files changed, 89 insertions(+), 2 deletions(-)
>
> diff --git a/arch/x86/include/asm/cmpxchg_32.h b/arch/x86/include/asm/cmpxchg_32.h
> index 0a7fe0321613..e874ff7f7529 100644
> --- a/arch/x86/include/asm/cmpxchg_32.h
> +++ b/arch/x86/include/asm/cmpxchg_32.h
> @@ -42,6 +42,9 @@ static inline void set_64bit(volatile u64 *ptr, u64 value)
> #define arch_cmpxchg64_local(ptr, o, n) \
> ((__typeof__(*(ptr)))__cmpxchg64_local((ptr), (unsigned long long)(o), \
> (unsigned long long)(n)))
> +#define arch_try_cmpxchg64(ptr, po, n) \
> + ((__typeof__(*(ptr)))__try_cmpxchg64((ptr), (unsigned long long *)(po), \
> + (unsigned long long)(n)))
> #endif
>
> static inline u64 __cmpxchg64(volatile u64 *ptr, u64 old, u64 new)
> @@ -70,6 +73,25 @@ static inline u64 __cmpxchg64_local(volatile u64 *ptr, u64 old, u64 new)
> return prev;
> }
>
> +static inline bool __try_cmpxchg64(volatile u64 *ptr, u64 *pold, u64 new)
> +{
> + bool success;
> + u64 prev;
> + asm volatile(LOCK_PREFIX "cmpxchg8b %2"
> + CC_SET(z)
> + : CC_OUT(z) (success),
> + "=A" (prev),
> + "+m" (*ptr)
> + : "b" ((u32)new),
> + "c" ((u32)(new >> 32)),
> + "1" (*pold)
> + : "memory");
> +
> + if (unlikely(!success))
> + *pold = prev;
I would prefer this be more like the existing try_cmpxchg code,
perhaps:
u64 old = *pold;
asm volatile (LOCK_PREFIX "cmpxchg8b %[ptr]"
CC_SET(z)
: CC_OUT(z) (success),
[ptr] "+m" (*ptr)
"+A" (old)
: "b" ((u32)new)
"c" ((u32)(new >> 32))
: "memory");
if (unlikely(!success))
*pold = old;
The existing 32bit cmpxchg code is a 'bit' crusty.
> + return success;
> +}
> +
> #ifndef CONFIG_X86_CMPXCHG64
> /*
> * Building a kernel capable running on 80386 and 80486. It may be necessary
> @@ -108,6 +130,27 @@ static inline u64 __cmpxchg64_local(volatile u64 *ptr, u64 old, u64 new)
> : "memory"); \
> __ret; })
>
> +#define arch_try_cmpxchg64(ptr, po, n) \
> +({ \
> + bool success; \
> + __typeof__(*(ptr)) __prev; \
> + __typeof__(ptr) _old = (__typeof__(ptr))(po); \
> + __typeof__(*(ptr)) __old = *_old; \
> + __typeof__(*(ptr)) __new = (n); \
> + alternative_io(LOCK_PREFIX_HERE \
> + "call cmpxchg8b_emu", \
> + "lock; cmpxchg8b (%%esi)" , \
> + X86_FEATURE_CX8, \
> + "=A" (__prev), \
> + "S" ((ptr)), "0" (__old), \
> + "b" ((unsigned int)__new), \
> + "c" ((unsigned int)(__new>>32)) \
> + : "memory"); \
> + success = (__prev == __old); \
> + if (unlikely(!success)) \
> + *_old = __prev; \
> + likely(success); \
> +})
Wouldn't this be better written like the normal fallback wrapper?
static __always_inline bool
arch_try_cmpxchg64(u64 *v, u64 *old, u64 new)
{
u64 r, o = *old;
r = arch_cmpxchg64(v, o, new);
if (unlikely(r != o))
*old = r;
return likely(r == o);
}
Less magical, same exact code.
next prev parent reply other threads:[~2022-05-13 9:11 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-05-10 15:42 [PATCH] locking/atomic/x86: Introduce try_cmpxchg64 Uros Bizjak
2022-05-10 16:55 ` Peter Zijlstra
2022-05-10 17:07 ` Uros Bizjak
2022-05-11 7:54 ` Peter Zijlstra
2022-05-11 8:24 ` Uros Bizjak
2022-05-11 16:04 ` Sean Christopherson
2022-05-11 19:54 ` Uros Bizjak
2022-05-16 14:04 ` Maxim Levitsky
2022-05-16 14:08 ` Sean Christopherson
2022-05-16 14:49 ` Maxim Levitsky
2022-05-16 15:14 ` Sean Christopherson
2022-05-16 15:36 ` Maxim Levitsky
2022-05-13 9:10 ` Peter Zijlstra [this message]
2022-05-13 10:20 ` Uros Bizjak
2022-05-13 15:36 ` Uros Bizjak
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=20220513091034.GH76023@worktop.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=kvm@vger.kernel.org \
--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