From: James Clark <james.clark@linaro.org>
To: Peter Zijlstra <peterz@infradead.org>,
Ingo Molnar <mingo@redhat.com>,
Arnaldo Carvalho de Melo <acme@kernel.org>,
Namhyung Kim <namhyung@kernel.org>,
Mark Rutland <mark.rutland@arm.com>,
Alexander Shishkin <alexander.shishkin@linux.intel.com>,
Jiri Olsa <jolsa@kernel.org>, Ian Rogers <irogers@google.com>,
Adrian Hunter <adrian.hunter@intel.com>,
Jakub Brnak <jbrnak@redhat.com>, Leo Yan <leo.yan@arm.com>
Cc: Arnaldo Carvalho de Melo <acme@redhat.com>,
linux-perf-users@vger.kernel.org, linux-kernel@vger.kernel.org,
James Clark <james.clark@linaro.org>
Subject: [PATCH v3 0/4] perf tools: LLVM dwarf and flaky test fixes
Date: Mon, 09 Nov 2026 10:17:00 +0000 [thread overview]
Message-ID: <20261109-james-perf-test-fixes-v3-0-e8d0a65e618a@linaro.org> (raw)
Running the tests on an LLVM build results in some dwarf issues that
need fixing. And there is an easy fix for some flakiness caused when
tests are run in parallel.
Assisted by Claude Opus 5.5
Signed-off-by: James Clark <james.clark@linaro.org>
---
Changes in v3:
- Rebase to resolve new conflicts
- Link to v2: https://patch.msgid.link/20261106-james-perf-test-fixes-v2-0-9a912662f822@linaro.org
Changes in v2:
- Break perf probe line (Namhyung)
- Use a software event instead of cycles for VM compatibility (Namhyung)
- Link to v1: https://patch.msgid.link/20261105-james-perf-test-fixes-v1-0-0b279bee5830@linaro.org
---
James Clark (4):
perf libdw: Find the CU by iterating all CUs when aranges are missing
perf dwarf-aux: Support DW_OP_addrx locations for global variables
perf test probe_vfs_getname: Fix missing debuginfo detection
perf test: Don't starve per-process tests with system-wide events
tools/perf/tests/shell/lib/probe_vfs_getname.sh | 6 ++-
tools/perf/tests/shell/record.sh | 6 +--
tools/perf/tests/shell/record_lbr.sh | 2 +-
tools/perf/tests/shell/record_sideband.sh | 4 +-
tools/perf/util/annotate-data.c | 27 +---------
tools/perf/util/dwarf-aux.c | 70 ++++++++++++++++++++++---
tools/perf/util/dwarf-aux.h | 3 ++
tools/perf/util/libdw.c | 19 +++----
8 files changed, 89 insertions(+), 48 deletions(-)
---
base-commit: 13a8d580433a3b72b10be34f0e26787fe5659d3c
change-id: 20261104-james-perf-test-fixes-f72265531d1a
Best regards,
--
James Clark <james.clark@linaro.org>
next reply other threads:[~2026-11-09 10:17 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-11-09 10:17 James Clark [this message]
2026-11-09 10:17 ` [PATCH v3 1/4] perf libdw: Find the CU by iterating all CUs when aranges are missing James Clark
2026-11-09 10:17 ` [PATCH v3 2/4] perf dwarf-aux: Support DW_OP_addrx locations for global variables James Clark
2026-11-09 10:17 ` [PATCH v3 3/4] perf test probe_vfs_getname: Fix missing debuginfo detection James Clark
2026-11-09 10:17 ` [PATCH v3 4/4] perf test: Don't starve per-process tests with system-wide events James Clark
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=20261109-james-perf-test-fixes-v3-0-e8d0a65e618a@linaro.org \
--to=james.clark@linaro.org \
--cc=acme@kernel.org \
--cc=acme@redhat.com \
--cc=adrian.hunter@intel.com \
--cc=alexander.shishkin@linux.intel.com \
--cc=irogers@google.com \
--cc=jbrnak@redhat.com \
--cc=jolsa@kernel.org \
--cc=leo.yan@arm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-perf-users@vger.kernel.org \
--cc=mark.rutland@arm.com \
--cc=mingo@redhat.com \
--cc=namhyung@kernel.org \
--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®