From: Peter Zijlstra <peterz@infradead.org>
To: Will Deacon <will.deacon@arm.com>
Cc: linux-kernel@vger.kernel.org, waiman.long@hpe.com,
mingo@redhat.com, paulmck@linux.vnet.ibm.com,
boqun.feng@gmail.com, torvalds@linux-foundation.org,
dave@stgolabs.net
Subject: Re: [RFC][PATCH 3/3] locking,arm64: Introduce cmpwait()
Date: Wed, 13 Apr 2016 14:52:43 +0200 [thread overview]
Message-ID: <20160413125243.GA6810@worktop.ger.corp.intel.com> (raw)
In-Reply-To: <20160412165941.GG26124@arm.com>
On Tue, Apr 12, 2016 at 05:59:41PM +0100, Will Deacon wrote:
> Thanks for looking at this!
n/p, had to se what it would look like etc.. :-)
> > I've misplaced my arm64 compiler, so this is not even compile tested.
>
> Guess what? ;)
>
> make: *** [init] Error 2
> make: *** Waiting for unfinished jobs....
>
> (and lot of similar errors).
>
> Looks like you're just missing an #undef in cmpxchg.h.
>
> FWIW, you can pick up arm64 toolchain binaries from:
>
> https://releases.linaro.org/components/toolchain/binaries/latest-5/
Ah, I usually build a whole set from sources; for some reason arm64
didn't build in the latest run. I'll have to kick it.
> > +#define __CMPWAIT_GEN(w, sz, name) \
> > +void __cmpwait_case_##name(volatile void *ptr, unsigned long val) \
> > +{ \
> > + unsigned long tmp; \
> > + \
> > + asm volatile( \
> > + " ldxr" #sz "\t%" #w "[tmp], %[v]\n" \
> > + " eor %" #w "[tmp], %" #w "[tmp], %" #w "[val]\n" \
> > + " cbnz %" #w "[tmp], 1f\n" \
>
> Shouldn't this be cbz? (i.e. branch over the wfe if the value is equal
> to what we wanted?).
Indeed so.
> > + " wfe\n" \
> > + "1:" \
> > + : [tmp] "=&r" (tmp), [val] "=&r" (val), \
>
> We only read val, so it can be an input operand, no?
True.. :-)
> > +#define cmpwait(ptr, val) \
> > + __cmpwait((ptr), (unsigned long)(val), sizeof(*(ptr)))
>
> We might want to call this cmpwait_relaxed, in case we decide to add
> fenced versions in the future. Or just make it cmpwait_acquire and
> remove the smp_rmb() from smp_cond_load_acquire(). Dunno.
This is something I'll very much leave up to you. I have no idea on the
tradeoffs involved here.
next prev parent reply other threads:[~2016-04-13 12:52 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-04-04 12:22 [RFC][PATCH 0/3] smp_cond_load_acquire + cmpwait Peter Zijlstra
2016-04-04 12:22 ` [RFC][PATCH 1/3] locking: Replace smp_cond_acquire with smp_cond_load_acquire Peter Zijlstra
2016-04-04 18:20 ` Waiman Long
2016-04-04 12:22 ` [RFC][PATCH 2/3] locking/qrwlock: Use smp_cond_load_acquire() Peter Zijlstra
2016-04-12 4:58 ` Davidlohr Bueso
2016-04-12 16:45 ` Waiman Long
2016-04-04 12:22 ` [RFC][PATCH 3/3] locking,arm64: Introduce cmpwait() Peter Zijlstra
2016-04-04 13:12 ` Peter Zijlstra
2016-04-12 16:59 ` Will Deacon
2016-04-13 12:52 ` Peter Zijlstra [this message]
2016-04-26 16:33 ` Will Deacon
2016-04-26 17:15 ` Will Deacon
2016-04-26 20:25 ` Peter Zijlstra
2016-04-22 16:08 ` Boqun Feng
2016-04-22 16:53 ` Will Deacon
2016-04-23 4:02 ` Boqun Feng
2016-04-23 2:37 ` Peter Zijlstra
2016-04-23 3:40 ` Boqun Feng
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=20160413125243.GA6810@worktop.ger.corp.intel.com \
--to=peterz@infradead.org \
--cc=boqun.feng@gmail.com \
--cc=dave@stgolabs.net \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=paulmck@linux.vnet.ibm.com \
--cc=torvalds@linux-foundation.org \
--cc=waiman.long@hpe.com \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.