From: <gregkh@linuxfoundation.org>
To: gregkh@linuxfoundation.org,loongarch@lists.linux.dev,yangtiezhu@loongson.cn
Cc: <stable-commits@vger.kernel.org>
Subject: Patch "perf tools: Fix build error for LoongArch" has been added to the 6.14-stable tree
Date: Tue, 20 May 2025 12:27:37 +0200 [thread overview]
Message-ID: <2025052037-icky-flattery-a618@gregkh> (raw)
In-Reply-To: <20250520063009.23504-1-yangtiezhu@loongson.cn>
This is a note to let you know that I've just added the patch titled
perf tools: Fix build error for LoongArch
to the 6.14-stable tree which can be found at:
http://www.kernel.org/git/?p=linux/kernel/git/stable/stable-queue.git;a=summary
The filename of the patch is:
perf-tools-fix-build-error-for-loongarch.patch
and it can be found in the queue-6.14 subdirectory.
If you, or anyone else, feels it should not be added to the stable tree,
please let <stable@vger.kernel.org> know about it.
From yangtiezhu@loongson.cn Tue May 20 11:10:01 2025
From: Tiezhu Yang <yangtiezhu@loongson.cn>
Date: Tue, 20 May 2025 14:30:09 +0800
Subject: perf tools: Fix build error for LoongArch
To: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Cc: stable@vger.kernel.org, linux-perf-users@vger.kernel.org, loongarch@lists.linux.dev, linux-kernel@vger.kernel.org
Message-ID: <20250520063009.23504-1-yangtiezhu@loongson.cn>
From: Tiezhu Yang <yangtiezhu@loongson.cn>
There exists the following error when building perf tools on LoongArch:
CC util/syscalltbl.o
In file included from util/syscalltbl.c:16:
tools/perf/arch/loongarch/include/syscall_table.h:2:10: fatal error: asm/syscall_table_64.h: No such file or directory
2 | #include <asm/syscall_table_64.h>
| ^~~~~~~~~~~~~~~~~~~~~~~~
compilation terminated.
This is because the generated syscall header is syscalls_64.h rather
than syscall_table_64.h. The above problem was introduced from v6.14,
then the header syscall_table.h has been removed from mainline tree
in commit af472d3c4454 ("perf syscalltbl: Remove syscall_table.h"),
just fix it only for the linux-6.14.y branch of stable tree.
By the way, no need to fix the mainline tree and there is no upstream
git id for this patch.
How to reproduce:
git clone https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git
cd linux && git checkout origin/linux-6.14.y
make JOBS=1 -C tools/perf
Fixes: fa70857a27e5 ("perf tools loongarch: Use syscall table")
Signed-off-by: Tiezhu Yang <yangtiezhu@loongson.cn>
Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
---
tools/perf/arch/loongarch/include/syscall_table.h | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
--- a/tools/perf/arch/loongarch/include/syscall_table.h
+++ b/tools/perf/arch/loongarch/include/syscall_table.h
@@ -1,2 +1,2 @@
/* SPDX-License-Identifier: GPL-2.0 */
-#include <asm/syscall_table_64.h>
+#include <asm/syscalls_64.h>
Patches currently in stable-queue which might be from yangtiezhu@loongson.cn are
queue-6.14/loongarch-uprobes-remove-user_-en-dis-able_single_step.patch
queue-6.14/loongarch-uprobes-remove-redundant-code-about-resume_era.patch
queue-6.14/perf-tools-fix-build-error-for-loongarch.patch
prev parent reply other threads:[~2025-05-20 10:27 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-05-20 6:30 [PATCH for 6.14.y] perf tools: Fix build error for LoongArch Tiezhu Yang
2025-05-20 10:27 ` gregkh [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=2025052037-icky-flattery-a618@gregkh \
--to=gregkh@linuxfoundation.org \
--cc=loongarch@lists.linux.dev \
--cc=stable-commits@vger.kernel.org \
--cc=yangtiezhu@loongson.cn \
/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