From: will.deacon@arm.com (Will Deacon)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH] ARM: futex: add SMP futex support when !CPU_USE_DOMAINS
Date: Wed, 20 Apr 2011 16:29:07 +0100 [thread overview]
Message-ID: <1303313347.11314.4.camel@e102144-lin.cambridge.arm.com> (raw)
In-Reply-To: <1302267519-18156-1-git-send-email-will.deacon@arm.com>
On Fri, 2011-04-08 at 13:58 +0100, Will Deacon wrote:
> This patch uses the load/store exclusive instructions to add SMP futex
> support for ARM.
>
> Since the ARM architecture does not provide instructions for
> unprivileged exclusive memory accesses, we can only provide SMP futexes
> when CPU domain support is disabled.
>
> Signed-off-by: Will Deacon <will.deacon@arm.com>
> ---
> arch/arm/include/asm/futex.h | 137 +++++++++++++++++++++++++++--------------
> 1 files changed, 90 insertions(+), 47 deletions(-)
Any comments on this patch? The LTP tests for {get,set}_robust_list seem
happy enough but any review would be welcome.
Will
next prev parent reply other threads:[~2011-04-20 15:29 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-04-08 12:58 [PATCH] ARM: futex: add SMP futex support when !CPU_USE_DOMAINS Will Deacon
2011-04-20 15:29 ` Will Deacon [this message]
2011-04-20 17:41 ` Nicolas Pitre
2011-04-21 14:35 ` Will Deacon
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=1303313347.11314.4.camel@e102144-lin.cambridge.arm.com \
--to=will.deacon@arm.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;
as well as URLs for NNTP newsgroup(s).