The Linux Kernel Mailing List
 help / color / mirror / Atom feed
From: Will Deacon <will.deacon@arm.com>
To: Pranith Kumar <bobby.prani@gmail.com>
Cc: Catalin Marinas <Catalin.Marinas@arm.com>,
	Steve Capper <steve.capper@linaro.org>,
	"linux-arm-kernel@lists.infradead.org" 
	<linux-arm-kernel@lists.infradead.org>,
	open list <linux-kernel@vger.kernel.org>
Subject: Re: [RFC PATCH] arm64: cmpxchg.h: Bring ldxr and stxr closer
Date: Fri, 27 Feb 2015 20:15:30 +0000	[thread overview]
Message-ID: <20150227201526.GH24818@arm.com> (raw)
In-Reply-To: <1425067776-2794-1-git-send-email-bobby.prani@gmail.com>

On Fri, Feb 27, 2015 at 08:09:17PM +0000, Pranith Kumar wrote:
> ARM64 documentation recommends keeping exclusive loads and stores as close as
> possible. Any instructions which do not depend on the value loaded should be
> moved outside. 
> 
> In the current implementation of cmpxchg(), there is a mov instruction which can
> be pulled before the load exclusive instruction without any change in
> functionality. This patch does that change.
> 
> Signed-off-by: Pranith Kumar <bobby.prani@gmail.com>
> ---
>  arch/arm64/include/asm/cmpxchg.h | 10 +++++-----
>  1 file changed, 5 insertions(+), 5 deletions(-)

[...]

> @@ -166,11 +166,11 @@ static inline int __cmpxchg_double(volatile void *ptr1, volatile void *ptr2,
>  		VM_BUG_ON((unsigned long *)ptr2 - (unsigned long *)ptr1 != 1);
>  		do {
>  			asm volatile("// __cmpxchg_double8\n"
> +			"	mov	%w0, #0\n"
>  			"	ldxp	%0, %1, %2\n"

Seriously, you might want to test this before you mindlessly make changes to
low-level synchronisation code. Not only is the change completely unnecessary
but it is actively harmful.

Have a good weekend,

Will

  reply	other threads:[~2015-02-27 20:15 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-02-27 20:09 [RFC PATCH] arm64: cmpxchg.h: Bring ldxr and stxr closer Pranith Kumar
2015-02-27 20:15 ` Will Deacon [this message]
2015-02-27 20:17   ` Pranith Kumar
2015-02-27 20:29     ` Pranith Kumar
2015-03-03 14:34       ` Catalin Marinas
2015-03-03 16:58         ` Pranith Kumar
2015-03-03 17:22           ` Catalin Marinas

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=20150227201526.GH24818@arm.com \
    --to=will.deacon@arm.com \
    --cc=Catalin.Marinas@arm.com \
    --cc=bobby.prani@gmail.com \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=steve.capper@linaro.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