[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <Z0ZhDHXxHKoE2Nrl@google.com>
Date: Tue, 26 Nov 2024 16:00:12 -0800
From: Namhyung Kim <namhyung@...nel.org>
To: Linus Torvalds <torvalds@...ux-foundation.org>
Cc: Arnaldo Carvalho de Melo <acme@...nel.org>,
Ian Rogers <irogers@...gle.com>,
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
Hello,
On Tue, Nov 26, 2024 at 03:33:10PM -0800, Linus Torvalds wrote:
> On Sun, 24 Nov 2024 at 23:17, Namhyung Kim <namhyung@...nel.org> wrote:
> >
> > Please consider pulling the following changes in perf tools for v6.13.
>
> Hmm. Has the default search path for the vmlinux image changed?
I don't think so.
>
> Doing profiling with this, I get
>
> openat(AT_FDCWD, "vmlinux", O_RDONLY) = 5
>
> which is very very wrong for my kernel build - it basically picks up
> the vmlinux image from the build directory, which has absolutely
> *nothign* to do with the image that is being run at the moment.
Sure, at least it should match the build-id before use.
>
> So now I need to point "perf report" at the actual image, which I
> didn't need to do before.
Ok, I'll try to reproduce it and take a look.
Thanks,
Namhyung
Powered by blists - more mailing lists