[for-next][PATCH 0/7] tracing: Add new filesystem tracefs

[Steven Rostedt]

Al,

I know that you do not like the releasing of the parent i_mutex lock.
But it is no different than what we do today, except that we move the
release out of the tracing code and into the tracefs code.

This still gives us the separate tracefs filesystem that will let
users mount it without needing to mount debugfs, so I want to get this
into 3.20.

These are the patches that I plan on submitting, and will soon be adding
to my linux-next branch, to be included in linux-next.

-- Steve


  git://git.kernel.org/pub/scm/linux/kernel/git/rostedt/linux-trace.git
ftrace/tracefs

Head SHA1: eae473581cf93dad94ca833aa961c033c6a43924


Steven Rostedt (Red Hat) (7):
      tracing: Only create tracer options files if directory exists
      tracing: Create cmdline tracer options on tracing fs init
      tracefs: Add new tracefs file system
      tracing: Convert the tracing facility over to use tracefs
      tracing: Automatically mount tracefs on debugfs/tracing
      tracefs: Add directory /sys/kernel/tracing
      tracing: Have mkdir and rmdir be part of tracefs

----
 fs/Makefile                          |   1 +
 fs/tracefs/Makefile                  |   4 +
 fs/tracefs/inode.c                   | 650 +++++++++++++++++++++++++++++++++++
 include/linux/tracefs.h              |  45 +++
 include/uapi/linux/magic.h           |   2 +
 kernel/trace/ftrace.c                |  22 +-
 kernel/trace/trace.c                 | 187 +++++-----
 kernel/trace/trace.h                 |   2 +-
 kernel/trace/trace_events.c          |  32 +-
 kernel/trace/trace_functions_graph.c |   7 +-
 kernel/trace/trace_kprobe.c          |  10 +-
 kernel/trace/trace_probe.h           |   2 +-
 kernel/trace/trace_stat.c            |  10 +-
 13 files changed, 832 insertions(+), 142 deletions(-)
--
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/