linux-kernel - Re: [PATCH 1/2] perf: Add persistent events

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:	Sun, 23 May 2010 20:54:11 +0200
From:	Borislav Petkov <bp@...en8.de>
To:	Peter Zijlstra <peterz@...radead.org>
Cc:	Ingo Molnar <mingo@...e.hu>,
	Frederic Weisbecker <fweisbec@...il.com>,
	Steven Rostedt <rostedt@...dmis.org>,
	Arnaldo Carvalho de Melo <acme@...hat.com>,
	Lin Ming <ming.m.lin@...el.com>, linux-kernel@...r.kernel.org
Subject: Re: [PATCH 1/2] perf: Add persistent events

From: Peter Zijlstra <peterz@...radead.org>
Date: Sun, May 23, 2010 at 08:40:47PM +0200

> > > A persistent event would simply be a regular event, but created by the
> > > kernel and not tied to a file-desc's lifetime.
> > 
> > So you're saying the trace_mce_record() tracepoint for example should
> > be created completely internally in the kernel and cease to be a
> > tracepoint? Will it still be able to be selected by perf -e?
> 
> No, it should be a regular tracepoint as far as tracepoints are
> concerned.
> 
> But the only thing persistence should add is an instance of a
> perf_event, it should not modify either the perf_event nor the
> tracepoint code.

which means that subsystems which initialize earlier than perf (mce,
for example) should have to be notified when perf is ready so that they
could register a persistent event. How does that sound?

-- 
Regards/Gruss,
    Boris.
--
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/