[<prev] [next>] [thread-next>] [day] [month] [year] [list]
Message-Id: <20141214164104.307127356@goodmis.org>
Date: Sun, 14 Dec 2014 11:41:04 -0500
From: Steven Rostedt <rostedt@...dmis.org>
To: linux-kernel@...r.kernel.org
Cc: Linus Torvalds <torvalds@...ux-foundation.org>,
Ingo Molnar <mingo@...nel.org>,
Andrew Morton <akpm@...ux-foundation.org>,
Thomas Gleixner <tglx@...utronix.de>,
Mathieu Desnoyers <mathieu.desnoyers@...icios.com>,
"Paul E. McKenney" <paulmck@...ux.vnet.ibm.com>
Subject: [PATCH 0/3] tracing: Enable tracepoints early and allow printk to use them
As the merge window is still open, and this code was not as complex
as I thought it might be. I'm thinking of pushing this in now.
This will allow Thomas to debug his irq work for 3.20.
This code is not that intrusive and I'm currently running it through
all my tests (which caught the call_rcu_sched issue()). But I like to
have some more eyes on this, as I don't like to push something into
mainline this quickly. I'm doing this only because the code is simple
enough and is useful for work coming in 3.20.
I also feel that I could handle the fall out of this work over the
holidays if need be.
Steven Rostedt (Red Hat) (3):
tracepoints: Do not use call_rcu_sched() before early_initcall()
tracing: Move enabling tracepoints to just after mm_init()
tracing: Add tp_printk cmdline to have tracepoints go to printk()
----
Documentation/kernel-parameters.txt | 18 ++++++++++++++++
include/linux/ftrace.h | 7 +++++++
init/main.c | 3 +++
kernel/sysctl.c | 7 +++++++
kernel/trace/trace.c | 25 +++++++++++++++++++++-
kernel/trace/trace.h | 14 +++++++++++++
kernel/trace/trace_events.c | 42 +++++++++++++++++++++++++++++++++++--
kernel/trace/trace_syscalls.c | 7 ++-----
kernel/tracepoint.c | 27 +++++++++++++++++++++++-
9 files changed, 141 insertions(+), 9 deletions(-)
--
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