[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20090923105252.GA32176@elte.hu>
Date: Wed, 23 Sep 2009 12:52:52 +0200
From: Ingo Molnar <mingo@...e.hu>
To: Frederic Weisbecker <fweisbec@...il.com>
Cc: LKML <linux-kernel@...r.kernel.org>,
Masami Hiramatsu <mhiramat@...hat.com>,
Steven Rostedt <rostedt@...dmis.org>,
Li Zefan <lizf@...fujitsu.com>
Subject: Re: [GIT PULL] tracing/kprobes: Kprobes core/tracing/profiling
updates
* Frederic Weisbecker <fweisbec@...il.com> wrote:
> Hi Ingo,
>
> Kprobes has been nicely improved lately. The x86 instruction decoder
> has been fixed to support cross builds and mmx instruction set,
> besides of a lot of various kprobes core fixes.
>
> The tracing part has evolved too, we can define human names for
> arguments and custom subsystem names for dynamic tracepoints.
>
> And also kprobes profiling and raw dynamic tracepoint samples are now
> supported through perf. Looks like most of the kernel parts are now in
> place for a perf support. Things are going to be focused on a perf
> kprobes tool to exploit that.
Nice progress. What's the expected timeline of exhaustive tools/perf/
support?
> Concerning this git tree, based on tip:/tracing/kprobes, I had to
> merge tracing/core inside few weeks ago because it needed build fixes
> that were in tracing/core (the merge commit provides the details). The
> tree is self contained but it's already async with recent upstream
> tracing updates. It means that merging upstream tree or tracing/core
> inside may result in non-trivial conflicts. I can handle them, or
> rebase the whole, as you prefer.
>
> The tree can be found at:
>
> git://git.kernel.org/pub/scm/linux/kernel/git/frederic/random-tracing.git
> tracing/kprobes
Would be nice to merge latest -git into this tree and resolve the
conflicts:
kernel/trace/Makefile
kernel/trace/trace.h
kernel/trace/trace_event_types.h
kernel/trace/trace_export.c
Then i could pull it into tip:tracing/kprobes for more testing.
Ingo
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists