public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Namhyung Kim <namhyung@kernel.org>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: Arnaldo Carvalho de Melo <acme@kernel.org>,
	Ian Rogers <irogers@google.com>,
	Kan Liang <kan.liang@linux.intel.com>,
	Peter Zijlstra <peterz@infradead.org>,
	Ingo Molnar <mingo@kernel.org>,
	LKML <linux-kernel@vger.kernel.org>,
	linux-perf-users@vger.kernel.org
Subject: Re: [GIT PULL] perf-tools changes for v6.13
Date: Tue, 26 Nov 2024 16:00:12 -0800	[thread overview]
Message-ID: <Z0ZhDHXxHKoE2Nrl@google.com> (raw)
In-Reply-To: <CAHk-=whQ_yeRDh_zZjhz-4q8G=vu5Ypb-Y3f=efHQSwd5Kas3w@mail.gmail.com>

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@kernel.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


  reply	other threads:[~2024-11-27  0:00 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-11-25  7:16 [GIT PULL] perf-tools changes for v6.13 Namhyung Kim
2024-11-25 19:07 ` Sasha Levin
2024-11-26  2:53   ` Namhyung Kim
2024-11-26  7:36     ` Ian Rogers
2024-12-03 18:33       ` Namhyung Kim
2024-11-26 23:33 ` Linus Torvalds
2024-11-27  0:00   ` Namhyung Kim [this message]
2024-11-27  0:59     ` Arnaldo Carvalho de Melo
2024-11-27  3:25       ` Namhyung Kim
2024-11-27 13:12         ` Arnaldo Carvalho de Melo
2024-11-27 16:02         ` Linus Torvalds
2024-11-27 18:27           ` Namhyung Kim
2024-11-28  5:53             ` Ian Rogers
2024-11-26 23:40 ` pr-tracker-bot

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=Z0ZhDHXxHKoE2Nrl@google.com \
    --to=namhyung@kernel.org \
    --cc=acme@kernel.org \
    --cc=irogers@google.com \
    --cc=kan.liang@linux.intel.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-perf-users@vger.kernel.org \
    --cc=mingo@kernel.org \
    --cc=peterz@infradead.org \
    --cc=torvalds@linux-foundation.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