Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1755751AbZD0O2E (ORCPT ); Mon, 27 Apr 2009 10:28:04 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S1753361AbZD0O1w (ORCPT ); Mon, 27 Apr 2009 10:27:52 -0400 Received: from hrndva-omtalb.mail.rr.com ([71.74.56.125]:44287 "EHLO hrndva-omtalb.mail.rr.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751763AbZD0O1w (ORCPT ); Mon, 27 Apr 2009 10:27:52 -0400 Date: Mon, 27 Apr 2009 10:27:49 -0400 (EDT) From: Steven Rostedt X-X-Sender: rostedt@gandalf.stny.rr.com To: Huang Ying cc: Robert Richter , Ingo Molnar , "H. Peter Anvin" , Thomas Gleixner , Andi Kleen , "linux-kernel@vger.kernel.org" , Hidetoshi Seto Subject: Re: Re-implement MCE log ring buffer as per-CPU ring buffer In-Reply-To: <1240818596.6842.1001.camel@yhuang-dev.sh.intel.com> Message-ID: References: <1240391484.6842.474.camel@yhuang-dev.sh.intel.com> <20090422092259.GC18226@elte.hu> <20090422101600.GL3226@erda.amd.com> <1240553210.6842.871.camel@yhuang-dev.sh.intel.com> <20090424100943.GJ27264@erda.amd.com> <1240818596.6842.1001.camel@yhuang-dev.sh.intel.com> User-Agent: Alpine 2.00 (DEB 1167 2008-08-23) MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1318 Lines: 36 On Mon, 27 Apr 2009, Huang Ying wrote: > 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? Yes, I plan on being able to post it before the 31 merge window opens. I'll ping the lawyer to expedite the process. -- Steve -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/