From: Guru Prasad <gurupras@buffalo.edu>
To: Donitta <sabra_gr@yahoo.fr>
Cc: linux-perf-users@vger.kernel.org
Subject: Re: How to monitor sampling over time with Perf
Date: Sun, 28 Apr 2013 08:47:51 -0400 [thread overview]
Message-ID: <CAMefCkC9qkw+Gf11m4ODGq0hofL2qHLxB_KbnMfs--F9xuKB_w@mail.gmail.com> (raw)
In-Reply-To: <loom.20130428T132842-381@post.gmane.org>
I don't think this functionality is available in perf..I could be wrong..
I think you would have to add a small piece of code in perf stat to
achieve this..
Follow the execution from cmd_stat until run_perf_stat(I think..)
I will try to answer your question better once I go back to my lab..I
don't have access to the kernel sources currently..
On Sun, Apr 28, 2013 at 8:01 AM, Donitta <sabra_gr@yahoo.fr> wrote:
> Hi,
> I would like to monitor perf results over time. For example, I would like to
> have all the occurrences of an event and their timestamp of occurrence.
> How can I have those infos? I read somewhere in the documentation that perf
> script command provides timestamps for each occurrence, but when I tried this
> command I didn't understand it's output, and there is no documentation.
> Could someone plead provide me examples on how to use perf utilities to answer
> my needs?
>
> Many thnaks
>
> --
> To unsubscribe from this list: send the line "unsubscribe linux-perf-users" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
prev parent reply other threads:[~2013-04-28 12:47 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-04-28 12:01 How to monitor sampling over time with Perf Donitta
2013-04-28 12:47 ` Guru Prasad [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=CAMefCkC9qkw+Gf11m4ODGq0hofL2qHLxB_KbnMfs--F9xuKB_w@mail.gmail.com \
--to=gurupras@buffalo.edu \
--cc=linux-perf-users@vger.kernel.org \
--cc=sabra_gr@yahoo.fr \
/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).