mirror of https://lore.kernel.org/lkml/
 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: [GIT PULL] perf-tools fixes for v6.17-rc4
Date: Wed, 27 Aug 2025 16:48:17 -0700	[thread overview]
Message-ID: <20250827234817.4156091-1-namhyung@kernel.org> (raw)

Hi Linus,

Please consider pulling the following changes in perf tools for v6.17.

I've noticed a number of test failures when preparing this pull request.
I didn't notice it since it happens when running the tests in parallel.
So far git bisect couldn't find the correct bad commit but I don't think
it belongs to this series.  I'll keep investigating.

Thanks,
Namhyung


The following changes since commit c17b750b3ad9f45f2b6f7e6f7f4679844244f0b9:

  Linux 6.17-rc2 (2025-08-17 15:22:10 -0700)

are available in the Git repository at:

  git://git.kernel.org/pub/scm/linux/kernel/git/perf/perf-tools.git tags/perf-tools-fixes-for-v6.17-2025-08-27

for you to fetch changes up to 2c369d91d0933aaff96b6b807b22363e6a38a625:

  perf symbol: Add blocking argument to filename__read_build_id (2025-08-25 15:07:18 -0700)

----------------------------------------------------------------
perf-tools fixes for v6.17-rc4

A list of kernel header sync changes and two build-id fixes.

Signed-off-by: Namhyung Kim <namhyung@kernel.org>

----------------------------------------------------------------
Ian Rogers (2):
      perf symbol-minimal: Fix ehdr reading in filename__read_build_id
      perf symbol: Add blocking argument to filename__read_build_id

Namhyung Kim (12):
      perf test: Fix a build error in x86 topdown test
      tools headers: Sync KVM headers with the kernel source
      tools headers: Sync linux/bits.h with the kernel source
      tools headers: Sync linux/cfi_types.h with the kernel source
      tools headers: Sync x86 headers with the kernel source
      tools headers: Sync arm64 headers with the kernel source
      tools headers: Sync powerpc headers with the kernel source
      tools headers: Sync syscall tables with the kernel source
      tools headers: Sync uapi/linux/fcntl.h with the kernel source
      tools headers: Sync uapi/linux/fs.h with the kernel source
      tools headers: Sync uapi/linux/prctl.h with the kernel source
      tools headers: Sync uapi/linux/vhost.h with the kernel source

 tools/arch/arm64/include/asm/cputype.h             | 28 +++++++
 tools/arch/powerpc/include/uapi/asm/kvm.h          | 13 ----
 tools/arch/x86/include/asm/cpufeatures.h           | 10 ++-
 tools/arch/x86/include/asm/msr-index.h             |  7 ++
 tools/arch/x86/include/uapi/asm/kvm.h              |  8 +-
 tools/include/linux/bits.h                         | 29 ++-----
 tools/include/linux/cfi_types.h                    | 23 ++++++
 tools/include/uapi/asm-generic/unistd.h            |  8 +-
 tools/include/uapi/linux/kvm.h                     | 27 +++++++
 tools/perf/arch/arm/entry/syscalls/syscall.tbl     |  2 +
 .../perf/arch/mips/entry/syscalls/syscall_n64.tbl  |  2 +
 tools/perf/arch/powerpc/entry/syscalls/syscall.tbl |  2 +
 tools/perf/arch/s390/entry/syscalls/syscall.tbl    |  2 +
 tools/perf/arch/sh/entry/syscalls/syscall.tbl      |  2 +
 tools/perf/arch/sparc/entry/syscalls/syscall.tbl   |  2 +
 tools/perf/arch/x86/entry/syscalls/syscall_32.tbl  |  2 +
 tools/perf/arch/x86/entry/syscalls/syscall_64.tbl  |  2 +
 tools/perf/arch/x86/tests/topdown.c                |  1 +
 tools/perf/arch/xtensa/entry/syscalls/syscall.tbl  |  2 +
 tools/perf/bench/inject-buildid.c                  |  2 +-
 tools/perf/builtin-buildid-cache.c                 |  8 +-
 tools/perf/builtin-inject.c                        |  4 +-
 tools/perf/tests/sdt.c                             |  2 +-
 tools/perf/trace/beauty/include/uapi/linux/fcntl.h | 18 +++++
 tools/perf/trace/beauty/include/uapi/linux/fs.h    | 88 ++++++++++++++++++++++
 tools/perf/trace/beauty/include/uapi/linux/prctl.h |  9 ++-
 tools/perf/trace/beauty/include/uapi/linux/vhost.h | 35 +++++++++
 tools/perf/util/build-id.c                         |  4 +-
 tools/perf/util/debuginfo.c                        |  8 +-
 tools/perf/util/dsos.c                             |  4 +-
 tools/perf/util/symbol-elf.c                       |  9 ++-
 tools/perf/util/symbol-minimal.c                   | 59 +++++++--------
 tools/perf/util/symbol.c                           |  8 +-
 tools/perf/util/symbol.h                           |  2 +-
 tools/perf/util/synthetic-events.c                 |  2 +-
 tools/scripts/syscall.tbl                          |  2 +
 36 files changed, 342 insertions(+), 94 deletions(-)

             reply	other threads:[~2025-08-27 23:48 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-08-27 23:48 Namhyung Kim [this message]
2025-08-28  2:30 ` 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=20250827234817.4156091-1-namhyung@kernel.org \
    --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

all inboxes | Powered by JetHome®