From: Frederic Weisbecker <fweisbec@gmail.com>
To: Ingo Molnar <mingo@elte.hu>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Steven Rostedt <rostedt@goodmis.org>,
Pekka Enberg <penberg@cs.helsinki.fi>,
Eduard - Gabriel Munteanu <eduard.munteanu@linux360.ro>,
fweisbec@gmail.com
Subject: [PATCH 0/2] tracing/stat handling updates
Date: Wed, 31 Dec 2008 16:41:48 +0100 [thread overview]
Message-ID: <20081231154147.GB5748@nowhere> (raw)
After a quick look on the need of stats tracers, it looks like it is often
needed to have several stat modes/files for a single tracer.
The current tracing stat API doesn't support more than one stat file per tracer.
The first patch makes the tracing/stat Api reentrant and let a tracer able
implement more than one stat file.
The second one adapts this Api to the branch tracer.
kernel/trace/trace.h | 35 ++++---
kernel/trace/trace_branch.c | 69 +++++--------
kernel/trace/trace_stat.c | 229 +++++++++++++++++++++++++++++++------------
3 files changed, 216 insertions(+), 117 deletions(-)
reply other threads:[~2008-12-31 15:42 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20081231154147.GB5748@nowhere \
--to=fweisbec@gmail.com \
--cc=eduard.munteanu@linux360.ro \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=penberg@cs.helsinki.fi \
--cc=rostedt@goodmis.org \
/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