From: Ingo Molnar <mingo@kernel.org>
To: Peter Zijlstra <peterz@infradead.org>
Cc: "Wangnan (F)" <wangnan0@huawei.com>, Jiri Olsa <jolsa@kernel.org>,
Arnaldo Carvalho de Melo <acme@kernel.org>,
David Ahern <dsahern@gmail.com>,
Milian Wolff <milian.wolff@kdab.com>,
linux-kernel@vger.kernel.org, pi3orama <pi3orama@163.com>,
lizefan 00213767 <lizefan@huawei.com>
Subject: Re: [BUG REPORT] perf tools: x86_64: Broken calllchain when sampling taken at 'callq' instruction
Date: Tue, 1 Dec 2015 17:11:25 +0100 [thread overview]
Message-ID: <20151201161125.GA2441@gmail.com> (raw)
In-Reply-To: <20151201083845.GI3816@twins.programming.kicks-ass.net>
* Peter Zijlstra <peterz@infradead.org> wrote:
> > so I think the problem here is that the RSP does not match up to the RIP. We
> > can either pass along the original RIP+RSP, or the fixed up one - but what we
> > do currently is that we pass along only half of it - which corrupts dwarf
> > unwinding state that doesn't tolerate such errors.
>
> Still not sure what that gets you. Then you get a sample at a known wrong
> location, why would you want that?
Well, we'd at least get a valid call trace - which the 'mixed' one isn't? I.e.
this only matters with --call-graph.
But yeah, with my suggestion we'd essentially fall back from cycles:pp to
cycles:p, ideally we'd want to have real_rsp. Does the hardware provide that?
User-space cannot compute that reliably I think, what if the 'real' instruction
was manipulating RSP in more complex ways than doing a CALL?
Thanks,
Ingo
next prev parent reply other threads:[~2015-12-01 16:11 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-11-18 7:20 [BUG REPORT] perf tools: x86_64: Broken calllchain when sampling taken at 'callq' instruction Wangnan (F)
2015-11-18 8:00 ` Wangnan (F)
2015-11-18 8:20 ` Ingo Molnar
2015-11-18 8:42 ` Wangnan (F)
2015-11-18 8:49 ` Wangnan (F)
2015-11-19 6:37 ` Ingo Molnar
2015-11-19 6:45 ` Wangnan (F)
2015-11-19 10:23 ` Ingo Molnar
2015-11-19 10:43 ` Wangnan (F)
2015-11-19 11:28 ` Peter Zijlstra
2015-11-19 11:23 ` Peter Zijlstra
2015-11-27 8:38 ` Ingo Molnar
2015-11-30 9:28 ` Peter Zijlstra
2015-12-01 7:28 ` Ingo Molnar
2015-12-01 8:38 ` Peter Zijlstra
2015-12-01 16:11 ` Ingo Molnar [this message]
2015-12-01 17:21 ` Peter Zijlstra
2015-12-02 9:55 ` Ingo Molnar
2015-11-18 8:48 ` Jiri Olsa
2015-11-18 9:02 ` Wangnan (F)
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=20151201161125.GA2441@gmail.com \
--to=mingo@kernel.org \
--cc=acme@kernel.org \
--cc=dsahern@gmail.com \
--cc=jolsa@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=lizefan@huawei.com \
--cc=milian.wolff@kdab.com \
--cc=peterz@infradead.org \
--cc=pi3orama@163.com \
--cc=wangnan0@huawei.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.