linux-kernel - Re: [PATCH 4/4] x86, mce: Have MCE persistent event off by default for now

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]

Date:	Tue, 3 May 2011 21:56:58 +0200
From:	Ingo Molnar <mingo@...e.hu>
To:	Borislav Petkov <bp@...64.org>
Cc:	"Luck, Tony" <tony.luck@...el.com>,
	Peter Zijlstra <peterz@...radead.org>,
	Arnaldo Carvalho de Melo <acme@...radead.org>,
	Steven Rostedt <rostedt@...dmis.org>,
	Frederic Weisbecker <fweisbec@...il.com>,
	Mauro Carvalho Chehab <mchehab@...hat.com>,
	EDAC devel <linux-edac@...r.kernel.org>,
	LKML <linux-kernel@...r.kernel.org>
Subject: Re: [PATCH 4/4] x86, mce: Have MCE persistent event off by default
 for now


* Borislav Petkov <bp@...64.org> wrote:

> > Probably make some sense to delay such a message (so that in the boot case 
> > we give the daemon a chance to get started before complaining that it 
> > hasn't shown up for work).
> 
> Yep, that and also I need to address the case for catching earlybird MCEs, 
> when perf hasn't been initialized yet. I'm thinking we could reuse the mcelog 
> buffer and feed those into the RAS daemon after init. Something like that.

I'd suggest that to solve that problem we initialize events earlier and allow 
something like a small static buffer backed event which does not need any 
dynamic memory so it can be enabled early on and can receive events, at the 
same time the MCE hw bits are enabled.

That event can get a larger buffer once the system is more fully up - without 
losing whatever events it is already holding.

Thanks,

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