From: Peter Zijlstra <a.p.zijlstra@chello.nl>
To: Frederic Weisbecker <fweisbec@gmail.com>
Cc: Steven Rostedt <rostedt@goodmis.org>,
David Sharp <dhsharp@google.com>,
Vaibhav Nagarnaik <vnagarnaik@google.com>,
Paul Menage <menage@google.com>, Li Zefan <lizf@cn.fujitsu.com>,
Stephane Eranian <eranian@google.com>,
Andrew Morton <akpm@linux-foundation.org>,
Michael Rubin <mrubin@google.com>, Ken Chen <kenchen@google.com>,
linux-kernel@vger.kernel.org,
containers@lists.linux-foundation.org,
Thomas Gleixner <tglx@linutronix.de>, Ingo Molnar <mingo@elte.hu>,
Arnaldo Carvalho de Melo <acme@redhat.com>
Subject: Re: [RFC] tracing: Adding cgroup aware tracing functionality
Date: Fri, 08 Apr 2011 16:07:52 +0200 [thread overview]
Message-ID: <1302271672.9086.155.camel@twins> (raw)
In-Reply-To: <20110408134537.GA1967@nowhere>
On Fri, 2011-04-08 at 15:45 +0200, Frederic Weisbecker wrote:
>
> I bet this idea is not controversial. What has yet to be solved is
> the debate on the writers that can run in overwriting mode at the same
> time we have readers. Which comes along debates on using subbuffers,
> etc..
>
> But I guess we can solve that along the way?
Dunno, but the much larger point is how ftrace is going to want to do
multiple sessions and keep session context etc (what events to where).
I've only heard some vague hand waving there but never heard anything
concrete.
next prev parent reply other threads:[~2011-04-08 14:08 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-04-06 18:50 [RFC] tracing: Adding cgroup aware tracing functionality Vaibhav Nagarnaik
2011-04-07 1:33 ` Frederic Weisbecker
2011-04-07 3:17 ` Vaibhav Nagarnaik
2011-04-07 12:06 ` Frederic Weisbecker
2011-04-07 20:22 ` David Sharp
2011-04-07 21:32 ` Frederic Weisbecker
2011-04-07 22:42 ` David Sharp
2011-04-08 0:28 ` Frederic Weisbecker
2011-04-08 7:37 ` Steven Rostedt
2011-04-08 13:45 ` Frederic Weisbecker
2011-04-08 14:07 ` Peter Zijlstra [this message]
2011-04-08 18:32 ` Michael Rubin
2011-04-08 20:27 ` Justin TerAvest
2011-04-08 14:07 ` Peter Zijlstra
2011-04-08 17:02 ` Steven Rostedt
2011-04-09 11:08 ` Peter Zijlstra
2011-04-08 19:00 ` Frederic Weisbecker
2011-04-08 20:38 ` Frederic Weisbecker
2011-04-08 21:41 ` David Sharp
2011-04-12 21:38 ` Frederic Weisbecker
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1302271672.9086.155.camel@twins \
--to=a.p.zijlstra@chello.nl \
--cc=acme@redhat.com \
--cc=akpm@linux-foundation.org \
--cc=containers@lists.linux-foundation.org \
--cc=dhsharp@google.com \
--cc=eranian@google.com \
--cc=fweisbec@gmail.com \
--cc=kenchen@google.com \
--cc=linux-kernel@vger.kernel.org \
--cc=lizf@cn.fujitsu.com \
--cc=menage@google.com \
--cc=mingo@elte.hu \
--cc=mrubin@google.com \
--cc=rostedt@goodmis.org \
--cc=tglx@linutronix.de \
--cc=vnagarnaik@google.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).