All of lore.kernel.org
 help / color / mirror / Atom feed
From: Thorsten Schuett <schuett@gmail.com>
To: linux-perf-users@vger.kernel.org
Subject: Re: perf with gnuplot
Date: Thu, 24 Jan 2013 10:06:27 +0100	[thread overview]
Message-ID: <5100F993.80905@gmail.com> (raw)
In-Reply-To: <87libjjes6.fsf@sejong.aot.lge.com>

After thinking about it, I have some questions/suggestions:

I would really like to see this work with record/report as well. In my 
case,
I  have to watch programs on a remote machine and do the analysis
afterwards on my local machine. The record/report workflow seems to
be more flexible here. I guess perf.data is a more compact file than the
interval counter printing and I can experiment with different parameters on
the report command.

Is this going to work with -s as well?

Thorsten

On 01/24/2013 07:06 AM, Namhyung Kim wrote:
> Hi Thorsten,
>
> On Wed, 23 Jan 2013 13:38:00 +0100, Thorsten Schuett wrote:
>> Hi,
>>
>> I record three different events for my test-program:
>> perf record -s -e cycles,instructions,LLC-load-misses ./test-program
>>
>> I want to plot the occurences of the different events over time,
>> i.e. x-axis is time and y-axis is event count.
>>
>> With
>> perf report -D
>> I can dump perf.data to ASCII. However, I could not figure out how to
>> extract different event types from the ASCII output.
>>
>> 0x1edb88 [0x30]: event: 9
>> .
>> . ... raw event: size 48 bytes
>> .  0000:  09 00 00 00 02 00 30 00 43 b6 2f e7 52 2b 00 00 ......0.C./.R+..
>> .  0010:  2b 20 01 00 2f 20 01 00 2e 21 8e 48 b4 a9 26 00  + ../ ...!.H..&.
>> .  0020:  f6 6d 00 00 00 00 00 00 6b 60 63 00 00 00 00 00 .m......k`c.....
>> .
>> 10882640891486510 0x1edb88 [0x30]: PERF_RECORD_SAMPLE(IP, 2):
>> 73771/73775: 0x2b52e72fb643 period: 6512747 addr: 0
>>
>> I figured out how to parse the timestamp, pid and pid and I guess
>> period says how often an event happened in the period. However I do
>> not know which event occured. Is this only encoded in the raw event or
>> am I missing something?
>>
>> Thorsten
> There's a patch proposed for this.  I guess it'll likely get merged soon
> so that you can use it in v3.9?
>
>    http://thread.gmane.org/gmane.linux.kernel/1427078/
>
> Thanks,
> Namhyung
>

      parent reply	other threads:[~2013-01-24  9:06 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-01-23 12:38 perf with gnuplot Thorsten Schuett
2013-01-24  6:06 ` Namhyung Kim
2013-01-24  8:07   ` Thorsten Schuett
2013-01-24  9:06   ` Thorsten Schuett [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=5100F993.80905@gmail.com \
    --to=schuett@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 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.