From: Milian Wolff <milian.wolff@kdab.com>
To: Nan Xiao <xiaonan830818@gmail.com>
Cc: linux-perf-users@vger.kernel.org
Subject: Re: Why the stack frame in perf.data isn't displayed in FlameGraph?
Date: Tue, 23 May 2017 11:32:58 +0200 [thread overview]
Message-ID: <4885592.kBH1JbPkZm@milian-kdab2> (raw)
In-Reply-To: <CA+MhoaP=HR43P6PxPdVhW5_36Zo52hrNeP4_j05CwGb6__0xDg@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1046 bytes --]
On Friday, May 19, 2017 3:50:46 AM CEST Nan Xiao wrote:
> Hi Milian,
>
> Thanks very much!
>
> So what is the difference between acme's perf/core and general perf
> installed by pacman/yum? Is acme's perf/core more newer? Thx!
Yes, acme is the maintainer of the perf subsystem and his perf/core branch is
where all the latest work gets merged and tested before it lands in mainline.
Once it's in mainline it takes some time until a kernel gets released with
this version, and then a couple of months before distros start using that
kernel version (or a newer one).
So in general, if you rely on the distro packages for perf, most things are
usually outdated by at least half a year or so, often times more. For the in-
kernel recording features, that's often fine. But for the user-space analysis
tools, that is often a difference between day and night in my eyes. YMMV.
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:[~2017-05-23 9:33 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-05-18 4:09 Why the stack frame in perf.data isn't displayed in FlameGraph? Nan Xiao
2017-05-18 7:32 ` Milian Wolff
2017-05-18 13:24 ` Nan Xiao
2017-05-18 19:01 ` Milian Wolff
2017-05-19 1:50 ` Nan Xiao
2017-05-23 9:32 ` Milian Wolff [this message]
2017-05-23 10:14 ` Nan Xiao
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=4885592.kBH1JbPkZm@milian-kdab2 \
--to=milian.wolff@kdab.com \
--cc=linux-perf-users@vger.kernel.org \
--cc=xiaonan830818@gmail.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