From: Willy Tarreau <w@1wt.eu>
To: "Thomas Weißschuh" <linux@weissschuh.net>
Cc: Shuah Khan <shuah@kernel.org>,
Paul Walmsley <paul.walmsley@sifive.com>,
Palmer Dabbelt <palmer@dabbelt.com>,
Albert Ou <aou@eecs.berkeley.edu>,
linux-kernel@vger.kernel.org, linux-kselftest@vger.kernel.org,
linux-riscv@lists.infradead.org, Zhangjin Wu <falcon@tinylab.org>
Subject: Re: [PATCH 1/6] tools/nolibc: add support for waitid()
Date: Sat, 21 Dec 2024 17:35:40 +0100 [thread overview]
Message-ID: <20241221163540.GA11984@1wt.eu> (raw)
In-Reply-To: <20241221-nolibc-rv32-v1-1-d9ef6dab7c63@weissschuh.net>
Hi Thomas!
On Sat, Dec 21, 2024 at 03:44:28PM +0100, Thomas Weißschuh wrote:
> waitid() is the modern variant of the family of wait-like syscalls.
> Some architectures have dropped support for wait(), wait4() and waitpid()
> but all of them support waitid().
> It is more flexible and easier to use than the older ones.
I'm generally fine with the series, but I'm starting to get concerned
that some simple applications that used to rely on wait() or waitpid()
will not work on this architecture. Just like we did for some early
syscalls that got replaced (e.g. open->openat etc), I think we'll have
to implement a default wrapper relying on waitid() for all these calls
in this case, and maybe as well for lseek->llseek() btw, what do you
think ?
The single fact that you've had to modify some of the nolibc-test code
(which is supposed to be the application here) indicates that we're
progressively going away from what applications need on certain archs.
Ideally an application relying on long-established calls should continue
to work unmodified.
Maybe it will be time for us to run an overall audit of arch-dependent
syscalls we currently have, to make sure that the common ones continue
to work fine there (and waitpid() definitely is as common a syscall as
open() since it's the good old and portable one).
Cheers,
Willy
next prev parent reply other threads:[~2024-12-21 16:36 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-12-21 14:44 [PATCH 0/6] selftests/nolibc: wire up riscv32 Thomas Weißschuh
2024-12-21 14:44 ` [PATCH 1/6] tools/nolibc: add support for waitid() Thomas Weißschuh
2024-12-21 16:35 ` Willy Tarreau [this message]
2024-12-22 11:39 ` Thomas Weißschuh
2024-12-23 8:13 ` Willy Tarreau
2024-12-21 14:44 ` [PATCH 2/6] selftests/nolibc: use waitid() over waitpid() Thomas Weißschuh
2024-12-21 14:44 ` [PATCH 3/6] selftests/nolibc: use a pipe to in vfprintf tests Thomas Weißschuh
2024-12-21 14:44 ` [PATCH 4/6] selftests/nolibc: skip tests for unimplemented syscalls Thomas Weißschuh
2024-12-21 14:44 ` [PATCH 5/6] selftests/nolibc: rename riscv to riscv64 Thomas Weißschuh
2025-01-17 19:13 ` Charlie Jenkins
2024-12-21 14:44 ` [PATCH 6/6] selftests/nolibc: add configurations for riscv32 Thomas Weißschuh
2025-01-17 19:10 ` Charlie Jenkins
2025-02-03 19:15 ` [PATCH 0/6] selftests/nolibc: wire up riscv32 patchwork-bot+linux-riscv
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=20241221163540.GA11984@1wt.eu \
--to=w@1wt.eu \
--cc=aou@eecs.berkeley.edu \
--cc=falcon@tinylab.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-kselftest@vger.kernel.org \
--cc=linux-riscv@lists.infradead.org \
--cc=linux@weissschuh.net \
--cc=palmer@dabbelt.com \
--cc=paul.walmsley@sifive.com \
--cc=shuah@kernel.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