linux-kernel - Re: [PATCH 03/20] x86, mce: Add persistent MCE event

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] [day] [month] [year] [list]

Date:	Thu, 11 Nov 2010 18:30:48 +0100
From:	Ingo Molnar <mingo@...e.hu>
To:	Borislav Petkov <bp@...64.org>
Cc:	Peter Zijlstra <peterz@...radead.org>,
	Ben Gamari <bgamari@...il.com>,
	"acme@...radead.org" <acme@...radead.org>,
	"fweisbec@...il.com" <fweisbec@...il.com>,
	"rostedt@...dmis.org" <rostedt@...dmis.org>,
	"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>
Subject: Re: [PATCH 03/20] x86, mce: Add persistent MCE event


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

> On Thu, Nov 11, 2010 at 10:38:50AM -0500, Peter Zijlstra wrote:
> > On Thu, 2010-11-11 at 14:34 +0100, Borislav Petkov wrote:
> > > 3) enable the persistent event and stash its fd in some /sysfs member
> > > which the RAS daemon reads out and mmaps. This last one actually sounds
> > > pretty neat. 
> > 
> > Right, stashing the thing in sysfs, which you can open()+mmap() seems
> > the best way. Not sure you want to make it a RAS specific place, maybe a
> > generic persistent buffer place.
> > 
> > You'll get multiple files anyway, one per cpu, so maybe something like:
> > 
> > /sysfs/persistent_buffer/ras[0..n]
> 
> Yeah, or even integrate it even further into the events hierarchy like
> this:
> 
> /sys/.../cpu/events/mce		-> this is the trace_mce_record tracepoint
> /sys/.../cpu/events/mce_pers	-> persistent buffer fd
> 
> or an additional level further down
> 
> /sys/.../cpu/events/mce/persistent/...
> 
> or whatever.
> 
> Generally I don't care too much where we put it at the end.

It should be in a nice logical place though :-)

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/