From: Steven Rostedt <rostedt@goodmis.org>
To: Frederic Weisbecker <fweisbec@gmail.com>
Cc: Seiji Aguchi <seiji.aguchi@hds.com>,
Vaibhav Nagarnaik <vnagarnaik@google.com>,
Thomas Gleixner <tglx@linutronix.de>,
Ingo Molnar <mingo@redhat.com>,
Peter Zijlstra <a.p.zijlstra@chello.nl>,
Michael Rubin <mrubin@google.com>,
David Sharp <dhsharp@google.com>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"x86@kernel.org" <x86@kernel.org>,
Satoru Moriya <satoru.moriya@hds.com>
Subject: Re: [PATCH 2/2] trace,x86: Add x86 irq vector entry/exit tracepoints
Date: Wed, 14 Dec 2011 11:37:17 -0500 [thread overview]
Message-ID: <1323880637.23971.34.camel@gandalf.stny.rr.com> (raw)
In-Reply-To: <20111214163407.GE10791@somewhere.redhat.com>
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
next prev parent reply other threads:[~2011-12-14 16:37 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-07-29 23:59 [PATCH 0/2] Add tracepoints to trace all x86 system IRQs Vaibhav Nagarnaik
2011-07-29 23:59 ` [PATCH 1/2] trace,x86: Add tracepoint to x86 timer interrupt handler Vaibhav Nagarnaik
2011-09-21 9:01 ` Thomas Gleixner
2011-09-21 18:20 ` Vaibhav Nagarnaik
2011-07-29 23:59 ` [PATCH 2/2] trace,x86: Add x86 irq vector entry/exit tracepoints Vaibhav Nagarnaik
2011-12-12 21:52 ` Seiji Aguchi
2011-12-13 19:26 ` Frederic Weisbecker
2011-12-14 8:18 ` Ingo Molnar
2011-12-14 14:47 ` Frederic Weisbecker
2011-12-14 16:19 ` Vaibhav Nagarnaik
2011-12-14 15:09 ` Seiji Aguchi
2011-12-14 16:34 ` Frederic Weisbecker
2011-12-14 16:37 ` Steven Rostedt [this message]
2011-12-14 17:46 ` Seiji Aguchi
2011-12-14 18:09 ` Steven Rostedt
2011-12-15 2:23 ` Seiji Aguchi
2012-02-03 15:40 ` Steven Rostedt
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1323880637.23971.34.camel@gandalf.stny.rr.com \
--to=rostedt@goodmis.org \
--cc=a.p.zijlstra@chello.nl \
--cc=dhsharp@google.com \
--cc=fweisbec@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=mrubin@google.com \
--cc=satoru.moriya@hds.com \
--cc=seiji.aguchi@hds.com \
--cc=tglx@linutronix.de \
--cc=vnagarnaik@google.com \
--cc=x86@kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®