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]

Message-ID: <20130531122443.GB17843@nazgul.tnic>
Date:	Fri, 31 May 2013 14:24:43 +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:07:20PM +0200, Ingo Molnar wrote:
> For that I'd like to create a persistent event that just keeps
> running, and to which I can occasionally attach to read-only to see
> what's going on and maybe attach to it read-write to drain the trace
> entries. I.e. basically a global trace buffer. How do I achieve that
> with this new tooling?

I have a patch which adds persistent_events= kernel command line param
and uses the same syntax as trace_event=. Rostedt has seen it already, I
need to incorporate his comments and send it out next week.

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