All of lore.kernel.org
 help / color / mirror / Atom feed
From: Namhyung Kim <namhyung@kernel.org>
To: Milian Wolff <milian.wolff@kdab.com>
Cc: linux-perf-users@vger.kernel.org
Subject: Re: Accessing sample data (like period) for trace events from python scripts
Date: Fri, 19 Aug 2016 10:35:49 +0900	[thread overview]
Message-ID: <20160819013549.GA22968@sejong> (raw)
In-Reply-To: <8086607.n4B18LBsdA@milian-kdab2>

On Wed, Aug 17, 2016 at 10:48:31AM +0200, Milian Wolff wrote:
> On Wednesday, August 17, 2016 12:05:53 PM CEST Namhyung Kim wrote:
> > Hi Milian,
> > 
> > On Tue, Aug 16, 2016 at 08:42:01PM +0200, Milian Wolff wrote:
> > > Hey all,
> > > 
> > > It doesn't seem to be possible to access the period, tid and various other
> > > sample fields from a python (and perl?) script using `perf script`. My
> > > use-
> > > case would be analyzing a perf data file created by perf inject
> > > --sched-stat.
> > 
> > I think you can access param_dict["sample"]["period"].
> 
> No, that is not possible, but would be a viable solution as well.

Sorry for late reply.  Oh, you wanted to access period of tracepoint
but I guess it's always 1, no?

Thanks,
Namhyung


> 
> ~~~~~~~~~~~~~~~~~~
> /tmp$ cat perf-script.py
> 
> import os
> import sys
> 
> sys.path.append(os.environ['PERF_EXEC_PATH'] + \
>         '/scripts/python/Perf-Trace-Util/lib/Perf/Trace')
> 
> from perf_trace_context import *
> from Core import *
> 
> def trace_unhandled(event_name, context, event_fields_dict):
>         print event_fields_dict['sample']['period']
> 
> /tmp$ perf script -s perf-script.py
> Traceback (most recent call last):
>   File "perf-script.py", line 11, in trace_unhandled
>     print event_fields_dict['sample']['period']
> KeyError: 'sample'
> Fatal Python error: problem in Python trace event handler
> Aborted (core dumped)
> ~~~~~~~~~~~~~~~~~~
> 
> Cheers
> -- 
> Milian Wolff | milian.wolff@kdab.com | Software Engineer
> KDAB (Deutschland) GmbH&Co KG, a KDAB Group company
> Tel: +49-30-521325470
> KDAB - The Qt Experts

  reply	other threads:[~2016-08-19  1:36 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-08-16 18:42 Accessing sample data (like period) for trace events from python scripts Milian Wolff
2016-08-17  3:05 ` Namhyung Kim
2016-08-17  8:48   ` Milian Wolff
2016-08-19  1:35     ` Namhyung Kim [this message]
2016-08-19  1:51       ` Namhyung Kim
2016-08-20 20:30         ` Milian Wolff
2016-08-23  2:42           ` Namhyung Kim
2016-08-23 19:48             ` Milian Wolff

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=20160819013549.GA22968@sejong \
    --to=namhyung@kernel.org \
    --cc=linux-perf-users@vger.kernel.org \
    --cc=milian.wolff@kdab.com \
    /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.