From: linux@arm.linux.org.uk (Russell King - ARM Linux)
To: linux-arm-kernel@lists.infradead.org
Subject: __xchg for sizes other than 32bit
Date: Wed, 10 Mar 2010 17:35:03 +0000 [thread overview]
Message-ID: <20100310173503.GC12345@n2100.arm.linux.org.uk> (raw)
In-Reply-To: <20100310162221.GA19201@localhost>
On Wed, Mar 10, 2010 at 06:22:21PM +0200, Imre Deak wrote:
> recently you've added support for __cmpxchg for ARMv6+. There the assumption
> is that ldrex[bh]/strex[bh] is only supported on platforms with the 32v6K
> extension.
>
> Currently the __xchg code uses these even without the extension. Should this
> be fixed?
next prev parent reply other threads:[~2010-03-10 17:35 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-03-10 16:22 __xchg for sizes other than 32bit Imre Deak
2010-03-10 17:35 ` Russell King - ARM Linux [this message]
2010-03-10 20:02 ` [PATCH] ARM support single byte cmpxchg and cmpxchg_local on ARMv6 Mathieu Desnoyers
2010-03-10 20:30 ` Russell King - ARM Linux
2010-03-10 21:15 ` Mathieu Desnoyers
2010-03-10 23:16 ` __xchg for sizes other than 32bit Jamie Lokier
2010-03-18 9:29 ` [PATCH 1/1] [RFC] arm: add half-word __xchg Alexander Shishkin
2010-03-18 12:32 ` Mathieu Desnoyers
2010-03-18 12:37 ` Alexander Shishkin
2010-03-18 13:33 ` Alexander Shishkin
2010-03-18 13:50 ` Mathieu Desnoyers
2010-03-18 16:33 ` Imre Deak
2010-03-18 17:21 ` Mathieu Desnoyers
2010-03-18 19:00 ` Imre Deak
2010-03-18 19:30 ` Mathieu Desnoyers
2010-03-19 1:49 ` Jamie Lokier
2010-03-19 2:12 ` Mathieu Desnoyers
2010-03-19 3:36 ` Jamie Lokier
2010-03-25 15:52 ` [PATCH 1/1] [RFCv2] " Alexander Shishkin
2010-03-25 16:42 ` Alexander Shishkin
2010-03-27 22:52 ` Russell King - ARM Linux
2010-03-28 0:14 ` Jamie Lokier
2010-03-28 0:18 ` Russell King - ARM Linux
2010-03-28 1:00 ` Mathieu Desnoyers
2010-03-28 14:39 ` Jamie Lokier
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=20100310173503.GC12345@n2100.arm.linux.org.uk \
--to=linux@arm.linux.org.uk \
--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;
as well as URLs for NNTP newsgroup(s).