From: "H. Peter Anvin" <hpa@zytor.com>
To: Huang Ying <ying.huang@intel.com>
Cc: Mathieu Desnoyers <compudj@krystal.dyndns.org>,
Steven Rostedt <rostedt@goodmis.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
Ingo Molnar <mingo@elte.hu>,
Andrew Morton <akpm@linux-foundation.org>,
Thomas Gleixner <tglx@linutronix.de>,
Peter Zijlstra <peterz@infradead.org>,
Frederic Weisbecker <fweisbec@gmail.com>,
Theodore Tso <tytso@mit.edu>,
Arnaldo Carvalho de Melo <acme@redhat.com>,
Lai Jiangshan <laijs@cn.fujitsu.com>,
"Martin J. Bligh" <mbligh@mbligh.org>,
Christoph Hellwig <hch@infradead.org>,
Li Zefan <lizf@cn.fujitsu.com>,
Hidetoshi Seto <seto.hidetoshi@jp.fujitsu.com>,
Masami Hiramatsu <mhiramat@redhat.com>
Subject: Re: [PATCH 3/3] ring-buffer: add design document
Date: Thu, 11 Jun 2009 20:46:20 -0700 [thread overview]
Message-ID: <4A31CF8C.6060609@zytor.com> (raw)
In-Reply-To: <1244776417.5320.160.camel@yhuang-dev.sh.intel.com>
Huang Ying wrote:
>
> 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?
>
Well, we still support it (UP only, though.) It all depends on if there
is a fallback that is good enough.
-hpa
--
H. Peter Anvin, Intel Open Source Technology Center
I work for Intel. I don't speak on their behalf.
next prev parent reply other threads:[~2009-06-12 3:55 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-06-10 19:53 [PATCH 0/3] [GIT PULL][for 2.6.32] lockless ring buffer Steven Rostedt
2009-06-10 19:53 ` [PATCH 1/3] ring-buffer: make the buffer a true circular link list Steven Rostedt
2009-06-11 1:12 ` Lai Jiangshan
2009-06-11 2:00 ` Steven Rostedt
2009-06-11 3:25 ` Lai Jiangshan
2009-06-11 3:35 ` Steven Rostedt
2009-06-10 19:53 ` [PATCH 2/3] ring-buffer: make lockless Steven Rostedt
2009-06-10 19:53 ` [PATCH 3/3] ring-buffer: add design document Steven Rostedt
2009-06-10 22:13 ` Mathieu Desnoyers
2009-06-11 1:55 ` Steven Rostedt
2009-06-11 3:51 ` Mathieu Desnoyers
2009-06-11 3:59 ` Mathieu Desnoyers
2009-06-11 4:15 ` Steven Rostedt
2009-06-11 18:09 ` Mathieu Desnoyers
2009-06-11 0:51 ` Huang Ying
2009-06-11 0:54 ` H. Peter Anvin
2009-06-11 1:58 ` Steven Rostedt
2009-06-11 2:33 ` Huang Ying
2009-06-11 2:38 ` Mathieu Desnoyers
2009-06-12 3:13 ` Huang Ying
2009-06-12 3:46 ` H. Peter Anvin [this message]
2009-06-11 3:15 ` Hidetoshi Seto
2009-06-11 3:25 ` Steven Rostedt
2009-06-13 1:54 ` Frederic Weisbecker
2009-06-13 2:16 ` Steven Rostedt
2009-06-13 22:36 ` Frederic Weisbecker
2009-06-14 12:39 ` Steven Rostedt
2009-06-15 0:05 ` Frederic Weisbecker
2009-06-15 0:56 ` Frederic Weisbecker
-- strict thread matches above, loose matches on Subject: below --
2009-07-08 20:13 [PATCH 0/3] [GIT PULL] rebase of lockless ring buffer Steven Rostedt
2009-07-08 20:13 ` [PATCH 3/3] ring-buffer: add design document Steven Rostedt
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=4A31CF8C.6060609@zytor.com \
--to=hpa@zytor.com \
--cc=acme@redhat.com \
--cc=akpm@linux-foundation.org \
--cc=compudj@krystal.dyndns.org \
--cc=fweisbec@gmail.com \
--cc=hch@infradead.org \
--cc=laijs@cn.fujitsu.com \
--cc=linux-kernel@vger.kernel.org \
--cc=lizf@cn.fujitsu.com \
--cc=mbligh@mbligh.org \
--cc=mhiramat@redhat.com \
--cc=mingo@elte.hu \
--cc=peterz@infradead.org \
--cc=rostedt@goodmis.org \
--cc=seto.hidetoshi@jp.fujitsu.com \
--cc=tglx@linutronix.de \
--cc=tytso@mit.edu \
--cc=ying.huang@intel.com \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.