linux-kernel - Re: [PATCH -v5] x86: MCE: 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: <1244446222.8361.584.camel@yhuang-dev.sh.intel.com>
Date:	Mon, 08 Jun 2009 15:30:22 +0800
From:	Huang Ying <ying.huang@...el.com>
To:	Ingo Molnar <mingo@...e.hu>
Cc:	"H. Peter Anvin" <hpa@...or.com>,
	Thomas Gleixner <tglx@...utronix.de>,
	Andi Kleen <ak@...ux.intel.com>,
	Hidetoshi Seto <seto.hidetoshi@...fujitsu.com>,
	"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>
Subject: Re: [PATCH -v5] x86: MCE: Re-implement MCE log ring buffer as
 per-CPU ring buffer

On Mon, 2009-06-08 at 15:20 +0800, Ingo Molnar wrote:
> * Huang Ying <ying.huang@...el.com> wrote:
> 
> > Re-implement MCE log ring buffer as per-CPU ring buffer for better 
> > scalability.
> 
> this should be done using the generic ring-buffer code - see 
> include/linux/ring_buffer.h. Having a private implementation in 
> architecture code is not really acceptable.

MCE log ring buffer need to be NMI-safe, while current generic
ring-buffer code is not NMI safe. Maybe we can use the generic
ring-buffer code after it goes NMI-safe. But for now, I think this patch
is better.

Best Regards,
Huang Ying


--
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/