From: Andi Kleen <andi@firstfloor.org>
To: Mohammed Riyaz <riyaz.list@gmail.com>
Cc: linux-perf-users@vger.kernel.org
Subject: Re: Measuring worst case interrupt processing time
Date: Sun, 08 Dec 2013 19:49:44 -0800 [thread overview]
Message-ID: <87ob4qvg2v.fsf@tassilo.jf.intel.com> (raw)
In-Reply-To: <CAL7o8itUf0wOj-f7LEF=EfydzimOkpi1VrTZXVE0VvECNP0VPQ@mail.gmail.com> (Mohammed Riyaz's message of "Sun, 8 Dec 2013 05:18:06 -0800")
Mohammed Riyaz <riyaz.list@gmail.com> writes:
> Hi,
>
> I am working on trying to measure the worst case processing time for
> hard IRQ and soft IRQ. Well, I understand that we could use time
> stamps at entry and exit to measure this. Just wanted to know if there
> were other standard ways of measuring this. Any suggestions?
If your goal is to identify worst case latencies of interrupted code --
ftrace has special tracers for this: CONFIG_{IRQSOFF,PREEMPT,SCHED}_TRACER
-Andi
--
ak@linux.intel.com -- Speaking for myself only
next prev parent reply other threads:[~2013-12-09 3:49 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-12-08 13:18 Measuring worst case interrupt processing time Mohammed Riyaz
2013-12-09 3:49 ` Andi Kleen [this message]
2013-12-10 9:14 ` Mohammed Riyaz
2013-12-09 11:26 ` JJ Hiblot
2013-12-09 12:17 ` Mohammed Riyaz
2013-12-09 16:53 ` Jean-Jacques Hiblot
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=87ob4qvg2v.fsf@tassilo.jf.intel.com \
--to=andi@firstfloor.org \
--cc=linux-perf-users@vger.kernel.org \
--cc=riyaz.list@gmail.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.