From: Andi Kleen <andi@firstfloor.org>
To: Jan Blunck <jblunck@suse.de>
Cc: Linux-Kernel Mailinglist <linux-kernel@vger.kernel.org>,
linux-rt-users@vger.kernel.org, peterz@infradead.org,
Sven-Thorsten Dietrich <sdietrich@novell.com>,
Michael Galbraith <MGalbraith@novell.com>
Subject: Re: [RFC 1/4] ftrace: Add events for tracing timer interrupts
Date: Wed, 08 Sep 2010 15:24:01 +0200 [thread overview]
Message-ID: <87zkvsweq6.fsf@basil.nowhere.org> (raw)
In-Reply-To: <1283948964-6418-2-git-send-email-jblunck@suse.de> (Jan Blunck's message of "Wed, 8 Sep 2010 14:29:21 +0200")
Jan Blunck <jblunck@suse.de> writes:
> Trace the execution of the timer interrupt. I did not find an argument that
> makes any sense so traces look like this:
>
> <idle>-0 [000] 181019.693546: timerirq_enter: unused=1
> <idle>-0 [000] 181019.693553: timerirq_exit: unused=1
I think you can get the same by just filtering the normal
irq entry for the timer irq number.
-Andi
--
ak@linux.intel.com -- Speaking for myself only.
next prev parent reply other threads:[~2010-09-08 13:24 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-09-08 12:29 [RFC 0/4] Disable timer tick for SCHED_FIFO tasks Jan Blunck
2010-09-08 12:29 ` [RFC 1/4] ftrace: Add events for tracing timer interrupts Jan Blunck
2010-09-08 12:38 ` Peter Zijlstra
2010-09-08 13:24 ` Andi Kleen [this message]
2010-09-08 12:29 ` [RFC 2/4] ftrace: Add events for tracing tick start and stop Jan Blunck
2010-09-08 12:29 ` [RFC 3/4] Disable scheduler tick when we are running SCHED_FIFO tasks Jan Blunck
2010-09-08 12:43 ` Peter Zijlstra
2010-09-08 14:32 ` Jan Blunck
2010-09-08 12:45 ` Peter Zijlstra
2010-09-08 13:21 ` Thomas Gleixner
2010-09-08 14:28 ` Jan Blunck
2010-09-08 17:11 ` Andi Kleen
2010-09-08 13:25 ` Andi Kleen
2010-09-08 14:47 ` Jan Blunck
2010-09-08 12:29 ` [RFC 4/4] ftrace: Add argument to tick start/stop tracing Jan Blunck
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=87zkvsweq6.fsf@basil.nowhere.org \
--to=andi@firstfloor.org \
--cc=MGalbraith@novell.com \
--cc=jblunck@suse.de \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-rt-users@vger.kernel.org \
--cc=peterz@infradead.org \
--cc=sdietrich@novell.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.