[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20141214152915.431f7aa8@gandalf.local.home>
Date: Sun, 14 Dec 2014 15:29:15 -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: Re: [PATCH 0/2 v2] tracing: Enable tracepoints early and allow
printk to use them
On Sun, 14 Dec 2014 15:16:09 -0500
Steven Rostedt <rostedt@...dmis.org> wrote:
> 1) Allow traceopoints to be enabled right after mm_init(). By passing
> in the trace_event= kernel command line parameter, tracepoints can be
> enabled at boot up. For debugging things like the initialization of
> interrupts, it is needed to have tracepoints enabled very early. People
> have asked about this before and this has been on my todo list. As it
> can be helpful for Thomas to debug his upcoming 3.20 IRQ work, I'm
> pushing this now. This way he can add tracepoints into the IRQ set up
> and have have users enable them when things go wrong.
Cut and paste is a bitch!
s/mm_init/rcu_init/
-- Steve
--
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