[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20090324180123.GF31117@elte.hu>
Date: Tue, 24 Mar 2009 19:01:23 +0100
From: Ingo Molnar <mingo@...e.hu>
To: Mathieu Desnoyers <mathieu.desnoyers@...ymtl.ca>
Cc: akpm@...ux-foundation.org, linux-kernel@...r.kernel.org,
ltt-dev@...ts.casi.polymtl.ca,
Frederic Weisbecker <fweisbec@...il.com>,
Jason Baron <jbaron@...hat.com>,
Peter Zijlstra <peterz@...radead.org>,
Thomas Gleixner <tglx@...utronix.de>,
Russell King <rmk+lkml@....linux.org.uk>,
Masami Hiramatsu <mhiramat@...hat.com>,
"Frank Ch. Eigler" <fche@...hat.com>,
Hideo AOKI <haoki@...hat.com>,
Takashi Nishiie <t-nishiie@...css.fujitsu.com>,
Steven Rostedt <rostedt@...dmis.org>,
Eduard - Gabriel Munteanu <eduard.munteanu@...ux360.ro>
Subject: Re: [patch 4/9] LTTng instrumentation softirq
* Mathieu Desnoyers <mathieu.desnoyers@...ymtl.ca> wrote:
> Compared to Jason's patch, this patch also instruments softirq raise event.
Mind sending this on top of Jason's patch, which is already applied
to the tracing tree?
Note, your instrumentation misses one source of softirq raise
events:
> @@ -300,6 +306,7 @@ void irq_exit(void)
> */
> inline void raise_softirq_irqoff(unsigned int nr)
> {
> + trace_irq_softirq_raise(nr);
> __raise_softirq_irqoff(nr);
__raise_softirq_irqoff() is used in the networking tree. It makes
little sense to instrument raise_softirq_irqoff() while not
instrumenting __raise_softirq_irqoff().
Ingo
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists