linux-kernel - Re: [PATCH 0/4] perf tools: Persistent events, changes for perf tool integration

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:	Fri, 31 May 2013 17:31:44 +0200
From:	Borislav Petkov <bp@...en8.de>
To:	Ingo Molnar <mingo@...nel.org>
Cc:	Robert Richter <rric@...nel.org>,
	Arnaldo Carvalho de Melo <acme@...stprotocols.net>,
	Peter Zijlstra <peterz@...radead.org>,
	Jiri Olsa <jolsa@...hat.com>, linux-kernel@...r.kernel.org,
	Robert Richter <robert.richter@...xeda.com>
Subject: Re: [PATCH 0/4] perf tools: Persistent events, changes for perf tool
 integration

On Fri, May 31, 2013 at 02:48:05PM +0200, Ingo Molnar wrote:
> A kernel command line does not make it very practical - this needs to
> be accessible from tooling ...

It will be accessible from tooling since the event is always enabled and
with the persistent pmu you spacify that you want to consume already
created buffers, i.e. the persistent event.

However, you need to be able to enable such event as early as possible
for tasks like boot tracing. I don't care if it is a kernel command line
param or something else - in the end of the day we need a mechanism
to say "enable this event the earliest moment possible, after you've
enabled the perf subsystem."

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