linux-kernel - Re: RAS trace event proto

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: <20120221145943.GB15515@aftab>
Date:	Tue, 21 Feb 2012 15:59:43 +0100
From:	Borislav Petkov <bp@...64.org>
To:	Steven Rostedt <rostedt@...dmis.org>
Cc:	Mauro Carvalho Chehab <mchehab@...hat.com>,
	Ingo Molnar <mingo@...e.hu>, Tony Luck <tony.luck@...el.com>,
	edac-devel <linux-edac@...r.kernel.org>,
	LKML <linux-kernel@...r.kernel.org>
Subject: Re: RAS trace event proto

On Tue, Feb 21, 2012 at 09:48:18AM -0500, Steven Rostedt wrote:
> On Tue, 2012-02-21 at 15:12 +0100, Borislav Petkov wrote:
> 
> > > Also, folding everything into just one string prevents (or make hard) the usage of
> > > the perf filters, for example, to filter only the errors at the memory controller 1.
> > 
> > Huh, because you can't grep through the trace anymore...?
> > 
> 
> I believe Mauro is talking about the tracing filters used by both perf
> and ftrace that lets you ignore trace events when the contents of the
> event does not match the filter. This is filtering out events before
> they go to the buffer.

Oh ok, in that case we could filter the errors - if needed - before they
get even reported. I say "if needed" because normally we want to collect
all hw errors in the trace, IMHO.

-- 
Regards/Gruss,
Boris.

Advanced Micro Devices GmbH
Einsteinring 24, 85609 Dornach
GM: Alberto Bozzo
Reg: Dornach, Landkreis Muenchen
HRB Nr. 43632 WEEE Registernr: 129 19551
--
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/