From: Andi Kleen <andi@firstfloor.org>
To: linux-perf-users@vger.kernel.org
Subject: Introduction to Last Branch Records on perf
Date: Thu, 7 Apr 2016 07:21:57 -0700 [thread overview]
Message-ID: <20160407142157.GD9407@two.firstfloor.org> (raw)
Hi,
I wrote a two part article on theory and practice of Last Branch
Records using Linux perf. They were published on LWN.
This includes the background (what is a last branch record and why
branch sampling), what you can use it for in perf, like hot path
profiling, frame pointerless callgraphs, or automatic micro benchmarks,
and also other uses like continuous compiler feedback.
The articles are now freely available.
Introduction of Last Branch Records
http://lwn.net/Articles/680985/
Advanced uses of Last Branch Reocrds
http://lwn.net/Articles/680996
-Andi
--
ak@linux.intel.com -- Speaking for myself only.
reply other threads:[~2016-04-07 14:22 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20160407142157.GD9407@two.firstfloor.org \
--to=andi@firstfloor.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).