From: Andi Kleen <andi@firstfloor.org>
To: Daniel Speyer <dspeyer@gmail.com>
Cc: linux-perf-users@vger.kernel.org
Subject: Re: What helps with stacks?
Date: Tue, 21 Apr 2015 13:06:34 -0700 [thread overview]
Message-ID: <87sibtmek5.fsf@tassilo.jf.intel.com> (raw)
In-Reply-To: <loom.20150421T215002-474@post.gmane.org> (Daniel Speyer's message of "Tue, 21 Apr 2015 19:54:28 +0000 (UTC)")
Daniel Speyer <dspeyer@gmail.com> writes:
> Hello all,
>
> I'm trying to get stack traces for a bunch of events using perf record and
> having trouble with them getting cut off. I'm using --callgraph dwarf,
> which helps a little, and I recompiled libc with --fno-omit-frame-pointer,
> which doesn't seem to have helped at all. Very often, the bottom of the
> stack is in libc, often __epoll_wait_nocancel. Stacks for
> sched:sched_switch events seem to be worse than cycles or sched:sched_wakeup
> events, but it isn't 100%. Is there anything else I could try?
If you have a Haswell/Broadwell system and uptodate perf (4.0) you can also
use --call-graph lbr
This uses a new hardware mechanism that can handle many situations
where the old ones failed (but also has some situations where
it has to give up)
-andi
--
ak@linux.intel.com -- Speaking for myself only
next prev parent reply other threads:[~2015-04-21 20:06 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-04-21 19:54 What helps with stacks? Daniel Speyer
2015-04-21 20:06 ` Andi Kleen [this message]
2015-04-25 18:42 ` Daniel Speyer
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=87sibtmek5.fsf@tassilo.jf.intel.com \
--to=andi@firstfloor.org \
--cc=dspeyer@gmail.com \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.