From: "Frank Ch. Eigler" <fche@redhat.com>
To: Peter Zijlstra <peterz@infradead.org>
Cc: Jason Baron <jbaron@redhat.com>,
mingo@elte.hu, rostedt@goodmis.org, linux-kernel@vger.kernel.org,
acme@ghostprotocols.net, fweisbec@gmail.com,
compudj@krystal.dyndns.org
Subject: Re: [PATCH] new irq tracer
Date: Wed, 18 Feb 2009 17:23:16 -0500 [thread overview]
Message-ID: <20090218222316.GH24507@redhat.com> (raw)
In-Reply-To: <1234995035.4799.14.camel@laptop>
Hi -
On Wed, Feb 18, 2009 at 11:10:35PM +0100, Peter Zijlstra wrote:
> > > I really am having a difficult time seeing the use in such narrow
> > > tracers.
> >
> > Part of the problem may come from defining "tracers" as something
> > limited to ftrace engines. Once such tracepoints are in the kernel,
> > more powerful analytical tools may be attached to them.
>
> ftrace graph tracer is by far the most powerful thing I've seen [...]
Be that as it may, what you suggested required separate correlation of
data with /proc/interrupts contents.
> What is limiting are these puny little tracers that have no real value.
Which limited resource would even puny tracers exhaust?
> A much better purpose for these tracepoints would be augmenting data in
> existing tracers like the graph/function/sched tracer.
Be more specific. How would you augment those tracers with e.g.
individual irq numbers, their disposition status (HANDLED etc.).
- FChE
next prev parent reply other threads:[~2009-02-18 22:24 UTC|newest]
Thread overview: 48+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-02-18 19:53 [PATCH] new irq tracer Jason Baron
2009-02-18 20:08 ` Steven Rostedt
2009-02-18 20:26 ` Mathieu Desnoyers
2009-02-19 1:42 ` KOSAKI Motohiro
2009-02-18 20:30 ` Kyle McMartin
2009-02-18 21:15 ` Peter Zijlstra
2009-02-18 21:35 ` Jason Baron
2009-02-18 21:46 ` Peter Zijlstra
2009-02-18 22:02 ` Frank Ch. Eigler
2009-02-18 22:10 ` Peter Zijlstra
2009-02-18 22:23 ` Frank Ch. Eigler [this message]
2009-02-18 23:21 ` Peter Zijlstra
2009-02-20 19:52 ` Jason Baron
2009-02-21 3:39 ` Frederic Weisbecker
2009-02-22 3:38 ` KOSAKI Motohiro
2009-02-25 16:48 ` Masami Hiramatsu
2009-02-25 16:57 ` Jason Baron
2009-02-25 17:34 ` Mathieu Desnoyers
2009-02-25 18:05 ` Steven Rostedt
2009-02-25 22:12 ` Mathieu Desnoyers
2009-02-25 22:20 ` Frederic Weisbecker
2009-02-25 23:13 ` Mathieu Desnoyers
2009-02-26 1:41 ` Steven Rostedt
2009-02-26 12:37 ` Dominique Toupin
2009-02-27 3:14 ` KOSAKI Motohiro
2009-02-27 3:29 ` Steven Rostedt
2009-02-27 3:36 ` Steven Rostedt
2009-02-27 7:48 ` KOSAKI Motohiro
2009-02-27 8:06 ` Peter Zijlstra
2009-02-27 8:13 ` KOSAKI Motohiro
2009-02-27 13:10 ` Arnaldo Carvalho de Melo
2009-02-27 14:43 ` Steven Rostedt
2009-02-27 7:23 ` Peter Zijlstra
2009-02-25 22:21 ` Steven Rostedt
2009-02-26 15:11 ` Jason Baron
2009-02-26 15:32 ` Steven Rostedt
2009-02-26 15:35 ` Ingo Molnar
2009-02-26 15:40 ` Peter Zijlstra
2009-02-26 16:20 ` Frederic Weisbecker
2009-02-27 3:35 ` KOSAKI Motohiro
2009-02-27 3:33 ` KOSAKI Motohiro
2009-02-27 7:25 ` Peter Zijlstra
2009-02-25 16:58 ` Mathieu Desnoyers
2009-02-25 17:19 ` Masami Hiramatsu
2009-02-27 3:08 ` KOSAKI Motohiro
2009-02-18 23:34 ` Kyle McMartin
2009-02-19 2:13 ` Frederic Weisbecker
2009-02-19 1:46 ` Frederic Weisbecker
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=20090218222316.GH24507@redhat.com \
--to=fche@redhat.com \
--cc=acme@ghostprotocols.net \
--cc=compudj@krystal.dyndns.org \
--cc=fweisbec@gmail.com \
--cc=jbaron@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=peterz@infradead.org \
--cc=rostedt@goodmis.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