From: "Paul E. McKenney" <paulmck@kernel.org>
To: "Thomas Weißschuh" <linux@weissschuh.net>
Cc: Willy Tarreau <w@1wt.eu>,
rcu@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] rcutorture: add nolibc init support for mips, ppc and rv64
Date: Sun, 15 Oct 2023 21:08:59 -0700 [thread overview]
Message-ID: <d41e7924-f497-4517-87c8-1961434d72dd@paulmck-laptop> (raw)
In-Reply-To: <20231016-rcu-nolibc-arch-v1-1-391af51b129b@weissschuh.net>
On Mon, Oct 16, 2023 at 12:25:14AM +0200, Thomas Weißschuh wrote:
> Use nolibc for all support architectures.
>
> Signed-off-by: Thomas Weißschuh <linux@weissschuh.net>
Queued and pushed, thank you!
Thanx, Paul
> ---
> 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
>
> ---
> base-commit: 58720809f52779dc0f08e53e54b014209d13eebb
> change-id: 20231016-rcu-nolibc-arch-edd1db03554a
>
> Best regards,
> --
> Thomas Weißschuh <linux@weissschuh.net>
>
prev parent reply other threads:[~2023-10-16 4:09 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-10-15 22:25 [PATCH] rcutorture: add nolibc init support for mips, ppc and rv64 Thomas Weißschuh
2023-10-16 4:08 ` Paul E. McKenney [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=d41e7924-f497-4517-87c8-1961434d72dd@paulmck-laptop \
--to=paulmck@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@weissschuh.net \
--cc=rcu@vger.kernel.org \
--cc=w@1wt.eu \
/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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).