public inbox for linux-arm-kernel@lists.infradead.org
 help / color / mirror / Atom feed
From: ganguly.s@samsung.com (Sarbojit Ganguly)
To: linux-arm-kernel@lists.infradead.org
Subject: [RFC] arm: Add for atomic half word exchange
Date: Tue, 19 May 2015 11:20:11 +0000 (GMT)	[thread overview]
Message-ID: <1795987946.405311432034410830.JavaMail.weblogic@ep2mlwas07a> (raw)

Yes, I will try to do that. OTOH, I saw that  there was a discussion on removal of bad_xchg() altogether. Perhaps that approach be better than adding this half word exchange?


Regards,
Sarbojit

------- Original Message -------
Sender : Arnd Bergmann<arnd@arndb.de>
Date : May 19, 2015 18:51 (GMT+09:00)
Title : Re: [RFC] arm: Add for atomic half word exchange

On Tuesday 19 May 2015 09:39:33 Sarbojit Ganguly wrote:
> Since 16 bit half word exchange was not there and MCS based qspinlock by Waiman's xchg_tail() requires an atomic exchange on a half word,
> here is a small modification to __xchg() code.

We have discussed a similar patch before, see
https://lkml.org/lkml/2015/2/25/390

>  #if __LINUX_ARM_ARCH__ >= 6
> @@ -50,6 +52,23 @@
>                         : "r" (x), "r" (ptr)
>                         : "memory", "cc");
>                 break;
> +               /* 
> +                * halfword exclusive exchange
> +                * This is new implementation as qspinlock
> +                * wants 16 bit atomic CAS.
> +                */
> +       case 2:
> +               asm volatile("@ __xchg2\n"
> +               "1:     ldrexh  %0, [%3]\n"
> +               "       strexh  %1, %2, [%3]\n"
> +               "       teq     %1, #0\n"
> +               "       bne     1b"
> +                       : "=&r" (ret), "=&r" (tmp)
> +                       : "r" (x), "r" (ptr)
> +                       : "memory", "cc");
> +               break;
>         case 4: 
>                 asm volatile("@ __xchg4\n"
>                 "1:     ldrex   %0, [%3]\n"

Please try to find a way to make this compile when CONFIG_CPU_V6
is set.

Arnd

             reply	other threads:[~2015-05-19 11:20 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-05-19 11:20 Sarbojit Ganguly [this message]
2015-05-19 11:42 ` [RFC] arm: Add for atomic half word exchange Arnd Bergmann
2015-05-19 12:13 ` Russell King - ARM Linux
2015-05-19 12:43 ` Peter Zijlstra
     [not found] <274749765.566061433467033693.JavaMail.weblogic@epmlwas07c>
2015-06-05 12:33 ` Arnd Bergmann
     [not found] <146879519.394951433226103227.JavaMail.weblogic@epmlwas06d>
2015-06-02 10:49 ` Arnd Bergmann
     [not found] <1357570181.391771433224164775.JavaMail.weblogic@epmlwas06d>
2015-06-02  6:11 ` Raghavendra K T
     [not found] <1348896100.440561432098574765.JavaMail.weblogic@ep2mlwas07a>
2015-05-20  6:51 ` Arnd Bergmann
2015-05-20  6:57 ` Peter Zijlstra
  -- strict thread matches above, loose matches on Subject: below --
2015-05-19  9:39 Sarbojit Ganguly
2015-05-19  9:51 ` Arnd Bergmann

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=1795987946.405311432034410830.JavaMail.weblogic@ep2mlwas07a \
    --to=ganguly.s@samsung.com \
    --cc=linux-arm-kernel@lists.infradead.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