From: catalin.marinas@arm.com (Catalin Marinas)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v4 0/4] ARM mandatory barriers
Date: Fri, 19 Mar 2010 13:48:20 +0000 [thread overview]
Message-ID: <20100319134614.14625.18408.stgit@e102109-lin.cambridge.arm.com> (raw)
Hi,
Updated series on the ARM mandatory barriers. As per Russell's
suggestion, most platform seem to define the mb() as dsb(); outer_sync()
and it makes sense to make this the default (if CONFIG_OUTER_CACHE_SYNC
is defined). The patch still allows per-platform barriers via the
CONFIG_ARCH_HAS_BARRIERS option.
Catalin Marinas (4):
ARM: Move the outer_cache definitions into a separate file
ARM: Add outer_cache_fns.sync function pointer
ARM: Add L2x0 outer_sync() support
ARM: Change the mandatory barriers implementation
arch/arm/include/asm/cacheflush.h | 38 -------------------
arch/arm/include/asm/outercache.h | 75 +++++++++++++++++++++++++++++++++++++
arch/arm/include/asm/system.h | 14 ++++---
arch/arm/mm/Kconfig | 13 ++++++
arch/arm/mm/cache-l2x0.c | 10 +++++
5 files changed, 107 insertions(+), 43 deletions(-)
create mode 100644 arch/arm/include/asm/outercache.h
--
Catalin
next reply other threads:[~2010-03-19 13:48 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-03-19 13:48 Catalin Marinas [this message]
2010-03-19 13:48 ` [PATCH v4 1/4] ARM: Move the outer_cache definitions into a separate file Catalin Marinas
2010-03-19 13:48 ` [PATCH v4 2/4] ARM: Add outer_cache_fns.sync function pointer Catalin Marinas
2010-03-19 13:48 ` [PATCH v4 3/4] ARM: Add L2x0 outer_sync() support Catalin Marinas
2010-03-19 13:48 ` [PATCH v4 4/4] ARM: Change the mandatory barriers implementation Catalin Marinas
2010-03-19 14:10 ` [PATCH v4 0/4] ARM mandatory barriers 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=20100319134614.14625.18408.stgit@e102109-lin.cambridge.arm.com \
--to=catalin.marinas@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).