Date: Fri, 31 May 2013 14:24:43 +0200
From: Borislav Petkov <bp@alien8.de>
To: Ingo Molnar <mingo@kernel.org>
Cc: Robert Richter <rric@kernel.org>,
        Arnaldo Carvalho de Melo <acme@ghostprotocols.net>,
        Peter Zijlstra <peterz@infradead.org>, Jiri Olsa <jolsa@redhat.com>,
        linux-kernel@vger.kernel.org,
        Robert Richter <robert.richter@calxeda.com>
Subject: Re: [PATCH 0/4] perf tools: Persistent events, changes for perf tool
 integration
Message-ID: <20130531122443.GB17843@nazgul.tnic>
References: <1369991785-10499-1-git-send-email-rric@kernel.org>
 <20130531120720.GA7885@gmail.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Disposition: inline
In-Reply-To: <20130531120720.GA7885@gmail.com>
User-Agent: Mutt/1.5.21 (2010-09-15)
Sender: linux-kernel-owner@vger.kernel.org
Content-Length: 822
Lines: 17

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@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/