public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Huang Ying <ying.huang@intel.com>
To: Hidetoshi Seto <seto.hidetoshi@jp.fujitsu.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>
Subject: Re: [PATCH -v5] x86: MCE: Re-implement MCE log ring buffer as per-CPU ring buffer
Date: Thu, 11 Jun 2009 14:48:25 +0800	[thread overview]
Message-ID: <1244702905.5320.9.camel@yhuang-dev.sh.intel.com> (raw)
In-Reply-To: <4A30A779.4040101@jp.fujitsu.com>

On Thu, 2009-06-11 at 14:43 +0800, Hidetoshi Seto wrote:
> Huang Ying wrote:
> > Re-implement MCE log ring buffer as per-CPU ring buffer for better
> > scalability.
> 
> It seems your patch implicitly includes some bug fix for tip/mce3.
> Still discussion of generic lockless ring buffer is going on, so how
> about dividing the patch into 2 pieces, for improvement and for bug fix?
> 
> Maybe improvement part need to be reworked, so I pulled out the bug fix
> part from your patch.
> 
> If it's all right, I'd like to put this on top of tip/mce3 asap.

It is OK for me.

Best Regards,
Huang Ying


      reply	other threads:[~2009-06-11  6:48 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-06-08  7:11 [PATCH -v5] x86: MCE: Re-implement MCE log ring buffer as per-CPU ring buffer Huang Ying
2009-06-08  7:20 ` Ingo Molnar
2009-06-08  7:30   ` Huang Ying
2009-06-08  7:38     ` Ingo Molnar
2009-06-08  8:26       ` Huang Ying
2009-06-08  8:52         ` Ingo Molnar
2009-06-08 12:01         ` Steven Rostedt
2009-06-11  6:43 ` Hidetoshi Seto
2009-06-11  6:48   ` Huang Ying [this message]

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=1244702905.5320.9.camel@yhuang-dev.sh.intel.com \
    --to=ying.huang@intel.com \
    --cc=ak@linux.intel.com \
    --cc=hpa@zytor.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@elte.hu \
    --cc=seto.hidetoshi@jp.fujitsu.com \
    --cc=tglx@linutronix.de \
    /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