From: Christoph Hellwig <hch@lst.de>
To: Ingo Molnar <mingo@elte.hu>
Cc: Christoph Hellwig <hch@lst.de>,
Benjamin Herrenschmidt <benh@kernel.crashing.org>,
Paul Mackerras <paulus@samba.org>,
cbe-oss-dev@ozlabs.org, srostedt@redhat.com,
linux-kernel@vger.kernel.org,
Fr?d?ric Weisbecker <fweisbec@gmail.com>
Subject: Re: [PATCH, RFC] sputrace: use the generic event tracer
Date: Wed, 6 May 2009 13:02:58 +0200 [thread overview]
Message-ID: <20090506110258.GA24850@lst.de> (raw)
In-Reply-To: <20090506105748.GE25203@elte.hu>
On Wed, May 06, 2009 at 12:57:48PM +0200, Ingo Molnar wrote:
> Nice! Needs also an Ack from PowerPC folks before we can do this.
> The cross section to other powerpc code seems to be rather low.
cbe-oss-dev is the Cell list.
> > -config SPU_TRACE
> > - tristate "SPU event tracing support"
> > - depends on SPU_FS && MARKERS
> > - help
> > - This option allows reading a trace of spu-related events through
> > - the sputrace file in procfs.
>
> I think we should keep this option around.
Why? trace_events that aren't enabled are extremly low overhead.
And most in the current tree are non-optional.
> > +# magic for the trace events
> > +CFLAGS_sched.o := -I$(src)
>
> Steve, i'm wondering whether this type of Makefile hackery (caused
> by modular tracepoints) could be eliminated ...
We would just have to include the header file with "" instead of <>.
But I remember Steve not liking this when we talked about it.
next prev parent reply other threads:[~2009-05-06 11:03 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20090506102918.GA23278@lst.de>
2009-05-06 10:57 ` [PATCH, RFC] sputrace: use the generic event tracer Ingo Molnar
2009-05-06 11:02 ` Christoph Hellwig [this message]
2009-05-06 11:23 ` Ingo Molnar
2009-05-06 13:54 ` Steven Rostedt
2009-05-06 14:47 ` Ingo Molnar
2009-05-06 14:59 ` Steven Rostedt
2009-05-06 16:53 ` Frederic Weisbecker
2009-05-06 17:13 ` Christoph Hellwig
2009-05-06 19:05 ` Steven Rostedt
2009-05-10 19:07 ` [Cbe-oss-dev] " Christoph Hellwig
2009-05-06 10:58 ` Ingo Molnar
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=20090506110258.GA24850@lst.de \
--to=hch@lst.de \
--cc=benh@kernel.crashing.org \
--cc=cbe-oss-dev@ozlabs.org \
--cc=fweisbec@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=paulus@samba.org \
--cc=srostedt@redhat.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.