From: "Brian J. Murrell" <brian@interlinx.bc.ca>
To: linux-media@vger.kernel.org
Subject: Re: HVR-1600: Skipped encoder MPEG, MDL 63, 62 times - it must have dropped out of rotation
Date: Mon, 23 Apr 2012 13:07:45 -0400 [thread overview]
Message-ID: <jn4292$6te$1@dough.gmane.org> (raw)
In-Reply-To: <1335128213.2602.23.camel@palomino.walls.org>
[-- Attachment #1: Type: text/plain, Size: 1212 bytes --]
On 12-04-22 04:56 PM, Andy Walls wrote:
>
> If, in your system, IRQ service for device A under some circumstances
> has precendence over IRQ service for the CX23418 and hence holds off its
> service; and the irq handler in the driver for device A decides to
> perform some some long I/O operations with device A; then it doesn't
> matter how fast your CPU is.
Yes, quite true. I was forgetting about how nasty an irq handler can be
on other hardware.
> You may wish to use perf or ftrace, or some other tool/method of
> measuring kernel interrupt handling latency to find out what causes any
> delays from the CX23418 raising its IRQ line to cx18_irq_handler() being
> called by the kernel.
Excellent idea. I'm afraid I'm quite (read: very) green in the area of
kernel performance profiling. But I'm smart. Looking around, it seems
that with ftrace, I am looking for the irqsoff tracer, is that correct?
Unfortunately my kernel doesn't have that one:
# cat /sys/kernel/debug/tracing/available_tracers
blk function_graph mmiotrace wakeup_rt wakeup function nop
I can't seem to find any useful information on using perf to analyze ISR
latency. Any pointers?
Cheers,
b.
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 262 bytes --]
next prev parent reply other threads:[~2012-04-23 17:07 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-04-22 16:03 HVR-1600: Skipped encoder MPEG, MDL 63, 62 times - it must have dropped out of rotation Brian J. Murrell
2012-04-22 20:56 ` Andy Walls
2012-04-23 17:07 ` Brian J. Murrell [this message]
2012-04-24 0:54 ` Andy Walls
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='jn4292$6te$1@dough.gmane.org' \
--to=brian@interlinx.bc.ca \
--cc=linux-media@vger.kernel.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.