[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <CAP-5=fV4A-FKxv7Ovq5d44C-ght3_y3YuaevR12ptL1YyAWLSw@mail.gmail.com>
Date: Wed, 27 Nov 2024 21:53:10 -0800
From: Ian Rogers <irogers@...gle.com>
To: Namhyung Kim <namhyung@...nel.org>
Cc: Linus Torvalds <torvalds@...ux-foundation.org>,
Arnaldo Carvalho de Melo <acme@...nel.org>, Kan Liang <kan.liang@...ux.intel.com>,
Peter Zijlstra <peterz@...radead.org>, Ingo Molnar <mingo@...nel.org>,
LKML <linux-kernel@...r.kernel.org>, linux-perf-users@...r.kernel.org
Subject: Re: [GIT PULL] perf-tools changes for v6.13
On Wed, Nov 27, 2024 at 10:27 AM Namhyung Kim <namhyung@...nel.org> wrote:
>
> On Wed, Nov 27, 2024 at 08:02:42AM -0800, Linus Torvalds wrote:
> > On Tue, 26 Nov 2024 at 19:25, Namhyung Kim <namhyung@...nel.org> wrote:
> > >
> > > I think it's a bug in perf record since v6.12. I found the build-id
> > > event in the header area is broken. Can you verify if this works?
> >
> > Ahh. And the reason I thought it was new to this release was simply
> > because I was traveling during the 6.12 merge window and didn't do the
> > tools build that I usually do, so I hadn't realized it was actually
> > pre-existing.
> >
> > Your patch indeed seems to fix it for me. Not hugely urgent (I just
> > installed the fixed perf binaries and clearly nobody else has even hit
> > the issue), so I'll leave this alone until the next perf tools fixes
> > pull and we'll get it fixed then.
>
> Good to hear it worked. I'll add it to the perf-tools tree.
Apologies, for the breakage. Have my:
Reviewed-by: Ian Rogers <irogers@...gle.com>
and it'd be useful for a Fixes tag for a 6.12 backport.
Thanks,
Ian
Powered by blists - more mailing lists