linux-perf-users.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Milian Wolff <milian.wolff@kdab.com>
To: Arnaldo Carvalho de Melo <acme@kernel.org>
Cc: perf group <linux-perf-users@vger.kernel.org>
Subject: Re: perf record of multiple events: disable callgraph for some events
Date: Fri, 09 Oct 2015 16:08:10 +0200	[thread overview]
Message-ID: <1795032.7YQzqPdcGP@agathebauer> (raw)
In-Reply-To: <20151004204059.GF20515@kernel.org>

[-- Attachment #1: Type: text/plain, Size: 1702 bytes --]

On Sonntag, 4. Oktober 2015 17:40:59 CEST Arnaldo Carvalho de Melo wrote:
> Em Sun, Oct 04, 2015 at 01:48:21PM +0200, Milian Wolff escreveu:
> > Hey all,
> > 
> > would it be possible to add a feature to perf to only grab callgraphs for
> > a
> > certain selection of events? E.g. thinking about a lock contention profile
> > of a Qt application, I'd listen to
> > 
> > -e syscalls:sys_enter_futex,syscalls:sys_exit_futex
> > 
> > Now, with the dwarf unwinder this easily produces huge data files in the
> > order of gigabytes. This cost could easily be reduced by a factor of two,
> > as one only needs the callgraphs for syscalls:sys_enter_futex - the TID
> > should be enough to find the callgraph for the enter event from the exit
> > trace point.
> > 
> > Could someone guide me in implementing such a feature to make it possible
> > to filter the events which trigger the collection of a callgraph? Or is
> > that already possible somehow?
> 
> Can you please check if this suits you, it is already in the tree:
> 
> commit e637d17757a10732fa5d573c18f20b3cd4d31245
> Author: He Kuang <hekuang@huawei.com>
> Date:   Mon Sep 28 03:52:16 2015 +0000

<snip>

Perfect, Thanks Arnaldo for pointing me in that direction, and many thanks to 
He for implementing it! Works like a charm.

Does anyone have a suggestion on where to put documentation for this? I'll try 
to add that then next week, together with the other stuff I've noticed and 
couldn't find before. Otherwise, I'll put it into the docs for `perf record`'s 
`--call-graph`.

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 --]

  reply	other threads:[~2015-10-09 14:08 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-10-04 11:48 perf record of multiple events: disable callgraph for some events Milian Wolff
2015-10-04 20:40 ` Arnaldo Carvalho de Melo
2015-10-09 14:08   ` Milian Wolff [this message]
2015-10-09 14:31     ` 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=1795032.7YQzqPdcGP@agathebauer \
    --to=milian.wolff@kdab.com \
    --cc=acme@kernel.org \
    --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).