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 11:41:16 +0000 [thread overview]
Message-ID: <20100223114116.GB10501@n2100.arm.linux.org.uk> (raw)
In-Reply-To: <EAF47CD23C76F840A9E7FCE10091EFAB02C42E13E7@dbde02.ent.ti.com>
On Tue, Feb 23, 2010 at 05:05:31PM +0530, Shilimkar, Santosh wrote:
> OMAP3 and family would be ok with this much needed mandatory barriers
> but for OMAP4, we need platform specified barriers as you mentioned. Will
> have a look at this series and do some testing on OMAP4. Will send
> a follow up patch then.
Wait for v2 - it introduces barriers onto the older CPUs which do not
need it, and therefore is definitely not right.
Eg, ARMv4 CPUs don't need the drain-write-buffer instruction for mb()
and wmb() - we have no relaxed behaviours on those CPUs, so this is
pointless. As I also pointed out, it breaks ARMv3 because the drain-
write-buffer instruction there is an undefined instruction.
Plus, non-coherent Xscale has the same requirements as ARMv4, so getting
rid of the arch_is_coherent() stuff was completely wrong.
Basically, the patch is not suitable as it currently stands, and is in
need of rework.
next prev parent reply other threads:[~2010-02-23 11:41 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
2010-02-23 11:35 ` Shilimkar, Santosh
2010-02-23 11:41 ` Russell King - ARM Linux [this message]
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=20100223114116.GB10501@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).