All of lore.kernel.org
 help / color / mirror / Atom feed
From: Arnaldo Carvalho de Melo <acme@kernel.org>
To: Michel Lind <michel@michel-slm.name>
Cc: linux-perf-users@vger.kernel.org, James Clark <james.clark@linaro.org>
Subject: Re: perf-tools v6.15 tarball not uploaded?
Date: Fri, 6 Jun 2025 17:14:54 -0300	[thread overview]
Message-ID: <aENMPp9SZdABPkic@x1> (raw)
In-Reply-To: <a4ac0d06699b0d69262953ce49c740d66590e05b.camel@michel-slm.name>

On Fri, Jun 06, 2025 at 02:59:27PM -0500, Michel Lind wrote:
> On Thu, 2025-06-05 at 16:40 -0300, Arnaldo Carvalho de Melo wrote:
> > On Thu, Jun 05, 2025 at 11:24:50AM -0500, Michel Lind wrote:
> > > I noticed the kernel.org mirrors don't have perf tarballs newer
> > > than
> > > 6.14.0 -
> > > https://mirrors.edge.kernel.org/pub/linux/kernel/tools/perf/

> > > Will they be uploaded soon? Presumably I can just generate the
> > > tarball
> > > myself for now from the Git tag.

> > Its there now:

> > https://www.kernel.org/pub/linux/kernel/tools/perf/v6.15.0/perf-6.15.0.tar.xz

> Thanks! This works great on x86_64, on arm64 it's failing because some
> files that are needed to generate unistd_64.h per James' commits
> starting Apr 29 are not there.
 
> (I tried copying the files that show up in the error log, but
> eventually hit a wall - for the Hyperscale build I'm going to get
> around it for now by just generating the file on CentOS Stream 9 and
> Stream 10 VMs, but I'll try soldiering on a bit to get this fixed
> properly next week)

Yeah, reproduced:

  CC      /tmp/build/perf-6.15.0/libapi/fd/array.o
  MKDIR   /tmp/build/perf-6.15.0/libapi/fs/
  CC      /tmp/build/perf-6.15.0/libapi/fs/fs.o
make[4]: /tmp/perf-6.15.0/scripts/Makefile.asm-headers: No such file or directory
make[4]: *** No rule to make target '/tmp/perf-6.15.0/scripts/Makefile.asm-headers'.  Stop.
make[3]: *** [Makefile:108: uapi-asm-generic] Error 2
make[2]: *** [Makefile.perf:973: /tmp/build/perf-6.15.0/libperf/libperf.a] Error 2
make[2]: *** Waiting for unfinished jobs....
  INSTALL /tmp/build/perf-6.15.0/libapi/include/api/cpu.h


We shouldn't be ever using anything outside tools, but over time we
ended up doing that :-(

And its just arm64 that is getting things from outside tools/

⬢ [acme@toolbx perf-tools]$ head tools/perf/MANIFEST 
COPYING
LICENSES/preferred/GPL-2.0
arch/arm64/tools/gen-sysreg.awk
arch/arm64/tools/syscall_64.tbl
arch/arm64/tools/sysreg
arch/*/include/uapi/asm/bpf_perf_event.h
include/uapi/asm-generic/Kbuild
tools/perf
tools/arch
tools/scripts
⬢ [acme@toolbx perf-tools]$

James, has this appeared on your radar before?

- Arnaldo
 
> These are the files I had to add so far for those curious
> 
> # needed to build uapi-asm-generic on arm64, see
> tools/lib/perf/Makefile
> Source1:       
> https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/plain/scripts/Makefile.asm-headers?h=v%{tag_version}#/Makefile.asm-headers
> Source2:       
> https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/plain/scripts/Kbuild.include?h=v%{tag_version}#/Kbuild.include
> Source3:       
> https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/plain/include/uapi/asm-generic/Kbuild?h=v%{tag_version}#/uapi-asm-generic-Kbuild
> 
> ...
> 
> %ifarch aarch64
> cp -p %{SOURCE1} scripts/
> cp -p %{SOURCE2} scripts/
> mkdir -p include/uapi/asm-generic/
> cp -p %{SOURCE3} include/uapi/asm-generic/Kbuild
> %endif
> 
> Best regards,
> 
> -- 
>  _o) Michel Lind
> _( ) identities:
> https://keyoxide.org/5dce2e7e9c3b1cffd335c1d78b229d2f7ccc04f2
>      README:     https://fedoraproject.org/wiki/User:Salimma#README



  parent reply	other threads:[~2025-06-06 20:14 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-06-05 16:24 perf-tools v6.15 tarball not uploaded? Michel Lind
2025-06-05 19:40 ` Arnaldo Carvalho de Melo
2025-06-06 19:59   ` Michel Lind
2025-06-06 20:07     ` Arnaldo Carvalho de Melo
2025-06-06 20:14     ` Arnaldo Carvalho de Melo [this message]
2025-06-12  8:59       ` Michel Lind
2025-10-21 16:00       ` Michel Lind

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=aENMPp9SZdABPkic@x1 \
    --to=acme@kernel.org \
    --cc=james.clark@linaro.org \
    --cc=linux-perf-users@vger.kernel.org \
    --cc=michel@michel-slm.name \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.