[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-Id: <1244776417.5320.160.camel@yhuang-dev.sh.intel.com>
Date: Fri, 12 Jun 2009 11:13:37 +0800
From: Huang Ying <ying.huang@...el.com>
To: Mathieu Desnoyers <compudj@...stal.dyndns.org>
Cc: Steven Rostedt <rostedt@...dmis.org>,
"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
Ingo Molnar <mingo@...e.hu>,
Andrew Morton <akpm@...ux-foundation.org>,
Thomas Gleixner <tglx@...utronix.de>,
Peter Zijlstra <peterz@...radead.org>,
Frederic Weisbecker <fweisbec@...il.com>,
Theodore Tso <tytso@....edu>,
Arnaldo Carvalho de Melo <acme@...hat.com>,
Lai Jiangshan <laijs@...fujitsu.com>,
"Martin J. Bligh" <mbligh@...igh.org>,
Christoph Hellwig <hch@...radead.org>,
Li Zefan <lizf@...fujitsu.com>,
"H. Peter Anvin" <hpa@...or.com>,
Hidetoshi Seto <seto.hidetoshi@...fujitsu.com>,
Masami Hiramatsu <mhiramat@...hat.com>
Subject: Re: [PATCH 3/3] ring-buffer: add design document
On Thu, 2009-06-11 at 10:38 +0800, Mathieu Desnoyers wrote:
> > > Are these archs without cmpxchg and NMIs, a concern for you?
> >
> > ARM has no cmpxchg until ARM v6, but it has NMI like mechanism named
> > FIQ.
> >
>
> One could probably adapt the cmpxchg for earlier ARM so it disables
> FIQs. Note that the current limitation is that there is only a
> fiq disable, not a fiq save/restore.
Yes. It seems that ARM is OK after FIQ save/restore issue is fixed.
Another machine with NMI but no NMI-safe cmpxchg is "real" 386. That is
very old machine, does that matter?
Best Regards,
Huang Ying
--
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