linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: catalin.marinas@arm.com (Catalin Marinas)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 0/4] ARM mandatory barriers
Date: Tue, 02 Mar 2010 09:58:36 +0000	[thread overview]
Message-ID: <1267523916.10368.8.camel@e102109-lin.cambridge.arm.com> (raw)
In-Reply-To: <63386a3d1003020150o6a7bf041mf9c32fb989430063@mail.gmail.com>

On Tue, 2010-03-02 at 09:50 +0000, Linus Walleij wrote:
> 2010/2/23 Catalin Marinas <catalin.marinas@arm.com>:
> 
> > This is a follow up to a previous patch I posted on the implementation
> > of the mandatory barriers on ARM. The third patch adds support for the
> > L2x0 cache sync operation and the last patch implements the
> > RealView-specific mandatory barriers.
> 
> Catalin what is the status of these patches? I don't find them in the
> patch tracker, are they being reworked? (Sorry if I missed some of the
> discussion here...)

They are being slightly reworked. The latest version is in my devel
branch (the top four patches currently):

http://linux-arm.org/git?p=linux-2.6.git;a=shortlog;h=refs/heads/devel

I think the main issue is whether the smp_mb() should be a DSB or a DMB.
Some drivers assume it's a DSB but this would have performance issues on
other usage models of this barrier where DMB would be enough.

I'll take this today to linux-arch for some clarification and I should
hopefully repost a new set of patches by the end of the week.

-- 
Catalin

      reply	other threads:[~2010-03-02  9:58 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-02-23 11:00 [PATCH 0/4] ARM mandatory barriers Catalin Marinas
2010-03-02  9:50 ` Linus Walleij
2010-03-02  9:58   ` Catalin Marinas [this message]

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=1267523916.10368.8.camel@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).