[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <1323880637.23971.34.camel@gandalf.stny.rr.com>
Date: Wed, 14 Dec 2011 11:37:17 -0500
From: Steven Rostedt <rostedt@...dmis.org>
To: Frederic Weisbecker <fweisbec@...il.com>
Cc: Seiji Aguchi <seiji.aguchi@....com>,
Vaibhav Nagarnaik <vnagarnaik@...gle.com>,
Thomas Gleixner <tglx@...utronix.de>,
Ingo Molnar <mingo@...hat.com>,
Peter Zijlstra <a.p.zijlstra@...llo.nl>,
Michael Rubin <mrubin@...gle.com>,
David Sharp <dhsharp@...gle.com>,
"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
"x86@...nel.org" <x86@...nel.org>,
Satoru Moriya <satoru.moriya@....com>
Subject: Re: [PATCH 2/2] trace,x86: Add x86 irq vector entry/exit tracepoints
On Wed, 2011-12-14 at 17:34 +0100, Frederic Weisbecker wrote:
> Well ftrace is a whole subsystem that includes the function tracer and also an interface
> for tracepoints in debugfs.
Confusing isn't it ;)
> I was rather suggesting the latter one. This is a good
> choice for background tracing. And it supports stacktraces. If those generate too much
> overhead perhaps you can tune the number of entries in the stacktrace, I don't remember
> if we can do that currently but this can be an interesting feature.
That would probably be trivial to add, especially now that we allow
pretty much a full stack trace anyway.
-- 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