From: Arnaldo Carvalho de Melo <acme@kernel.org>
To: Ian Rogers <irogers@google.com>
Cc: "Peter Zijlstra" <peterz@infradead.org>,
"Ingo Molnar" <mingo@redhat.com>,
"Namhyung Kim" <namhyung@kernel.org>,
"Mark Rutland" <mark.rutland@arm.com>,
"Alexander Shishkin" <alexander.shishkin@linux.intel.com>,
"Jiri Olsa" <jolsa@kernel.org>,
"Adrian Hunter" <adrian.hunter@intel.com>,
"Kan Liang" <kan.liang@linux.intel.com>,
"Athira Rajeev" <atrajeev@linux.ibm.com>,
"Kajol Jain" <kjain@linux.ibm.com>,
"Li Huafei" <lihuafei1@huawei.com>,
"Steinar H. Gunderson" <sesse@google.com>,
"James Clark" <james.clark@linaro.org>,
"Stephen Brennan" <stephen.s.brennan@oracle.com>,
"Andi Kleen" <ak@linux.intel.com>,
"Dmitry Vyukov" <dvyukov@google.com>,
"Zhongqiu Han" <quic_zhonhan@quicinc.com>,
"Yicong Yang" <yangyicong@hisilicon.com>,
"Krzysztof Łopatowski" <krzysztof.m.lopatowski@gmail.com>,
"Dr. David Alan Gilbert" <linux@treblig.org>,
"Zixian Cai" <fzczx123@gmail.com>,
"Steve Clevenger" <scclevenger@os.amperecomputing.com>,
"Thomas Falcon" <thomas.falcon@intel.com>,
"Martin Liska" <martin.liska@hey.com>,
"Martin Liška" <m.liska@foxlink.cz>, "Song Liu" <song@kernel.org>,
linux-perf-users@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v3 0/9] perf: Default use of build IDs and improvements
Date: Wed, 28 May 2025 15:48:07 -0300 [thread overview]
Message-ID: <aDdaZ0TMA5kwZ-iV@x1> (raw)
In-Reply-To: <CAP-5=fVy6J+d1aoQwv6TMuybXWAhpeaJOvMmr3-jbsz5ig66kg@mail.gmail.com>
On Tue, May 27, 2025 at 01:48:43PM -0700, Ian Rogers wrote:
> On Mon, Apr 28, 2025 at 2:34 PM Ian Rogers <irogers@google.com> wrote:
> >
> > Build ID mmap2 events have been available since Linux v5.12 and avoid
> > certain races. Enable these by default as discussed in:
> > https://lore.kernel.org/linux-perf-users/CAP-5=fXP7jN_QrGUcd55_QH5J-Y-FCaJ6=NaHVtyx0oyNh8_-Q@mail.gmail.com/
> >
> > The dso_id is used to indentify a DSO that may change by being
> > overwritten. The inode generation isn't present in /proc/pid/maps and
> > so was already only optionally filled in. With build ID mmap events
> > the other major, minor and inode varialbes aren't filled in. Change
> > the dso_id implementation to make optional values explicit, rather
> > than injecting a dso_id we want to improve it during find operations,
> > add the buildid to the dso_id for sorting and so that matching fails
> > when build IDs vary between DSOs.
> >
> > Mark the callchain for buildids and not just the sample IP, fixing
> > missing DSOs.
> >
> > Fix sample__for_each_callchain_node to populate the map even when
> > symbols aren't computed.
> >
> > Other minor bits of build_id clean up.
> >
> > v3: Ensure the struct build_id is initialized empty prior to use as
> > read paths may fail (Namhyung).
> >
> > v2: Make marking DSOs still the default even with the defaulted build
> > ID mmap. The command line option still disables this to avoid
> > regressions. Add callchain patches and jitdump fix.
>
> Ping. Thanks,
> Ian
⬢ [acme@toolbx perf-tools-next]$ git am ./v3_20250428_irogers_perf_default_use_of_build_ids_and_improvements.mbx
Applying: perf callchain: Always populate the addr_location map when adding IP
Applying: perf build-id: Reduce size of "size" variable
Applying: perf build-id: Truncate to avoid overflowing the build_id data
Applying: perf build-id: Change sprintf functions to snprintf
Applying: perf build-id: Mark DSO in sample callchains
Applying: perf build-id: Ensure struct build_id is empty before use
Applying: perf dso: Move build_id to dso_id
Applying: perf jitdump: Directly mark the jitdump DSO
Applying: perf record: Make --buildid-mmap the default
error: patch failed: tools/perf/builtin-record.c:3349
error: tools/perf/builtin-record.c: patch does not apply
Patch failed at 0009 perf record: Make --buildid-mmap the default
hint: Use 'git am --show-current-patch=diff' to see the failed patch
hint: When you have resolved this problem, run "git am --continue".
hint: If you prefer to skip this patch, run "git am --skip" instead.
hint: To restore the original branch and stop patching, run "git am --abort".
hint: Disable this message with "git config set advice.mergeConflict false"
⬢ [acme@toolbx perf-tools-next]$
- Arnaldo
next prev parent reply other threads:[~2025-05-28 18:48 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-04-28 21:33 [PATCH v3 0/9] perf: Default use of build IDs and improvements Ian Rogers
2025-04-28 21:34 ` [PATCH v3 1/9] perf callchain: Always populate the addr_location map when adding IP Ian Rogers
2025-04-28 21:34 ` [PATCH v3 2/9] perf build-id: Reduce size of "size" variable Ian Rogers
2025-04-28 21:34 ` [PATCH v3 3/9] perf build-id: Truncate to avoid overflowing the build_id data Ian Rogers
2025-04-28 21:34 ` [PATCH v3 4/9] perf build-id: Change sprintf functions to snprintf Ian Rogers
2025-04-28 21:34 ` [PATCH v3 5/9] perf build-id: Mark DSO in sample callchains Ian Rogers
2025-05-28 20:41 ` Namhyung Kim
2025-05-28 20:54 ` Ian Rogers
2025-05-28 22:16 ` Namhyung Kim
2025-05-28 23:11 ` Ian Rogers
2025-05-29 20:53 ` Namhyung Kim
2025-04-28 21:34 ` [PATCH v3 6/9] perf build-id: Ensure struct build_id is empty before use Ian Rogers
2025-04-28 21:34 ` [PATCH v3 7/9] perf dso: Move build_id to dso_id Ian Rogers
2025-04-28 21:34 ` [PATCH v3 8/9] perf jitdump: Directly mark the jitdump DSO Ian Rogers
2025-04-28 21:34 ` [PATCH v3 9/9] perf record: Make --buildid-mmap the default Ian Rogers
2025-05-28 20:38 ` Namhyung Kim
2025-05-28 20:47 ` Ian Rogers
2025-05-28 23:56 ` Namhyung Kim
2025-05-27 20:48 ` [PATCH v3 0/9] perf: Default use of build IDs and improvements Ian Rogers
2025-05-28 18:48 ` Arnaldo Carvalho de Melo [this message]
2025-05-28 18:58 ` Ian Rogers
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=aDdaZ0TMA5kwZ-iV@x1 \
--to=acme@kernel.org \
--cc=adrian.hunter@intel.com \
--cc=ak@linux.intel.com \
--cc=alexander.shishkin@linux.intel.com \
--cc=atrajeev@linux.ibm.com \
--cc=dvyukov@google.com \
--cc=fzczx123@gmail.com \
--cc=irogers@google.com \
--cc=james.clark@linaro.org \
--cc=jolsa@kernel.org \
--cc=kan.liang@linux.intel.com \
--cc=kjain@linux.ibm.com \
--cc=krzysztof.m.lopatowski@gmail.com \
--cc=lihuafei1@huawei.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-perf-users@vger.kernel.org \
--cc=linux@treblig.org \
--cc=m.liska@foxlink.cz \
--cc=mark.rutland@arm.com \
--cc=martin.liska@hey.com \
--cc=mingo@redhat.com \
--cc=namhyung@kernel.org \
--cc=peterz@infradead.org \
--cc=quic_zhonhan@quicinc.com \
--cc=scclevenger@os.amperecomputing.com \
--cc=sesse@google.com \
--cc=song@kernel.org \
--cc=stephen.s.brennan@oracle.com \
--cc=thomas.falcon@intel.com \
--cc=yangyicong@hisilicon.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).