From: Ingo Molnar <mingo@elte.hu>
To: Mathieu Desnoyers <mathieu.desnoyers@polymtl.ca>
Cc: Jeremy Fitzhardinge <jeremy@goop.org>,
Steven Rostedt <rostedt@goodmis.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Jeremy Fitzhardinge <jeremy.fitzhardinge@citrix.com>
Subject: Re: [PATCH 1/4] tracing: move __DO_TRACE out of line
Date: Fri, 17 Apr 2009 18:23:26 +0200 [thread overview]
Message-ID: <20090417162326.GG8253@elte.hu> (raw)
In-Reply-To: <20090417161005.GA16361@Krystal>
* Mathieu Desnoyers <mathieu.desnoyers@polymtl.ca> wrote:
> > > +#define DEFINE_DO_TRACE(name, proto, args) \
> > > + void __do_trace_##name(struct tracepoint *tp, TP_PROTO(proto)) \
> > > + { \
> >
> > that needs to be marked notrace, otherwise the function tracer
> > becomes noisy. (or even lockupy.)
>
> I guess I'll have to put it more clearly : I am all for minimizing
> tracepoint header dependency, but I'll be nacking this kind of
> out-of-lining patch. Taking a function call, and moving it
> out-of-line (thus duplicating the function call for nothing) seems
> *really* pointless and will hurt tracer performance.
No need to nak - just say you dont like it and it gets fixed :)
I meant to suggest to Jeremy to measure the effect of this
out-of-lining, in terms of instruction count in the hotpath.
> If thread_info.h is now so big that it needs a cleanup, I guess
> we'll just have to do it.
Music to my ears ...
Ingo
next prev parent reply other threads:[~2009-04-17 16:23 UTC|newest]
Thread overview: 37+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-04-17 6:35 [PATCH] tracing WIP patches Jeremy Fitzhardinge
2009-04-17 6:35 ` [PATCH 1/4] tracing: move __DO_TRACE out of line Jeremy Fitzhardinge
2009-04-17 15:46 ` Ingo Molnar
2009-04-17 16:10 ` Mathieu Desnoyers
2009-04-17 16:23 ` Ingo Molnar [this message]
2009-04-17 16:47 ` Jeremy Fitzhardinge
2009-04-17 19:31 ` Jeremy Fitzhardinge
2009-04-17 19:46 ` Ingo Molnar
2009-04-17 19:57 ` Steven Rostedt
2009-04-17 19:58 ` Jeremy Fitzhardinge
2009-04-17 20:06 ` Steven Rostedt
2009-04-18 6:53 ` Mathieu Desnoyers
2009-04-18 14:16 ` Steven Rostedt
2009-04-19 3:59 ` Mathieu Desnoyers
2009-04-19 23:38 ` Jeremy Fitzhardinge
2009-04-20 21:39 ` Mathieu Desnoyers
2009-04-19 23:40 ` Jeremy Fitzhardinge
2009-04-20 21:47 ` Mathieu Desnoyers
2009-04-17 6:35 ` [PATCH 2/4] x86/pvops: target CREATE_TRACE_POINTS to particular subsystems Jeremy Fitzhardinge
2009-04-17 15:55 ` Steven Rostedt
2009-04-17 16:14 ` Jeremy Fitzhardinge
2009-04-17 16:32 ` Steven Rostedt
2009-04-17 16:48 ` Jeremy Fitzhardinge
2009-04-17 16:57 ` Steven Rostedt
2009-04-17 17:14 ` Jeremy Fitzhardinge
2009-04-17 17:33 ` Steven Rostedt
2009-04-17 18:11 ` Jeremy Fitzhardinge
2009-04-17 6:35 ` [PATCH 3/4] tracing: pass proto and args to DEFINE_TRACE Jeremy Fitzhardinge
2009-04-17 6:48 ` Christoph Hellwig
2009-04-17 6:58 ` Jeremy Fitzhardinge
2009-04-17 7:05 ` Christoph Hellwig
2009-04-17 12:53 ` Ingo Molnar
2009-04-17 15:21 ` Mathieu Desnoyers
2009-04-17 6:35 ` [PATCH 4/4] tracing: avoid warnings from zero-arg tracepoints Jeremy Fitzhardinge
2009-04-17 15:53 ` Steven Rostedt
2009-04-17 15:53 ` Ingo Molnar
2009-04-17 16:10 ` [tip:tracing/core] " tip-bot for Jeremy Fitzhardinge
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=20090417162326.GG8253@elte.hu \
--to=mingo@elte.hu \
--cc=jeremy.fitzhardinge@citrix.com \
--cc=jeremy@goop.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mathieu.desnoyers@polymtl.ca \
--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 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.