All of lore.kernel.org
 help / color / mirror / Atom feed
From: Andi Kleen <ak@linux.intel.com>
To: Ingo Molnar <mingo@elte.hu>
Cc: Robert Richter <robert.richter@amd.com>,
	Huang Ying <ying.huang@intel.com>,
	"H. Peter Anvin" <hpa@zytor.com>,
	Thomas Gleixner <tglx@linutronix.de>,
	linux-kernel@vger.kernel.org,
	Hidetoshi Seto <seto.hidetoshi@jp.fujitsu.com>
Subject: Re: Re-implement MCE log ring buffer as per-CPU ring buffer
Date: Wed, 22 Apr 2009 13:35:22 +0200	[thread overview]
Message-ID: <49EF00FA.8090204@linux.intel.com> (raw)
In-Reply-To: <20090422101911.GB1115@elte.hu>

Ingo Molnar wrote:
> * Robert Richter <robert.richter@amd.com> 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).
> 
> Yeah. I'd have suggested that once cleanups and unification is done 
> (which is still a long way out :-).

Hi Ingo,

If you can tell us clearly how to do this I can work on it. e.g.
if the scheme laid out in my earlier mail is acceptable and
I can port these patches to mce2 I mentioned and that can be hopefully
all done quickly.

However I don't agree with you stalling important hardware support
and bug fix code  for a long time just because you have something
half baked in tree and I hope you won't pursue such a policy.

-Andi


  reply	other threads:[~2009-04-22 11:35 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 [this message]
2009-04-22 11:30     ` Andi Kleen
2009-04-24  6:06     ` Huang Ying
2009-04-24 10:09       ` Robert Richter
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=49EF00FA.8090204@linux.intel.com \
    --to=ak@linux.intel.com \
    --cc=hpa@zytor.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@elte.hu \
    --cc=robert.richter@amd.com \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.