public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Willy Tarreau <w@1wt.eu>
To: "Paul E. McKenney" <paulmck@kernel.org>
Cc: linux-kernel@vger.kernel.org, Sven Schnelle <svens@linux.ibm.com>,
	Willy Tarreau <w@1wt.eu>
Subject: [PATCH 4/4] rcutorture: build initrd for rcutorture with nolibc
Date: Mon,  9 Jan 2023 09:09:10 +0100	[thread overview]
Message-ID: <20230109080910.26594-5-w@1wt.eu> (raw)
In-Reply-To: <20230109080910.26594-1-w@1wt.eu>

From: Sven Schnelle <svens@linux.ibm.com>

This reduces the size of init from ~600KB to ~1KB.

Signed-off-by: Sven Schnelle <svens@linux.ibm.com>
Acked-by: Heiko Carstens <hca@linux.ibm.com>
Signed-off-by: Willy Tarreau <w@1wt.eu>
---
 tools/testing/selftests/rcutorture/bin/mkinitrd.sh | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/tools/testing/selftests/rcutorture/bin/mkinitrd.sh b/tools/testing/selftests/rcutorture/bin/mkinitrd.sh
index 70d62fd0d31d..71f0dfbb2a6d 100755
--- a/tools/testing/selftests/rcutorture/bin/mkinitrd.sh
+++ b/tools/testing/selftests/rcutorture/bin/mkinitrd.sh
@@ -64,7 +64,7 @@ ___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__\nyes\n#endif" \
+           "||__ARM_EABI__||__aarch64__||__s390x__\nyes\n#endif" \
    | ${CROSS_COMPILE}gcc -E -nostdlib -xc - \
    | grep -q '^yes'; then
 	# architecture supported by nolibc
-- 
2.17.5


  parent reply	other threads:[~2023-01-09  8:11 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-01-09  8:09 [PATCH 0/4] nolibc: add support for the s390 platform Willy Tarreau
2023-01-09  8:09 ` [PATCH 1/4] nolibc: add support for s390 Willy Tarreau
2023-01-09  8:09 ` [PATCH 2/4] selftests/nolibc: add s390 support Willy Tarreau
2023-01-09  8:09 ` [PATCH 3/4] rcutorture: add support for s390 Willy Tarreau
2023-01-09  8:09 ` Willy Tarreau [this message]
2023-01-09 19:15 ` [PATCH 0/4] nolibc: add support for the s390 platform Paul E. McKenney
2023-01-09 22:04   ` Paul E. McKenney
2023-01-10  7:32   ` Willy Tarreau
2023-01-10  9:25     ` Willy Tarreau
2023-01-10 14:53       ` Paul E. McKenney
2023-01-10 16:12         ` Willy Tarreau
2023-01-10 16:32           ` Paul E. McKenney
2023-01-10 17:53             ` Willy Tarreau
2023-01-10 21:29               ` Paul E. McKenney
2023-01-11  6:45             ` Sven Schnelle
2023-01-11  6:51               ` Willy Tarreau

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=20230109080910.26594-5-w@1wt.eu \
    --to=w@1wt.eu \
    --cc=linux-kernel@vger.kernel.org \
    --cc=paulmck@kernel.org \
    --cc=svens@linux.ibm.com \
    /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