linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Frederic Weisbecker <fweisbec@gmail.com>
To: Christoph Hellwig <hch@infradead.org>
Cc: Tom Zanussi <tzanussi@gmail.com>,
	linux-kernel@vger.kernel.org, mingo@elte.hu, rostedt@goodmis.org,
	lizf@cn.fujitsu.com
Subject: Re: [PATCH 2/3] perf trace: Update eval_flag() flags array to match interrupt.h
Date: Tue, 6 Oct 2009 17:25:58 +0200	[thread overview]
Message-ID: <20091006152556.GD5152@nowhere> (raw)
In-Reply-To: <20091006152255.GC5152@nowhere>

On Tue, Oct 06, 2009 at 05:22:58PM +0200, Frederic Weisbecker wrote:
> On Tue, Oct 06, 2009 at 11:21:06AM -0400, Christoph Hellwig wrote:
> > On Tue, Oct 06, 2009 at 05:19:00PM +0200, Frederic Weisbecker wrote:
> > > Yeah. We may want to do that by including trace/events/irq.h
> > > and then use the show_softirq_name() macro defined there.
> > > 
> > > The rest of the header can be wrapped through no-op macros and
> > > stub includes.
> > 
> > No, not at all.  Performance tracing tools really should not be
> > dependent on the kernel source.  This kind of creep is exactly what I
> > feared from putting the perf source in the kernel tree.
> > 
> 
> I see...
> Then the only solution I can imagine is to export a debugfs file
> in the tracing directory that provides this name resolution.
> 

I mean, not something that we would check from an offline client,
but something we could include in the traces info while recording the
traces.


  parent reply	other threads:[~2009-10-06 15:27 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-10-06  6:00 [PATCH 0/3] a few tracing bugfixes Tom Zanussi
2009-10-06  6:00 ` [PATCH 1/3] perf trace: Remove unused code in builtin-trace.c Tom Zanussi
2009-10-06 12:16   ` [tip:perf/urgent] " tip-bot for Tom Zanussi
2009-10-06  6:00 ` [PATCH 2/3] perf trace: Update eval_flag() flags array to match interrupt.h Tom Zanussi
2009-10-06 12:16   ` [tip:perf/urgent] " tip-bot for Tom Zanussi
2009-10-06 13:27   ` [PATCH 2/3] " Christoph Hellwig
2009-10-06 15:19     ` Frederic Weisbecker
2009-10-06 15:21       ` Christoph Hellwig
2009-10-06 15:22         ` Frederic Weisbecker
2009-10-06 15:24           ` Christoph Hellwig
2009-10-06 21:42             ` Frederic Weisbecker
2009-10-07  1:17               ` Steven Rostedt
2009-10-06 15:25           ` Frederic Weisbecker [this message]
2009-10-11  8:53         ` Ingo Molnar
2009-10-11 12:21           ` Christoph Hellwig
2009-10-16  8:47             ` Ingo Molnar
2009-10-06  6:00 ` [PATCH 3/3] tracing/syscalls: Use long for syscall ret format and field definitions Tom Zanussi
2009-10-06  7:15   ` Frédéric Weisbecker
2009-10-07  3:59     ` Tom Zanussi
2009-10-06 12:17   ` [tip:perf/urgent] " tip-bot for Tom Zanussi
2009-10-06  7:16 ` [PATCH 0/3] a few tracing bugfixes Frédéric 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=20091006152556.GD5152@nowhere \
    --to=fweisbec@gmail.com \
    --cc=hch@infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=lizf@cn.fujitsu.com \
    --cc=mingo@elte.hu \
    --cc=rostedt@goodmis.org \
    --cc=tzanussi@gmail.com \
    /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;
as well as URLs for NNTP newsgroup(s).