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

Em Fri, Oct 09, 2015 at 04:08:10PM +0200, Milian Wolff escreveu:
> 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:

> > > 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`.

Works for me. Glad that it worked for you. :-)

- Arnaldo

      reply	other threads:[~2015-10-09 14:31 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
2015-10-09 14:31     ` Arnaldo Carvalho de Melo [this message]

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=20151009143142.GL14409@kernel.org \
    --to=acme@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 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).