From: linux@arm.linux.org.uk (Russell King - ARM Linux)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 1/4] ARM: Change the mandatory barriers implementation
Date: Tue, 23 Feb 2010 12:31:35 +0000 [thread overview]
Message-ID: <20100223123135.GD10501@n2100.arm.linux.org.uk> (raw)
In-Reply-To: <1266927716.3123.57.camel@e102109-lin.cambridge.arm.com>
On Tue, Feb 23, 2010 at 12:21:56PM +0000, Catalin Marinas wrote:
> diff --git a/arch/arm/include/asm/system.h b/arch/arm/include/asm/system.h
> index 058e7e9..0db8b06 100644
> --- a/arch/arm/include/asm/system.h
> +++ b/arch/arm/include/asm/system.h
> @@ -138,10 +138,12 @@ extern unsigned int user_debug;
> #define dmb() __asm__ __volatile__ ("" : : : "memory")
> #endif
>
> -#if __LINUX_ARM_ARCH__ >= 7 || defined(CONFIG_SMP)
> -#define mb() dmb()
> +#ifdef CONFIG_ARCH_HAS_BARRIERS
> +#include <mach/barriers.h>
> +#elif __LINUX_ARM_ARCH__ >= 5
> +#define mb() dsb()
> #define rmb() dmb()
> -#define wmb() dmb()
> +#define wmb() dsb()
Why do we need these to be anything more than compiler barriers on PXA?
next prev parent reply other threads:[~2010-02-23 12:31 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-02-23 11:01 [PATCH 1/4] ARM: Change the mandatory barriers implementation Catalin Marinas
2010-02-23 11:10 ` Russell King - ARM Linux
2010-02-23 12:16 ` Catalin Marinas
2010-02-23 12:30 ` Russell King - ARM Linux
2010-02-23 15:12 ` Catalin Marinas
2010-02-23 15:24 ` Russell King - ARM Linux
2010-02-23 16:02 ` Catalin Marinas
2010-02-23 18:03 ` Russell King - ARM Linux
2010-02-23 18:07 ` Catalin Marinas
2010-03-01 3:37 ` Jamie Lokier
2010-02-26 15:43 ` Catalin Marinas
2010-03-01 3:44 ` Jamie Lokier
2010-02-23 12:21 ` Catalin Marinas
2010-02-23 12:31 ` Russell King - ARM Linux [this message]
2010-02-23 11:35 ` Shilimkar, Santosh
2010-02-23 11:41 ` Russell King - ARM Linux
2010-02-23 17:33 ` Russell King - ARM Linux
2010-02-23 17:58 ` Catalin Marinas
2010-02-23 18:04 ` 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=20100223123135.GD10501@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).