From: Milian Wolff <milian.wolff@kdab.com>
To: "Ralph Böhme" <slow@samba.org>
Cc: linux-perf-users@vger.kernel.org
Subject: Re: Callgraphs split at the kernel boundary
Date: Mon, 04 Sep 2017 19:22:30 +0200 [thread overview]
Message-ID: <3844492.W7veBuKMvv@milian-kdab2> (raw)
In-Reply-To: <20170904170127.yuofaew6orzrxl5e@kazak>
[-- Attachment #1: Type: text/plain, Size: 1020 bytes --]
On Monday, September 4, 2017 7:01:27 PM CEST Ralph Böhme wrote:
> On Mon, Sep 04, 2017 at 06:44:23PM +0200, Milian Wolff wrote:
> > In my case, it seems to help to remove the filter. I.e. by default perf
> > nowadays uses `cycles:uppp` on my system. If I instead specify `cycles:P`
> > explicitly at `perf record` time, the issue above seems to be reduced,
> > albeit not completely. Does this help in your situation too?
>
> nope, I still mostly see split callgraphs, when recording with
>
> # perf record -e cycles:P -g -p 30027
>
> Eg (from perf script):
>
> smbd 30027 66331.499304: 250000 cpu-clock:HG:
I just realize that you are using this from within a VM which has no access to
the PMU (so it's not using cycles but cpu-clock). So I doubt the issues we two
are seeing are directly related.
Sorry for the noise
--
Milian Wolff | milian.wolff@kdab.com | Senior 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: 3826 bytes --]
prev parent reply other threads:[~2017-09-04 17:22 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-09-03 9:49 Callgraphs split at the kernel boundary Ralph Böhme
2017-09-04 16:26 ` Milian Wolff
2017-09-04 16:44 ` Milian Wolff
2017-09-04 17:01 ` Ralph Böhme
2017-09-04 17:22 ` Milian Wolff [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=3844492.W7veBuKMvv@milian-kdab2 \
--to=milian.wolff@kdab.com \
--cc=linux-perf-users@vger.kernel.org \
--cc=slow@samba.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