From: Martin Ichilevici de Oliveira <martin.i.oliveira@gmail.com>
To: linux-perf-users@vger.kernel.org
Subject: Interrupt caused by software events
Date: Tue, 8 Jul 2014 11:42:42 -0300 [thread overview]
Message-ID: <20140708144242.GA300@gamayun> (raw)
[-- Attachment #1: Type: text/plain, Size: 682 bytes --]
Hello,
I'm learning the perf_events programming interface and I'm not sure if
what I'm trying to do is possible. I could only find the perf_event_open
documentation, but unfortunately that's not enough for my needs, as it
only counts the number of events that happened.
I'm looking for a way to determine which instruction caused some events:
something similar to what perf annotate does, but in an online fashion.
Ideally, I'd like to have some kind of handler that gets called whenever
a perf event occurs. Is that even possible? If not, is there any way I
could get this information in a real-time way?
I'll be using PEBS or IBS events.
Thank you,
-Martin
[-- Attachment #2: Type: application/pgp-signature, Size: 819 bytes --]
next reply other threads:[~2014-07-08 14:42 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-07-08 14:42 Martin Ichilevici de Oliveira [this message]
2014-07-09 13:54 ` Interrupt caused by software events Jiri Olsa
2014-07-09 14:05 ` Vince Weaver
2014-07-11 14:20 ` Martin Ichilevici de Oliveira
2014-07-11 15:26 ` Vince Weaver
2014-07-12 21:15 ` Jiri Olsa
2014-07-13 3:34 ` Andi Kleen
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=20140708144242.GA300@gamayun \
--to=martin.i.oliveira@gmail.com \
--cc=linux-perf-users@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 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 NNTP newsgroup(s).