From: "Neeraj Upadhyay (AMD)" <neeraj.iitr10@gmail.com>
To: rcu@vger.kernel.org
Cc: linux-kernel@vger.kernel.org, kernel-team@meta.com,
rostedt@goodmis.org, paulmck@kernel.org, Neeraj.Upadhyay@amd.com,
"Thomas Weißschuh" <linux@weissschuh.net>,
"Neeraj Upadhyay" <neeraj.iitr10@gmail.com>
Subject: [PATCH rcu 2/4] rcutorture: add nolibc init support for mips, ppc and rv64
Date: Tue, 12 Dec 2023 23:04:12 +0530 [thread overview]
Message-ID: <20231212173414.11602-2-neeraj.iitr10@gmail.com> (raw)
In-Reply-To: <20231212173334.GA11572@neeraj.linux>
From: Thomas Weißschuh <linux@weissschuh.net>
Use nolibc for all support architectures.
Signed-off-by: Thomas Weißschuh <linux@weissschuh.net>
Signed-off-by: Paul E. McKenney <paulmck@kernel.org>
Signed-off-by: Neeraj Upadhyay (AMD) <neeraj.iitr10@gmail.com>
---
tools/testing/selftests/rcutorture/bin/mkinitrd.sh | 5 ++++-
1 file changed, 4 insertions(+), 1 deletion(-)
diff --git a/tools/testing/selftests/rcutorture/bin/mkinitrd.sh b/tools/testing/selftests/rcutorture/bin/mkinitrd.sh
index 212c52ca90b5..f3f867129560 100755
--- a/tools/testing/selftests/rcutorture/bin/mkinitrd.sh
+++ b/tools/testing/selftests/rcutorture/bin/mkinitrd.sh
@@ -67,7 +67,10 @@ ___EOF___
# build using nolibc on supported archs (smaller executable) and fall
# back to regular glibc on other ones.
if echo -e "#if __x86_64__||__i386__||__i486__||__i586__||__i686__" \
- "||__ARM_EABI__||__aarch64__||__s390x__||__loongarch__\nyes\n#endif" \
+ "||__ARM_EABI__||__aarch64__||(__mips__ && _ABIO32)" \
+ "||__powerpc__||(__riscv && __riscv_xlen == 64)" \
+ "||__s390x__||__loongarch__" \
+ "\nyes\n#endif" \
| ${CROSS_COMPILE}gcc -E -nostdlib -xc - \
| grep -q '^yes'; then
# architecture supported by nolibc
--
2.40.1
next prev parent reply other threads:[~2023-12-12 17:34 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-12-12 17:33 [PATCH rcu 0/4] RCU/lock torture updates for v6.8 Neeraj Upadhyay (AMD)
2023-12-12 17:34 ` [PATCH rcu 1/4] locktorture: Increase Hamming distance between call_rcu_chain and rcu_call_chains Neeraj Upadhyay (AMD)
2023-12-12 17:34 ` Neeraj Upadhyay (AMD) [this message]
2023-12-12 17:34 ` [PATCH rcu 3/4] rcutorture: Add mid-sized stall to TREE07 Neeraj Upadhyay (AMD)
2023-12-12 17:34 ` [PATCH rcu 4/4] rcutorture: Add fqs_holdoff check before fqs_task is created Neeraj Upadhyay (AMD)
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=20231212173414.11602-2-neeraj.iitr10@gmail.com \
--to=neeraj.iitr10@gmail.com \
--cc=Neeraj.Upadhyay@amd.com \
--cc=kernel-team@meta.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@weissschuh.net \
--cc=paulmck@kernel.org \
--cc=rcu@vger.kernel.org \
--cc=rostedt@goodmis.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®