From: Milian Wolff <milian.wolff@kdab.com>
To: perf group <linux-perf-users@vger.kernel.org>
Subject: perf trace report with time consumed
Date: Tue, 29 Mar 2016 22:39:36 +0200 [thread overview]
Message-ID: <1894563.GPSC8z33rH@agathebauer> (raw)
[-- Attachment #1: Type: text/plain, Size: 631 bytes --]
Hey all,
with "perf trace record --call-graph dwarf" I get a nice data file with
potentially everything required to find slow syscalls in user space
applications. But I'm missing a way to rewrite the data file to let "perf
report" attribute samples with the time spent as cost, instead of the raw
number of syscalls, i.e. samples.
Is this functionality there already? Or do I have to write another "perf
inject" command, similar to "perf inject --sched-stat"?
Thanks
--
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 reply other threads:[~2016-03-29 20:39 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-03-29 20:39 Milian Wolff [this message]
2016-03-30 14:53 ` perf trace report with time consumed Arnaldo Carvalho de Melo
2016-03-30 21:24 ` Milian Wolff
2016-03-30 21:58 ` Arnaldo Carvalho de Melo
2016-03-31 22:34 ` Milian Wolff
2016-04-01 13:01 ` Arnaldo Carvalho de Melo
2016-04-03 16:30 ` Jiri Olsa
2016-04-03 18:46 ` Milian Wolff
2016-04-04 6:14 ` Jiri Olsa
2016-04-04 21:17 ` Milian Wolff
2016-04-05 8:35 ` Jiri Olsa
2016-04-06 15:46 ` [PATCH] perf tools: Add dedicated unwind addr_space member into thread struct Jiri Olsa
2016-04-06 21:15 ` Milian Wolff
2016-04-08 12:58 ` Arnaldo Carvalho de Melo
2016-04-06 21:16 ` perf trace report with time consumed Milian Wolff
2016-04-08 13:01 ` Arnaldo Carvalho de Melo
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=1894563.GPSC8z33rH@agathebauer \
--to=milian.wolff@kdab.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 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).