From: Andi Kleen <ak@linux.intel.com>
To: "H. Peter Anvin" <hpa@zytor.com>
Cc: Ingo Molnar <mingo@elte.hu>, Huang Ying <ying.huang@intel.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 II
Date: Wed, 29 Apr 2009 21:15:00 +0200 [thread overview]
Message-ID: <49F8A734.8050106@linux.intel.com> (raw)
In-Reply-To: <49EF3DE2.6000201@zytor.com>
H. Peter Anvin wrote:
> Andi Kleen wrote:
>> And then restart here? Add 32bit workarounds, add hook
>> to initialize p5/winchip, make 64bit code 32bit clean.
>> That can come straight from my patchkit. I can do that
>> if there is interest.
>>
>
> Could you come up with a tree we can look at?
Sorry for taking longer, had to fight some infrastructure issues.
I merged the two trees in
git://git.kernel.org/pub/scm/linux/kernel/git/ak/linux-mce-2.6.git mce-32bit-merge
This is my old 32bit mce unification tree forward ported to mce2 and some fixes
for the code in mce2. This is currently with Kconfig for old/new, deprecation
of old for .32 (could be done directly too, but doing it with this additional
step seems safer to me because it will allow easier debugging)
This currently includes the two error injection patches as last (used
for testing), those can be dropped/added later of course too.
If this is ok I can respin the rest of the mce patches on top of that
tree.
-Andi
next prev parent reply other threads:[~2009-04-29 19:15 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
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 ` Andi Kleen [this message]
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=49F8A734.8050106@linux.intel.com \
--to=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 \
--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