From: Peter Zijlstra <a.p.zijlstra@chello.nl>
To: Ingo Molnar <mingo@elte.hu>
Cc: "Frédéric Weisbecker" <fweisbec@gmail.com>,
"Steven Rostedt" <rostedt@goodmis.org>,
"Linux Kernel" <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH 0/3] tracing/function-graph-tracer: signal interrupt triggering on output
Date: Mon, 15 Dec 2008 09:03:21 +0100 [thread overview]
Message-ID: <1229328201.14605.6.camel@twins> (raw)
In-Reply-To: <20081213074930.GA4205@elte.hu>
On Sat, 2008-12-13 at 08:49 +0100, Ingo Molnar wrote:
> * Frédéric Weisbecker <fweisbec@gmail.com> wrote:
>
> > > applied to tip/tracing/function-graph-tracer, thanks Frederic!
> > >
> > > The output looks really nice.
> > >
> > > Ingo
> > >
> >
> > Thanks :-)
> >
> > If anyone has other needs or suggestions about this tracer, don't
> > hesitate to request it.
> > I remember Peter suggested that the preempt count could be output.
>
> that reminds me ... did you know about hardirq_count()? We could use it
> to detect IRQ entries in a more generic way, instead of the section
> trick?
hardirq_count() is set from __irq_enter(), which is too late, we've
already had all the ARCH irq code before that.
next prev parent reply other threads:[~2008-12-15 8:03 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <493EF64D.50804@gmail.com>
2008-12-09 22:56 ` [PATCH 0/3] tracing/function-graph-tracer: signal interrupt triggering on output Frederic Weisbecker
2008-12-12 10:14 ` Ingo Molnar
2008-12-12 11:27 ` Frédéric Weisbecker
2008-12-13 7:49 ` Ingo Molnar
2008-12-13 14:26 ` Frédéric Weisbecker
2008-12-13 15:22 ` Frédéric Weisbecker
2008-12-16 23:09 ` Ingo Molnar
2008-12-15 8:03 ` Peter Zijlstra [this message]
2008-12-10 2:14 ` Steven Rostedt
2008-12-10 8:46 ` Frédéric Weisbecker
2008-12-10 8:50 ` Wang Liming
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=1229328201.14605.6.camel@twins \
--to=a.p.zijlstra@chello.nl \
--cc=fweisbec@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--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.