mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: James Clark <james.clark@linaro.org>
To: Arnaldo Carvalho de Melo <acme@kernel.org>,
	Howard Chu <howardchu95@gmail.com>
Cc: Ian Rogers <irogers@google.com>,
	Adrian Hunter <adrian.hunter@intel.com>,
	Alan Maguire <alan.maguire@oracle.com>,
	Jiri Olsa <jolsa@kernel.org>,
	Kan Liang <kan.liang@linux.intel.com>,
	Namhyung Kim <namhyung@kernel.org>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	linux-perf-users@vger.kernel.org
Subject: Re: [PATCH 1/1] perf build: Require at least clang 16.0.6 to build BPF skeletons
Date: Thu, 12 Sep 2024 15:40:32 +0100	[thread overview]
Message-ID: <caad2d84-a8ff-4304-b8ab-04642ea18323@linaro.org> (raw)
In-Reply-To: <ZuGL9ROeTV2uXoSp@x1>



On 11/09/2024 13:24, Arnaldo Carvalho de Melo wrote:
> Howard reported problems using perf features that use BPF:
> 
>    perf $ clang -v
>    Debian clang version 15.0.6
>    Target: x86_64-pc-linux-gnu
>    Thread model: posix
>    InstalledDir: /bin
>    Found candidate GCC installation: /bin/../lib/gcc/x86_64-linux-gnu/12
>    Selected GCC installation: /bin/../lib/gcc/x86_64-linux-gnu/12
>    Candidate multilib: .;@m64
>    Selected multilib: .;@m64
>    perf $ ./perf trace -e write --max-events=1
>    libbpf: prog 'sys_enter_rename': BPF program load failed: Permission denied
>    libbpf: prog 'sys_enter_rename': -- BEGIN PROG LOAD LOG --
>    0: R1=ctx() R10=fp0
> 
> But it works with:
> 
>    perf $ clang -v
>    Debian clang version 16.0.6 (15~deb12u1)
>    Target: x86_64-pc-linux-gnu
>    Thread model: posix
>    InstalledDir: /bin
>    Found candidate GCC installation: /bin/../lib/gcc/x86_64-linux-gnu/12
>    Selected GCC installation: /bin/../lib/gcc/x86_64-linux-gnu/12
>    Candidate multilib: .;@m64
>    Selected multilib: .;@m64
>    perf $ ./perf trace -e write --max-events=1
>         0.000 ( 0.009 ms): gmain/1448 write(fd: 4, buf: \1\0\0\0\0\0\0\0, count: 8)                         = 8 (kworker/0:0-eve)
>    perf $
> 
> So lets make that the required version, if you happen to have a slightly
> older version where this work, please report so that we can adjust the
> minimum required version.
> 

I wasn't able to reproduce the issue with either of these versions. But 
I suppose it could be an issue with only 15.0.6.

$ clang -v
Ubuntu clang version 15.0.7
Target: x86_64-pc-linux-gnu
Thread model: posix
InstalledDir: /usr/bin
Found candidate GCC installation: /usr/bin/../lib/gcc/x86_64-linux-gnu/11
Found candidate GCC installation: /usr/bin/../lib/gcc/x86_64-linux-gnu/12
Selected GCC installation: /usr/bin/../lib/gcc/x86_64-linux-gnu/12
Candidate multilib: .;@m64
Selected multilib: .;@m64


Ubuntu clang version 14.0.0-1ubuntu1.1
Target: x86_64-pc-linux-gnu
Thread model: posix
InstalledDir: /usr/bin
Found candidate GCC installation: /usr/bin/../lib/gcc/x86_64-linux-gnu/11
Found candidate GCC installation: /usr/bin/../lib/gcc/x86_64-linux-gnu/12
Selected GCC installation: /usr/bin/../lib/gcc/x86_64-linux-gnu/12
Candidate multilib: .;@m64
Selected multilib: .;@m64

  reply	other threads:[~2024-09-12 14:40 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-09-11 12:24 Arnaldo Carvalho de Melo
2024-09-12 14:40 ` James Clark [this message]
2024-09-12 14:50   ` Arnaldo Carvalho de Melo
2024-09-12 15:00     ` James Clark
2024-09-13 10:20     ` James Clark
     [not found]       ` <CA+JHD936J-q0-7LANQ3aW2G-PEmFP8PnXQ-TF-AMs9MtrCqfew@mail.gmail.com>
2024-09-17 17:37         ` Howard Chu
2024-09-19  3:13           ` Howard Chu
2024-09-24  2:00             ` Howard Chu
2024-09-24  9:29               ` Alan Maguire
2024-09-24 18:45                 ` Howard Chu
2024-10-08  7:27                   ` Howard Chu
2024-10-10  1:01                     ` Namhyung Kim
     [not found]                       ` <CA+JHD93JgJL_4GJFcFUNu-FpNfFOoyDRJ7QuvO82M8G1EwM5pQ@mail.gmail.com>
2024-10-10  9:00                         ` James Clark
2024-10-10  9:11                           ` James Clark
2024-10-10 16:15                             ` Namhyung Kim
2024-10-11 19:06                           ` Arnaldo Carvalho de Melo

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=caad2d84-a8ff-4304-b8ab-04642ea18323@linaro.org \
    --to=james.clark@linaro.org \
    --cc=acme@kernel.org \
    --cc=adrian.hunter@intel.com \
    --cc=alan.maguire@oracle.com \
    --cc=howardchu95@gmail.com \
    --cc=irogers@google.com \
    --cc=jolsa@kernel.org \
    --cc=kan.liang@linux.intel.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-perf-users@vger.kernel.org \
    --cc=namhyung@kernel.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®