From: Mathieu Desnoyers <compudj@krystal.dyndns.org>
To: Steven Rostedt <rostedt@goodmis.org>
Cc: Jason Baron <jbaron@redhat.com>,
mingo@elte.hu, linux-kernel@vger.kernel.org,
acme@ghostprotocols.net, fweisbec@gmail.com, fche@redhat.com,
peterz@infradead.org
Subject: Re: [Patch 2/2] tracepoints for softirq entry/exit - tracepoints
Date: Mon, 16 Mar 2009 14:37:39 -0400 [thread overview]
Message-ID: <20090316183739.GA10292@Krystal> (raw)
In-Reply-To: <alpine.DEB.2.00.0903160934010.26431@gandalf.stny.rr.com>
* Steven Rostedt (rostedt@goodmis.org) wrote:
>
> On Fri, 13 Mar 2009, Mathieu Desnoyers wrote:
>
> > * Jason Baron (jbaron@redhat.com) wrote:
> > >
> > > introduce softirq entry/exit tracepoints. These are useful for
> > > augmenting existing tracers, and to figure out softirq frequencies and
> > > timings.
> > >
> > > Signed-off-by: Jason Baron <jbaron@redhat.com>
> > >
> > > ---
> > >
> > > include/trace/irq_event_types.h | 12 ++++++++++++
> > > kernel/softirq.c | 7 ++++++-
> > > 2 files changed, 18 insertions(+), 1 deletions(-)
> > >
> > >
> > > diff --git a/include/trace/irq_event_types.h b/include/trace/irq_event_types.h
> > > index 214bb92..38b4bdd 100644
> > > --- a/include/trace/irq_event_types.h
> > > +++ b/include/trace/irq_event_types.h
> > > @@ -40,4 +40,16 @@ TRACE_EVENT(irq_handler_exit,
> > > __entry->irq, __entry->ret ? "handled" : "unhandled")
> > > );
> > >
> > > +TRACE_FORMAT(irq_softirq_entry,
> > > + TP_PROTO(struct softirq_action *h, struct softirq_action *vec),
> > > + TP_ARGS(h, vec),
> > > + TP_FMT("softirq=%d action=%s", h - vec, softirq_to_name[h-vec])
> > > + );
> > > +
> > > +TRACE_FORMAT(irq_softirq_exit,
> > > + TP_PROTO(struct softirq_action *h, struct softirq_action *vec),
> > > + TP_ARGS(h, vec),
> > > + TP_FMT("softirq=%d action=%s", h - vec, softirq_to_name[h-vec])
> >
> > The softirq tracepoints are a good idea indeed (I have similar ones in
> > the LTTng tree). My main concern is about the fact that you output the
> > softirq name in plain text to the trace buffers. I would rather prefer
> > to save only the softirq (h-vec) into the trace and dump the mapping
> > (h-vec) to name only once, so we can save precious trace bytes.
>
> The TP_FMT is only used by those tracers that want to use it. Any tracer
> can still hook directly to the trace point and do what every they want.
>
> -- Steve
>
By doing so, you are removing the ability to use the TP_FMT information
to perform high-speed system-wide tracing. I thought the goal was to
create a unified buffering, but sadly I don't see the high-speed
requirements being part of that plan.
Mathieu
--
Mathieu Desnoyers
OpenPGP key fingerprint: 8CD5 52C3 8E3C 4140 715F BA06 3F25 A8FE 3BAE 9A68
next prev parent reply other threads:[~2009-03-16 18:37 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-03-12 18:36 [Patch 2/2] tracepoints for softirq entry/exit - tracepoints Jason Baron
2009-03-12 19:02 ` Frederic Weisbecker
2009-03-12 23:49 ` Ingo Molnar
2009-03-13 4:03 ` [tip:tracing/ftrace] tracing: " Jason Baron
2009-03-14 2:57 ` [Patch 2/2] " Mathieu Desnoyers
2009-03-15 5:33 ` Ingo Molnar
2009-03-16 13:34 ` Steven Rostedt
2009-03-16 18:37 ` Mathieu Desnoyers [this message]
2009-03-16 18:45 ` Steven Rostedt
2009-03-16 18:51 ` Steven Rostedt
2009-03-16 19:28 ` Mathieu Desnoyers
2009-03-16 19:23 ` Mathieu Desnoyers
2009-03-16 19:00 ` Jason Baron
2009-03-16 19:17 ` Steven Rostedt
2009-03-16 19:21 ` Mathieu Desnoyers
2009-03-16 19:38 ` Jason Baron
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=20090316183739.GA10292@Krystal \
--to=compudj@krystal.dyndns.org \
--cc=acme@ghostprotocols.net \
--cc=fche@redhat.com \
--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