public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Robert Richter <robert.richter@amd.com>
To: Huang Ying <ying.huang@intel.com>
Cc: Ingo Molnar <mingo@elte.hu>, "H. Peter Anvin" <hpa@zytor.com>,
	Thomas Gleixner <tglx@linutronix.de>,
	Andi Kleen <ak@linux.intel.com>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
	Hidetoshi Seto <seto.hidetoshi@jp.fujitsu.com>,
	Steven Rostedt <rostedt@goodmis.org>
Subject: Re: Re-implement MCE log ring buffer as per-CPU ring buffer
Date: Fri, 24 Apr 2009 12:09:43 +0200	[thread overview]
Message-ID: <20090424100943.GJ27264@erda.amd.com> (raw)
In-Reply-To: <1240553210.6842.871.camel@yhuang-dev.sh.intel.com>

On 24.04.09 14:06:50, Huang Ying wrote:
> On Wed, 2009-04-22 at 18:16 +0800, Robert Richter wrote:
> > On 22.04.09 11:22:59, Ingo Molnar wrote:
> > > 
> > > * Huang Ying <ying.huang@intel.com> wrote:
> > > 
> > > > Re-implement MCE log ring buffer as per-CPU ring buffer for better 
> > > > scalability. Basic design is as follow:
> > > 
> > > Before changing anything substantial in the MCE code it would be 
> > > necessary to clean up and then unify the 32-bit and 64-bit side of 
> > > the MCE code first. (Which essentially means extending the 
> > > 64-bit-only code to 32-bit)
> > 
> > You may also want to consider to use the in-kernel ring_buffer api
> > (include/linux/ring_buffer.h).
> 
> 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.

-Robert

-- 
Advanced Micro Devices, Inc.
Operating System Research Center
email: robert.richter@amd.com


  reply	other threads:[~2009-04-24 10:10 UTC|newest]

Thread overview: 29+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-04-22  9:11 Re-implement MCE log ring buffer as per-CPU ring buffer Huang Ying
2009-04-22  9:22 ` Ingo Molnar
2009-04-22 10:16   ` Robert Richter
2009-04-22 10:19     ` Ingo Molnar
2009-04-22 11:35       ` Andi Kleen
2009-04-22 11:30     ` Andi Kleen
2009-04-24  6:06     ` Huang Ying
2009-04-24 10:09       ` Robert Richter [this message]
2009-04-24 13:36         ` Steven Rostedt
2009-04-27  7:49           ` Huang Ying
2009-04-27  7:53             ` Andi Kleen
2009-04-27 14:39               ` Steven Rostedt
2009-04-27 14:44                 ` Davide Libenzi
2009-04-27 14:57                   ` Steven Rostedt
2009-04-27 16:14                   ` Valdis.Kletnieks
2009-04-27 17:05                 ` Theodore Tso
2009-04-27 20:06                   ` H. Peter Anvin
2009-04-27 14:27             ` Steven Rostedt
2009-04-27 14:36               ` Patenting kernel patches was " Andi Kleen
2009-04-27 14:49                 ` Steven Rostedt
2009-04-27 15:33                 ` Alan Cox
2009-04-27  0:58         ` Huang Ying
2009-04-22 11:20   ` Andi Kleen
2009-04-22 15:55     ` H. Peter Anvin
2009-04-22 15:58       ` Andi Kleen
2009-04-29 19:15       ` Re-implement MCE log ring buffer as per-CPU ring buffer II Andi Kleen
2009-04-30  7:38         ` 32bit mce unification (Re: Re-implement MCE log ring buffer as per-CPU ring buffer II) Hidetoshi Seto
2009-04-22 11:11 ` Re-implement MCE log ring buffer as per-CPU ring buffer Andi Kleen
2009-04-24  5:51   ` Huang Ying

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=20090424100943.GJ27264@erda.amd.com \
    --to=robert.richter@amd.com \
    --cc=ak@linux.intel.com \
    --cc=hpa@zytor.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@elte.hu \
    --cc=rostedt@goodmis.org \
    --cc=seto.hidetoshi@jp.fujitsu.com \
    --cc=tglx@linutronix.de \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox