[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-Id: <1244449602.8361.587.camel@yhuang-dev.sh.intel.com>
Date: Mon, 08 Jun 2009 16:26:42 +0800
From: Huang Ying <ying.huang@...el.com>
To: Ingo Molnar <mingo@...e.hu>
Cc: Steven Rostedt <rostedt@...dmis.org>,
"H. Peter Anvin" <hpa@...or.com>,
Thomas Gleixner <tglx@...utronix.de>,
Andi Kleen <ak@...ux.intel.com>,
Hidetoshi Seto <seto.hidetoshi@...fujitsu.com>,
"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>
Subject: Re: [PATCH -v5] x86: MCE: Re-implement MCE log ring buffer as
per-CPU ring buffer
On Mon, 2009-06-08 at 15:38 +0800, Ingo Molnar wrote:
> * Huang Ying <ying.huang@...el.com> wrote:
>
> > On Mon, 2009-06-08 at 15:20 +0800, Ingo Molnar wrote:
> > > * Huang Ying <ying.huang@...el.com> wrote:
> > >
> > > > Re-implement MCE log ring buffer as per-CPU ring buffer for better
> > > > scalability.
> > >
> > > this should be done using the generic ring-buffer code - see
> > > include/linux/ring_buffer.h. Having a private implementation in
> > > architecture code is not really acceptable.
> >
> > MCE log ring buffer need to be NMI-safe, while current generic
> > ring-buffer code is not NMI safe. [...]
>
> Then please work with Steve to make it NMI safe (or do so yourself)
> - i've Cc:-ed him - that way we help the core kernel: one of its
> essential facilities will get one more user. We dont put private,
> open-coded ring-buffer facilities into architecture code.
Steve have said he has a NMI-safe solution, but it is under patent
application. It seems that patent application will take very long time,
so we decide to enhance mce log buffer instead of waiting.
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