linux-kernel - Re: Re-implement MCE log ring buffer as per-CPU ring buffer

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <49EF00FA.8090204@linux.intel.com>
Date:	Wed, 22 Apr 2009 13:35:22 +0200
From:	Andi Kleen <ak@...ux.intel.com>
To:	Ingo Molnar <mingo@...e.hu>
CC:	Robert Richter <robert.richter@....com>,
	Huang Ying <ying.huang@...el.com>,
	"H. Peter Anvin" <hpa@...or.com>,
	Thomas Gleixner <tglx@...utronix.de>,
	linux-kernel@...r.kernel.org,
	Hidetoshi Seto <seto.hidetoshi@...fujitsu.com>
Subject: Re: Re-implement MCE log ring buffer as per-CPU ring buffer

Ingo Molnar wrote:
> * Robert Richter <robert.richter@....com> wrote:
> 
>> On 22.04.09 11:22:59, Ingo Molnar wrote:
>>> * Huang Ying <ying.huang@...el.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

--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/