From: Leo Yan <leo.yan@arm.com>
To: Arnaldo Carvalho de Melo <acme@kernel.org>
Cc: linux-kernel@vger.kernel.org,
Andreas Larsson <andreas@gaisler.com>,
Heiko Carstens <hca@linux.ibm.com>,
Ludwig Rydberg <ludwig.rydberg@gaisler.com>,
Peter Zijlstra <peterz@infradead.org>,
Thomas Gleixner <tglx@kernel.org>,
Adrian Hunter <adrian.hunter@intel.com>,
Ian Rogers <irogers@google.com>,
James Clark <james.clark@linaro.org>,
Jiri Olsa <jolsa@kernel.org>, Namhyung Kim <namhyung@kernel.org>,
linux-perf-users@vger.kernel.org
Subject: Re: [PATCH 1/1 fyi] tools headers: Update the syscall tables and unistd.h, to support the new 'rseq_slice_yield' syscall
Date: Fri, 6 Mar 2026 10:05:45 +0000 [thread overview]
Message-ID: <20260306100545.GK1098637@e132581.arm.com> (raw)
In-Reply-To: <aanmUizWVEcq6nw5@x1>
On Thu, Mar 05, 2026 at 05:23:46PM -0300, Arnaldo Carvalho de Melo wrote:
[...]
> Warning: Kernel ABI header differences:
> diff -u tools/include/uapi/asm-generic/unistd.h include/uapi/asm-generic/unistd.h
> diff -u tools/scripts/syscall.tbl scripts/syscall.tbl
Arm64 directly uses tools/scripts/syscall.tbl, I can confirm that this
patch works for Arm64 after updating tools/scripts/syscall.tbl.
Note, tools/perf/arch/arm64/entry/syscalls/syscall_32.tbl is not
synchronized. This is fine for me, as perf generates the syscall array
using tools/perf/arch/arm/entry/syscalls/syscall.tbl instead. We can
consider to remove tools/perf/arch/arm64/entry/syscalls/syscall_32.tbl
as it is not used in perf, but this is not in this patch's scope.
For Arm and Arm64:
Reviewed-by: Leo Yan <leo.yan@arm.com>
prev parent reply other threads:[~2026-03-06 10:05 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-03-05 20:23 [PATCH 1/1 fyi] tools headers: Update the syscall tables and unistd.h, to support the new 'rseq_slice_yield' syscall Arnaldo Carvalho de Melo
2026-03-06 10:05 ` Leo Yan [this message]
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=20260306100545.GK1098637@e132581.arm.com \
--to=leo.yan@arm.com \
--cc=acme@kernel.org \
--cc=adrian.hunter@intel.com \
--cc=andreas@gaisler.com \
--cc=hca@linux.ibm.com \
--cc=irogers@google.com \
--cc=james.clark@linaro.org \
--cc=jolsa@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-perf-users@vger.kernel.org \
--cc=ludwig.rydberg@gaisler.com \
--cc=namhyung@kernel.org \
--cc=peterz@infradead.org \
--cc=tglx@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