From: fche@redhat.com (Frank Ch. Eigler)
To: "Kevin Jia" <jiaminghao@gmail.com>
Cc: systemtap@sourceware.org
Subject: Re: help-about ISR
Date: Wed, 29 Mar 2006 14:29:00 -0000 [thread overview]
Message-ID: <y0m1wwle33g.fsf@ton.toronto.redhat.com> (raw)
In-Reply-To: <30c154100603290434m77677166qa59f1389c3419448@mail.gmail.com>
"Kevin Jia" <jiaminghao@gmail.com> writes:
> I want to use systemtap trace ISR(interrput service routine), but I
> have no idea that how trace the interrupt? [...]
You would need to pick functions in the interrupt service chain to
focus on. You would insert a probe into those functions, and arrange
for the probe handlers to print something. Some of the lower level
functions are "blacklisted" (deemed unsafe for direct probing), so
higher level, device-driver-level ones are better.
probe module("foo").function("foo_interrupt_handler"),
module("bar").function("bar_interrupt_handler"),
kernel.function("baz_interrupt_handler")
{
print ("in " . probefunc())
}
- FChE
prev parent reply other threads:[~2006-03-29 14:29 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-03-29 12:34 Kevin Jia
2006-03-29 14:29 ` Frank Ch. Eigler [this message]
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=y0m1wwle33g.fsf@ton.toronto.redhat.com \
--to=fche@redhat.com \
--cc=jiaminghao@gmail.com \
--cc=systemtap@sourceware.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).