From: "Mi, Dapeng" <dapeng1.mi@linux.intel.com>
To: Ravi Bangoria <ravi.bangoria@amd.com>,
Namhyung Kim <namhyung@kernel.org>
Cc: Gennady Kupava <gennady.kupava@gmail.com>,
linux-perf-users@vger.kernel.org
Subject: Re: [DISCUSSION] Three problems behind broken "perf --call-graph dwarf" on AMD: IP and stack dump mismatch, libdw fails on lld's layout, and the unwinder fallback never runs
Date: Fri, 4 Sep 2026 08:22:20 +0800 [thread overview]
Message-ID: <f0e05b97-1cce-427b-a56c-57a031cfe1ac@linux.intel.com> (raw)
In-Reply-To: <0e5e1fd0-0a46-4c1c-a391-5c245d903834@amd.com>
On 9/4/2026 12:02 AM, Ravi Bangoria wrote:
>> Suppose we need to follow below 2 rules to ensure the correct call-chain
>> unwinding and register snapshot consistency.
>>
>> 1. All registers including IP should come from either PEBS or PMI, must not
>> be mixed. This ensures to get an consistent registers snapshot.
>>
>> 2. Either SAMPLE_CALLCHAIN or SAMPLE_STACK_USER is required, the PMI
>> registers snapshot must be used. This proves the correct DWARF unwinding.
>>
>> How's your idea?
> Looks good. Mind sending the patch?
Yep, let me cook the patches. Thanks.
>
> Thanks,
> Ravi
next prev parent reply other threads:[~2026-09-04 0:22 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-08-21 21:49 [DISCUSSION] Three problems behind broken "perf --call-graph dwarf" on AMD: IP and stack dump mismatch, libdw fails on lld's layout, and the unwinder fallback never runs Gennady Kupava
2026-08-24 13:35 ` Ravi Bangoria
2026-08-25 18:05 ` Ian Rogers
2026-08-27 21:55 ` Namhyung Kim
2026-08-28 16:47 ` Namhyung Kim
2026-08-28 16:58 ` Namhyung Kim
2026-08-31 5:05 ` Ravi Bangoria
2026-09-01 15:19 ` Namhyung Kim
2026-09-03 8:39 ` Mi, Dapeng
2026-09-03 11:36 ` Ravi Bangoria
2026-09-03 11:59 ` Mi, Dapeng
2026-09-03 16:02 ` Ravi Bangoria
2026-09-04 0:22 ` Mi, Dapeng [this message]
2026-09-05 10:14 ` Gennady Kupava
2026-09-07 6:23 ` Mi, Dapeng
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=f0e05b97-1cce-427b-a56c-57a031cfe1ac@linux.intel.com \
--to=dapeng1.mi@linux.intel.com \
--cc=gennady.kupava@gmail.com \
--cc=linux-perf-users@vger.kernel.org \
--cc=namhyung@kernel.org \
--cc=ravi.bangoria@amd.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.