From: Willy Tarreau <w@1wt.eu>
To: "Paul E. McKenney" <paulmck@kernel.org>,
Zhangjin Wu <falcon@tinylab.org>,
thomas@t-8ch.de
Cc: linux-kernel@vger.kernel.org, linux-kselftest@vger.kernel.org
Subject: nolibc patches, still possible for 6.5 ?
Date: Sun, 4 Jun 2023 15:20:11 +0200 [thread overview]
Message-ID: <ZHyPi29q3MKiNAQZ@1wt.eu> (raw)
Hello Paul,
Thomas and Zhangjin have provided significant nolibc cleanups, and
fixes, as well as preparation work to later support riscv32.
These consist in the following main series:
- generalization of stackprotector to other archs that were not
previously supported (riscv, mips, loongarch, arm, arm64)
- general cleanups of the makefile, test report output, deduplication
of certain tests
- slightly better compliance of some tests performed on certain syscalls
(e.g. no longer pass (void*)1 to gettimeofday() since glibc hates it).
- add support for nanoseconds in stat() and statx()
- fixes for some syscalls (e.g. ppoll() has 5 arguments not 4)
- fixes around limits.h and INT_MAX / INT_FAST64_MAX
I rebased the whole series on top of your latest dev branch (d19a9ca3d5)
and it works fine for all archs.
I don't know if you're still planning on merging new stuff in this area
for 6.5 or not (since I know that it involves new series of tests on your
side as well), but given that Zhangjin will engage into deeper changes
later for riscv32 that will likely imply to update more syscalls to use
the time64 ones, I would prefer to split the cleanups from the hard stuff,
but I'll let you judge based on the current state of what's pending for
6.5.
In any case I'm putting all this here for now (not for merge yet):
git://git.kernel.org/pub/scm/linux/kernel/git/wtarreau/nolibc.git 20230604-nolibc-rv32+stkp6
I'd like Thomas and Zhangjin to perform a last check to confirm they're
OK with this final integration.
Thanks!
Willy
next reply other threads:[~2023-06-04 13:20 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-06-04 13:20 Willy Tarreau [this message]
2023-06-04 22:57 ` nolibc patches, still possible for 6.5 ? Paul E. McKenney
2023-06-05 3:26 ` Willy Tarreau
2023-06-07 21:03 ` Paul E. McKenney
2023-06-07 21:22 ` Willy Tarreau
2023-06-07 23:06 ` Paul E. McKenney
2023-06-08 4:32 ` Willy Tarreau
2023-06-08 16:37 ` Paul E. McKenney
2023-06-07 21:19 ` Willy Tarreau
2023-06-07 22:58 ` Paul E. McKenney
2023-06-08 4:36 ` Willy Tarreau
2023-06-08 16:39 ` Paul E. McKenney
2023-06-08 8:13 ` Zhangjin Wu
2023-06-08 8:21 ` Willy Tarreau
2023-06-08 16:40 ` Paul E. McKenney
2023-06-05 10:44 ` Thomas Weißschuh
2023-06-06 4:48 ` 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=ZHyPi29q3MKiNAQZ@1wt.eu \
--to=w@1wt.eu \
--cc=falcon@tinylab.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-kselftest@vger.kernel.org \
--cc=paulmck@kernel.org \
--cc=thomas@t-8ch.de \
/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