[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <1297705428.5226.142.camel@laptop>
Date: Mon, 14 Feb 2011 18:43:48 +0100
From: Peter Zijlstra <peterz@...radead.org>
To: Will Newton <will.newton@...il.com>
Cc: Steven Rostedt <rostedt@...dmis.org>,
Jason Baron <jbaron@...hat.com>,
Mathieu Desnoyers <mathieu.desnoyers@...ymtl.ca>,
hpa@...or.com, mingo@...e.hu, tglx@...utronix.de,
andi@...stfloor.org, roland@...hat.com, rth@...hat.com,
masami.hiramatsu.pt@...achi.com, fweisbec@...il.com,
avi@...hat.com, davem@...emloft.net, sam@...nborg.org,
ddaney@...iumnetworks.com, michael@...erman.id.au,
linux-kernel@...r.kernel.org, Mike Frysinger <vapier@...too.org>,
Chris Metcalf <cmetcalf@...era.com>,
dhowells <dhowells@...hat.com>,
Martin Schwidefsky <schwidefsky@...ibm.com>,
"heiko.carstens" <heiko.carstens@...ibm.com>,
benh <benh@...nel.crashing.org>
Subject: Re: [PATCH 0/2] jump label: 2.6.38 updates
On Mon, 2011-02-14 at 17:38 +0000, Will Newton wrote:
> On Mon, Feb 14, 2011 at 5:27 PM, Peter Zijlstra <peterz@...radead.org> wrote:
>
> >> So all but a few have basically (as you said on IRC)
> >> #define atomic_read(v) ACCESS_ONCE(v)
> >
> > ACCESS_ONCE(v->counter), but yeah :-)
>
> I maintain an out-of-tree architecture where that isn't the case
> unfortunately [1]. Not expecting any special favours for being
> out-of-tree of course, but just thought I would add that data point.
>
> [1] Our atomic operations go around the cache rather than through it,
> so the value of an atomic cannot be read with a normal load
> instruction.
Cannot how? It would observe a stale value? That is acceptable for
atomic_read().
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists