Re: [PATCH tracing/kprobes 3/6] ftrace: Fixtrace_remove_event_call() to lock trace_event_mutex
From: Ananth N Mavinakayanahalli
Date: Wed Sep 16 2009 - 00:54:32 EST
On Wed, Sep 16, 2009 at 06:05:12AM +0200, Frederic Weisbecker wrote:
> On Tue, Sep 15, 2009 at 11:17:30PM -0400, Steven Rostedt wrote:
> > On Mon, 2009-09-14 at 16:49 -0400, Masami Hiramatsu wrote:
...
> It's in tip:/tracing/kprobes, which is not merged into tip/master.
> I have some pending updates in my tracing/kprobes tree:
>
> Frederic Weisbecker (1):
> Merge commit 'tracing/core' into tracing/kprobes
>
> Masami Hiramatsu (16):
> kprobes/x86: Call BUG() when reentering probe into KPROBES_HIT_SS
> kprobes/x86-64: Allow to reenter probe on post_handler
> kprobes/x86: Fix to add __kprobes to in-kernel fault handing functions
> kprobes: Fix to add __kprobes to notify_die
> kprobes/x86-64: Fix to move common_interrupt to .kprobes.text
> kprobes: Prohibit to probe native_get_debugreg
> x86: Allow x86-32 instruction decoder selftest on x86-64
> x86: Remove unused config macros from instruction decoder selftest
> x86: Add MMX support for instruction decoder
> kprobes/x86-32: Move irq-exit functions to kprobes section
> x86/ptrace: Fix regs_get_argument_nth() to add correct offset
> tracing/kprobes: Fix probe offset to be unsigned
> tracing/kprobes: Cleanup kprobe tracer code.
> tracing/kprobes: Add event profiling support
> tracing/kprobes: Add argument name support
> tracing/kprobes: Show event name in trace output
>
> Plus the current set that I'm about to apply, if no problem arises.
> I should also merge one more time tip:tracing/core into it because
> it has developed another conflicts against it since then.
>
> Ingo, if you are fine with it, I'll send you a pull request
> soon.
Frederic,
Could you please add http://lkml.org/lkml/2009/9/15/13 too?
Ananth
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/