From: Milian Wolff <milian.wolff@kdab.com>
To: Namhyung Kim <namhyung@kernel.org>
Cc: linux-perf-users@vger.kernel.org
Subject: Re: Accessing sample data (like period) for trace events from python scripts
Date: Sat, 20 Aug 2016 22:30:59 +0200 [thread overview]
Message-ID: <1994747.p0vVkFxHI8@agathebauer> (raw)
In-Reply-To: <20160819015101.GB22968@sejong>
[-- Attachment #1: Type: text/plain, Size: 2020 bytes --]
On Freitag, 19. August 2016 10:51:01 CEST Namhyung Kim wrote:
> On Fri, Aug 19, 2016 at 10:35:49AM +0900, Namhyung Kim wrote:
> > 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?
>
> OK, it seems sched_stat events have periods bigger than 1. But you
> can access it using 'runtime' or 'delay' field in the event too. I
> think sample data of tracepoint event is mostly meaningless and you
> should access to the event fields for useful information. That's why
> it doesn't provide the info for tracepoint events, I guess.
>
> What do you specifically want to know from sample data?
Using `perf inject --sched-stat`, I can get the sched_stat event period to the
sched_switch event (which has the proper backtrace). That is the data I want
to access. This is doable when I run:
perf script -F event,period
But it is not accessible from Perl or Python.
Note: the runtime/delay fields are not translated by perf inject, it simply
sets the period which is then used by the other perf tools.
I really think it should be made possible to access that data from Python/
Perl.
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
[-- Attachment #2: smime.p7s --]
[-- Type: application/pkcs7-signature, Size: 5903 bytes --]
next prev parent reply other threads:[~2016-08-20 20:31 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
2016-08-19 1:51 ` Namhyung Kim
2016-08-20 20:30 ` Milian Wolff [this message]
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=1994747.p0vVkFxHI8@agathebauer \
--to=milian.wolff@kdab.com \
--cc=linux-perf-users@vger.kernel.org \
--cc=namhyung@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