Re: Re-implement MCE log ring buffer as per-CPU ring buffer

From: Huang Ying
Date: Mon Apr 27 2009 - 03:50:19 EST


On Fri, 2009-04-24 at 21:36 +0800, Steven Rostedt wrote:
> On Fri, 24 Apr 2009, Robert Richter wrote:
> > >
> > > It seems that ring_buffer is not NMI-safe, while mcelog buffer will be
> > > used in NMI context and interrupt context. When will ring_buffer to be
> > > NMI-safe?
> >
> > You can use it in nmi context with separate read and write
> > buffers. See this patch description:
> > 6dad828b76c7224a22ddc9ce7aa495d994f03b31
> >
> > Not sure if somebody will make the ring_buffer non-locking.
>
> It already is ;-)
>
> I've put in for a patent application on the algorithm so I must wait till
> it is processed before I can release the code.

When will it be merged by mainline kernel? Do you have a plan?

We do have some scalability issues of current mcelog implementation, and
hopes that can be solved as soon as possible, perhaps for 2.6.31?

Best Regards,
Huang Ying

Attachment: signature.asc
Description: This is a digitally signed message part