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: <49EEFFDE.3030105@linux.intel.com>
Date:	Wed, 22 Apr 2009 13:30:38 +0200
From:	Andi Kleen <ak@...ux.intel.com>
To:	Robert Richter <robert.richter@....com>
CC:	Ingo Molnar <mingo@...e.hu>, 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


> You may also want to consider to use the in-kernel ring_buffer api
> (include/linux/ring_buffer.h).

Its semantics don't map very well to the machine check requirements.

I did an analysis of that in http://thread.gmane.org/gmane.linux.kernel/772928/focus=773452
AFAIK the reasons stated there are all still valid.

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