Re: perf stat issue with 7.0.0rc3

[Arnaldo Carvalho de Melo <acme@kernel.org>]

On Fri, Mar 13, 2026 at 11:27:30AM -0700, Ian Rogers wrote:
> > >No worries, presumably if I'd been monitoring:
> > >https://web.git.kernel.org/pub/scm/linux/kernel/git/perf/perf-tools.git/log/?h=tmp.perf-tools
> > >I'd have seen it was missing. Perhaps you can give a heads up to check
> > >for missing patches when assembling the PRs. I rarely look at
> > >perf-tools.git as perf-tools-next.git is where all the action is :-)
> > >Actually, I vibe coded a script that may work to automate this:
> > >```

> > Well, if those patches are ok for perf-tools, i.e. are fixes for
> > bugs introduced in the current merge window or urgent fixes for
> > longstanding bugs, they shouldn't be in perf-tools-next, they should
> > be in perf-tools to be merger in the current merge window.

> > Coordination in triaging via an Acked-by/Reviewed-by pointing out
> > it's something for the current merge window, something I do, is what
> > we should strive to do.

> > When I notice something that's needed for the current window that's
> > been processed by Namhyung for perf-tools-next, I merge it as well
> > (as will be in this case and maybe in the others that you pointed
> > out, thanks, I'll check each one).

> > No problem with that, better be in both branches than to get missed
> > :-)
 
> Thanks! In the patches tagged as "fixes," I think these 2 also need picking up:
 
> commit aa6a6a2d16c1e2e27e986936369959d70316199f ("perf parse-events:
> Fix big-endian 'overwrite' by writing") to fix s390.
> commit 06ec44c2aa2ef15fd56f9808b6cf7495e1fbd8ec ("perf kvm stat: Fix
> relative paths for including headers") for non-x86 builds.

Picked the two above in addition to the original one that Leo pointed
out to me at the start of this thread,

Thanks,

- Arnaldo
 
> The other patches are test fixes or address malloc failures that
> shouldn't really happen, so they are not a priority.