From: Frederic Weisbecker on
On Wed, May 26, 2010 at 05:22:17PM +0800, Li Zefan wrote:
> We have been resisting new ftrace plugins and removing existing
> ones, and kmemtrace has been superseded by kmem trace events
> and perf-kmem, so we remove it.
>
> Signed-off-by: Li Zefan <lizf(a)cn.fujitsu.com>
> Acked-by: Pekka Enberg <penberg(a)cs.helsinki.fi>
> ---
> Documentation/ABI/testing/debugfs-kmemtrace | 71 ----
> Documentation/trace/kmemtrace.txt | 126 -------
> MAINTAINERS | 7 -
> include/linux/kmemtrace.h | 25 --
> include/linux/slab_def.h | 3 +-
> include/linux/slub_def.h | 3 +-
> init/main.c | 2 -
> kernel/trace/Kconfig | 20 -
> kernel/trace/kmemtrace.c | 529 ---------------------------
> kernel/trace/trace.h | 13 -
> kernel/trace/trace_entries.h | 35 --
> mm/slab.c | 1 -
> mm/slub.c | 1 -
> 13 files changed, 4 insertions(+), 832 deletions(-)
> delete mode 100644 Documentation/ABI/testing/debugfs-kmemtrace
> delete mode 100644 Documentation/trace/kmemtrace.txt
> delete mode 100644 include/linux/kmemtrace.h
> delete mode 100644 kernel/trace/kmemtrace.c



Thanks!

Just one thing: you forgot to update the kernel/trace/Makefile

--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo(a)vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
From: Christoph Hellwig on
On Wed, May 26, 2010 at 05:22:17PM +0800, Li Zefan wrote:
> We have been resisting new ftrace plugins and removing existing
> ones, and kmemtrace has been superseded by kmem trace events
> and perf-kmem, so we remove it.

While you're at it also care to remove the blk ftrace plugin? We have
the old blktrace ioctl interface and the trace events as better
alternatives.

--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo(a)vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
From: Frederic Weisbecker on
On Wed, May 26, 2010 at 06:16:17AM -0400, Christoph Hellwig wrote:
> On Wed, May 26, 2010 at 05:22:17PM +0800, Li Zefan wrote:
> > We have been resisting new ftrace plugins and removing existing
> > ones, and kmemtrace has been superseded by kmem trace events
> > and perf-kmem, so we remove it.
>
> While you're at it also care to remove the blk ftrace plugin? We have
> the old blktrace ioctl interface and the trace events as better
> alternatives.


But does the userspace tool support them?

--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo(a)vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
From: Christoph Hellwig on
On Wed, May 26, 2010 at 12:18:38PM +0200, Frederic Weisbecker wrote:
> But does the userspace tool support them?

The blktrace userspace tool only uses the ioctl/debugfs code.

--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo(a)vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
From: Frederic Weisbecker on
On Wed, May 26, 2010 at 06:24:46AM -0400, Christoph Hellwig wrote:
> On Wed, May 26, 2010 at 12:18:38PM +0200, Frederic Weisbecker wrote:
> > But does the userspace tool support them?
>
> The blktrace userspace tool only uses the ioctl/debugfs code.
>


But which debugfs code? Nothing related to $(DEBUGFS)/tracing right?

--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo(a)vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/