From: Frederic Weisbecker <fweisbec@gmail.com>
To: Ingo Molnar <mingo@elte.hu>
Cc: LKML <linux-kernel@vger.kernel.org>,
Frederic Weisbecker <fweisbec@gmail.com>,
Steven Rostedt <rostedt@goodmis.org>
Subject: [PATCH 0/2] tracing/stat: cleanups, latency
Date: Sat, 16 May 2009 07:18:42 +0200 [thread overview]
Message-ID: <1242451124-5466-1-git-send-email-fweisbec@gmail.com> (raw)
Hi,
Here are two patches for the stat tracing.
I would also like to do more work on the stat tracing to make
it able to manage by itself the entries for the tracers, ie:
the memory allocation, accesses, locking, releases, etc...
And the workqueue tracer would be a good base to work on it.
Then Ingo, if you pull this, could you please also merge tracing/core
into tracing/workqueue, so that I can continue the work
with these patches and prepare pull requests against tracing/workqueue.
It should be mergeable without conflicts, I just applied the raw patches
from this pull-request into tracing/workqueue and it was fine.
Thanks,
Frederic.
The following changes since commit 5872144f64b34a5942f6b4acedc90b02de72c58b:
Li Zefan (1):
tracing/filters: fix off-by-one bug
are available in the git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/frederic/random-tracing.git
tracing/core
Frederic Weisbecker (2):
tracing/stat: replace trace_stat_session by stat_session
tracing/stat: replace linked list by an rbtree for sorting
kernel/trace/trace_stat.c | 166 ++++++++++++++++++++++++++++++--------------
1 files changed, 113 insertions(+), 53 deletions(-)
next reply other threads:[~2009-05-16 5:18 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-05-16 5:18 Frederic Weisbecker [this message]
2009-05-16 5:18 ` [PATCH 1/2] tracing/stat: replace trace_stat_session by stat_session Frederic Weisbecker
2009-05-16 5:18 ` [PATCH 2/2] tracing/stat: replace linked list by an rbtree for sorting Frederic Weisbecker
2009-05-18 8:20 ` [PATCH 0/2] tracing/stat: cleanups, latency Ingo Molnar
2009-05-18 14:09 ` 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=1242451124-5466-1-git-send-email-fweisbec@gmail.com \
--to=fweisbec@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--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
all inboxes | Powered by JetHome®