From: Harald Servat <harald.servat@bsc.es>
To: linux-perf-users@vger.kernel.org
Subject: Information regarding the perf tool
Date: Tue, 22 Oct 2013 18:19:11 +0200 [thread overview]
Message-ID: <5266A57F.2000201@bsc.es> (raw)
Dear list,
I'm wondering whether it be possible to extend the "perf mem" (tool)
to emit the TSC of the sampling event?
I started looking at the code, and I'd like to understand how does
the perf tool work to extend that tool providing such functionality.
However, I'm clueless on how the perf tool works. I have a machine with
kernel 3.11.0 and its source code and within the source code in
tools/perf/builtin-mem.c I observe that the application is somehow
executed through "cmd_record ()" but I don't see the implementation of
cmd_record() around. Would anyone on the list giving me some hints on
how this is done?
Additionally, it seems that perf.data is a file that mostly contains
perf_event that represent the data gathered. It seems to be defined in
include/linux/perf_event.h, but it doesn't seem to me a simple container
for performance data. Is that the struct I'm looking for?
Thank you very much.
--
WARNING / LEGAL TEXT: This message is intended only for the use of the
individual or entity to which it is addressed and may contain
information which is privileged, confidential, proprietary, or exempt
from disclosure under applicable law. If you are not the intended
recipient or the person responsible for delivering the message to the
intended recipient, you are strictly prohibited from disclosing,
distributing, copying, or in any way using this message. If you have
received this communication in error, please notify the sender and
destroy and delete any copies you may have received.
http://www.bsc.es/disclaimer
next reply other threads:[~2013-10-22 16:26 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-10-22 16:19 Harald Servat [this message]
2013-10-23 12:47 ` Information regarding the perf tool Andi Kleen
2013-10-23 13:51 ` Harald Servat
2013-10-31 15:45 ` Harald Servat
2013-10-31 16:39 ` David Ahern
2013-10-31 17:23 ` Harald Servat
2013-10-31 18:22 ` David Ahern
2013-11-04 17:26 ` Harald Servat
2013-11-04 17:53 ` David Ahern
2013-11-04 18:02 ` Pawel Moll
2013-12-12 0:56 ` David Ahern
2013-12-12 8:47 ` Harald Servat
2014-01-09 12:11 ` Harald Servat
2013-10-31 16:48 ` Andi Kleen
2013-10-31 16:57 ` Harald Servat
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=5266A57F.2000201@bsc.es \
--to=harald.servat@bsc.es \
--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).