From: Frederic Weisbecker <fweisbec@gmail.com>
To: Ingo Molnar <mingo@elte.hu>
Cc: Li Zefan <lizf@cn.fujitsu.com>,
LKML <linux-kernel@vger.kernel.org>,
Steven Rostedt <rostedt@goodmis.org>
Subject: Re: [PATCH 0/2] tracing/stat: cleanups, latency
Date: Mon, 18 May 2009 16:09:45 +0200 [thread overview]
Message-ID: <20090518140943.GD4704@nowhere> (raw)
In-Reply-To: <20090518082051.GB10687@elte.hu>
On Mon, May 18, 2009 at 10:20:51AM +0200, Ingo Molnar wrote:
>
> * Frederic Weisbecker <fweisbec@gmail.com> wrote:
>
> > 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.
>
> sure, i've done that!
>
> > 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(-)
>
> Pulled, thanks Frederic.
>
> Note, i've rebased this on top of the tracing/workqueues topic and
> have merged both into tip:master. You can use tracing/stat as a Git
> basis. (assuming it survives today's testing in -tip without
> requiring a rebase)
>
> Ingo
Ok, thanks!
prev parent reply other threads:[~2009-05-18 14:09 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-05-16 5:18 [PATCH 0/2] tracing/stat: cleanups, latency Frederic Weisbecker
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 [this message]
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=20090518140943.GD4704@nowhere \
--to=fweisbec@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=lizf@cn.fujitsu.com \
--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