From: Peter Zijlstra <a.p.zijlstra@chello.nl>
To: Arun Sharma <asharma@fb.com>
Cc: LKML <linux-kernel@vger.kernel.org>, Jiri Olsa <jolsa@redhat.com>,
Arnaldo Carvalho de Melo <acme@ghostprotocols.net>,
Benjamin Redelings <benjamin.redelings@nescent.org>,
Corey Ashford <cjashfor@linux.vnet.ibm.com>,
Cyrill Gorcunov <gorcunov@openvz.org>,
"Frank Ch. Eigler" <fche@redhat.com>,
Frederic Weisbecker <fweisbec@gmail.com>,
Ingo Molnar <mingo@elte.hu>,
Masami Hiramatsu <masami.hiramatsu.pt@hitachi.com>,
Paul Mackerras <paulus@samba.org>,
Robert Richter <robert.richter@amd.com>,
Stephane Eranian <eranian@google.com>,
Tom Zanussi <tzanussi@gmail.com>,
Ulrich Drepper <drepper@gmail.com>
Subject: Re: perf backtraces off-by-1
Date: Tue, 28 Aug 2012 18:34:03 +0200 [thread overview]
Message-ID: <1346171643.2296.8.camel@laptop> (raw)
In-Reply-To: <503A6273.9090702@fb.com>
On Sun, 2012-08-26 at 10:52 -0700, Arun Sharma wrote:
> On 8/26/12 9:10 AM, Peter Zijlstra wrote:
> > On Fri, 2012-08-24 at 15:13 -0700, Arun Sharma wrote:
> >
> >> One option is to support
> >> this for user mode only, with code to detect signal frames. Any other
> >> ideas?
> >>
> > I guess we'd need to see what that patch would look like... :-)
> >
>
> It used to look like this:
>
> http://git.savannah.gnu.org/gitweb/?p=libunwind.git;a=commitdiff;h=92cc7fd78a5a79c4bb5f85bfb7d7fb025df9cd5a
Hmm, that's not too bad, but a long stretch from pretty ;-)
How would you 'encode' this in the perf callchain data?
> These days we just look at dwarf augmentation string:
>
> http://git.savannah.gnu.org/gitweb/?p=libunwind.git;a=blob;f=src/dwarf/Gfde.c;h=8659624b0320c514057861a259b6efe1b605bbf3;hb=HEAD#l189
Right, except of course we don't have that in kernel..
BTW, are you in San Diego for LinuxCon/LPC etc?
next prev parent reply other threads:[~2012-08-28 16:34 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-08-24 22:13 perf backtraces off-by-1 Arun Sharma
2012-08-26 16:10 ` Peter Zijlstra
2012-08-26 17:52 ` Arun Sharma
2012-08-28 16:34 ` Peter Zijlstra [this message]
2012-08-28 17:33 ` Arun Sharma
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=1346171643.2296.8.camel@laptop \
--to=a.p.zijlstra@chello.nl \
--cc=acme@ghostprotocols.net \
--cc=asharma@fb.com \
--cc=benjamin.redelings@nescent.org \
--cc=cjashfor@linux.vnet.ibm.com \
--cc=drepper@gmail.com \
--cc=eranian@google.com \
--cc=fche@redhat.com \
--cc=fweisbec@gmail.com \
--cc=gorcunov@openvz.org \
--cc=jolsa@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=masami.hiramatsu.pt@hitachi.com \
--cc=mingo@elte.hu \
--cc=paulus@samba.org \
--cc=robert.richter@amd.com \
--cc=tzanussi@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 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.