From: Namhyung Kim <namhyung@kernel.org>
To: Ian Rogers <irogers@google.com>
Cc: James Clark <james.clark@linaro.org>,
Peter Zijlstra <peterz@infradead.org>,
Ingo Molnar <mingo@redhat.com>,
Arnaldo Carvalho de Melo <acme@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>,
Jakub Brnak <jbrnak@redhat.com>, Leo Yan <leo.yan@arm.com>,
Arnaldo Carvalho de Melo <acme@redhat.com>,
linux-perf-users@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v4 0/4] perf tools: LLVM dwarf and flaky test fixes
Date: Tue, 10 Nov 2026 13:57:37 -0800 [thread overview]
Message-ID: <avOTUWTBoXDooTY2@google.com> (raw)
In-Reply-To: <CAP-5=fWpnzp4O-kKqToP0Q7WVp1dcPaUH1MgPNiL__MNJKZ7hQ@mail.gmail.com>
On Mon, Nov 09, 2026 at 10:20:06AM -0800, Ian Rogers wrote:
> On Mon, Nov 9, 2026 at 5:48 AM James Clark <james.clark@linaro.org> wrote:
> >
> > 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>
>
> For the series:
> Tested-by: Ian Rogers <irogers@google.com>
Thanks, as Arnaldo took the patch 3 and 4 to perf-tools, I'll process
the rest in perf-tools-next.
Thanks,
Namhyung
prev parent reply other threads:[~2026-11-10 21:57 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-11-09 13:48 James Clark
2026-11-09 13:48 ` [PATCH v4 1/4] perf libdw: Find the CU by iterating all CUs when aranges are missing James Clark
2026-11-09 13:48 ` [PATCH v4 2/4] perf dwarf-aux: Support DW_OP_addrx locations for global variables James Clark
2026-11-09 13:48 ` [PATCH v4 3/4] perf test probe_vfs_getname: Fix missing debuginfo detection James Clark
2026-11-09 13:48 ` [PATCH v4 4/4] perf test: Don't starve per-process tests with system-wide events James Clark
2026-11-09 17:47 ` Ian Rogers
2026-11-10 12:30 ` James Clark
2026-11-10 16:49 ` Ian Rogers
2026-11-09 18:20 ` [PATCH v4 0/4] perf tools: LLVM dwarf and flaky test fixes Ian Rogers
2026-11-10 21:57 ` 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=avOTUWTBoXDooTY2@google.com \
--to=namhyung@kernel.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=james.clark@linaro.org \
--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=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®