From: Namhyung Kim <namhyung@kernel.org>
To: Arnaldo Carvalho de Melo <acme@kernel.org>,
Ian Rogers <irogers@google.com>,
James Clark <james.clark@linaro.org>,
Namhyung Kim <namhyung@kernel.org>
Cc: Jiri Olsa <jolsa@kernel.org>,
Adrian Hunter <adrian.hunter@intel.com>,
Peter Zijlstra <peterz@infradead.org>,
Ingo Molnar <mingo@kernel.org>,
LKML <linux-kernel@vger.kernel.org>,
linux-perf-users@vger.kernel.org,
Eric Biggers <ebiggers@kernel.org>,
Pablo Galindo <pablogsal@gmail.com>,
Fangrui Song <maskray@sourceware.org>
Subject: Re: [PATCH v2 1/2] perf jitdump: Add sym/str-tables to build-ID generation
Date: Wed, 03 Dec 2025 09:58:34 -0800 [thread overview]
Message-ID: <176478471412.3636162.8826107482964301667.b4-ty@kernel.org> (raw)
In-Reply-To: <20251125080748.461014-1-namhyung@kernel.org>
On Tue, 25 Nov 2025 00:07:46 -0800, Namhyung Kim wrote:
> It was reported that python backtrace with JIT dump was broken after the
> change to built-in SHA-1 implementation. It seems python generates the
> same JIT code for each function. They will become separate DSOs but the
> contents are the same. Only difference is in the symbol name.
>
> But this caused a problem that every JIT'ed DSOs will have the same
> build-ID which makes perf confused. And it resulted in no python
> symbols (from JIT) in the output.
>
> [...]
Applied to perf-tools-next, thanks!
Best regards,
Namhyung
prev parent reply other threads:[~2025-12-03 17:58 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-11-25 8:07 Namhyung Kim
2025-11-25 8:07 ` [PATCH v2 2/2] perf test: Add python JIT dump test Namhyung Kim
2025-11-25 19:29 ` [PATCH v2 1/2] perf jitdump: Add sym/str-tables to build-ID generation Eric Biggers
2025-11-26 2:55 ` Ian Rogers
2025-11-26 3:04 ` Eric Biggers
2025-11-27 21:17 ` Namhyung Kim
2025-11-27 22:18 ` Eric Biggers
2025-12-02 21:56 ` Namhyung Kim
2025-12-02 23:26 ` Ian Rogers
2025-12-03 0:06 ` Namhyung Kim
2025-12-02 23:27 ` Eric Biggers
2025-12-02 23:32 ` Ian Rogers
2025-12-03 1:28 ` Fangrui Song
2025-12-03 17:58 ` Namhyung Kim [this message]
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=176478471412.3636162.8826107482964301667.b4-ty@kernel.org \
--to=namhyung@kernel.org \
--cc=acme@kernel.org \
--cc=adrian.hunter@intel.com \
--cc=ebiggers@kernel.org \
--cc=irogers@google.com \
--cc=james.clark@linaro.org \
--cc=jolsa@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-perf-users@vger.kernel.org \
--cc=maskray@sourceware.org \
--cc=mingo@kernel.org \
--cc=pablogsal@gmail.com \
--cc=peterz@infradead.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
all inboxes | Powered by JetHome®