From: "Frédéric Weisbecker" <fweisbec@gmail.com>
To: "Steven Rostedt" <rostedt@goodmis.org>
Cc: "Ingo Molnar" <mingo@elte.hu>, "Tim Bird" <tim.bird@am.sony.com>,
"Linux Kernel" <linux-kernel@vger.kernel.org>,
"Peter Zijlstra" <a.p.zijlstra@chello.nl>
Subject: Re: [PATCH] tracing/function-branch-tracer: enhancements for the trace output
Date: Thu, 27 Nov 2008 16:51:06 +0100 [thread overview]
Message-ID: <c62985530811270751o3593e409ia35d7060120fbc90@mail.gmail.com> (raw)
In-Reply-To: <alpine.DEB.1.10.0811271028260.18691@gandalf.stny.rr.com>
2008/11/27 Steven Rostedt <rostedt@goodmis.org>:
> No, please keep the CPU # first. If anything, you will want to separate
> out the CPUs first. Otherwise you will see things all mixed up.
So perhaps between CPU and time?
I don't really like it after the time, not so easy to find....
> Hmm, I could also add a per cpu files.
>
> debugfs/tracing/buffers/cpu0
> debugfs/tracing/buffers/cpu1
> debugfs/tracing/buffers/cpu2
> debugfs/tracing/buffers/cpu3
That would be useful indeed, as the ftrace_trace_pid on this tracer.
But I wonder about the cost of double function tracing in this case.
Your idea of a tgid;pid would be nice (with tgid || pid).
> That would print out the trace for a single CPU.
>
> BTW, I'm really not here. I'm on holiday eating turkeys.
next prev parent reply other threads:[~2008-11-27 15:51 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-11-27 0:46 Frederic Weisbecker
2008-11-27 0:57 ` Frédéric Weisbecker
2008-11-27 1:08 ` Steven Rostedt
2008-11-27 12:53 ` Frédéric Weisbecker
2008-11-27 10:19 ` Peter Zijlstra
2008-11-27 14:53 ` Frédéric Weisbecker
2008-11-27 15:05 ` Ingo Molnar
2008-11-27 10:34 ` Ingo Molnar
2008-11-27 10:55 ` Peter Zijlstra
2008-11-27 11:29 ` Ingo Molnar
2008-11-27 13:18 ` Frédéric Weisbecker
2008-11-27 14:07 ` Steven Rostedt
2008-11-27 14:13 ` Ingo Molnar
2008-11-27 13:11 ` Frédéric Weisbecker
2008-11-27 14:03 ` Steven Rostedt
2008-11-27 13:06 ` Frédéric Weisbecker
2008-11-27 13:51 ` Ingo Molnar
2008-11-27 14:44 ` Frédéric Weisbecker
2008-11-27 14:46 ` Ingo Molnar
2008-11-27 14:58 ` Frédéric Weisbecker
2008-11-27 15:03 ` Ingo Molnar
2008-11-27 15:09 ` Frédéric Weisbecker
2008-11-27 15:31 ` Steven Rostedt
2008-11-27 15:51 ` Frédéric Weisbecker [this message]
2008-11-28 13:05 ` Ingo Molnar
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=c62985530811270751o3593e409ia35d7060120fbc90@mail.gmail.com \
--to=fweisbec@gmail.com \
--cc=a.p.zijlstra@chello.nl \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=rostedt@goodmis.org \
--cc=tim.bird@am.sony.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
all inboxes | Powered by JetHome®