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: Wed, 17 Aug 2016 12:05:53 +0900 [thread overview]
Message-ID: <20160817030553.GB8981@sejong> (raw)
In-Reply-To: <12483222.2TZrqxLJ8H@agathebauer>
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"].
Thanks,
Namhyung
>
> I have hacked something together locally in python_process_tracepoint, but
> wonder what an upstreamable version should look like:
>
> - I simply added the sample data to the dict, like is done in
> python_process_general_event
>
> - Alternatively, one could think of more `common_period(context)` functions.
> If that is preferable, I could add the sample to the scripting_context and
> make that work.
>
> Please advise the path forward, I'm willing to send a patch upstream to make
> it work.
>
> 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
next prev parent reply other threads:[~2016-08-17 3:06 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 [this message]
2016-08-17 8:48 ` Milian Wolff
2016-08-19 1:35 ` Namhyung Kim
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=20160817030553.GB8981@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.