From: Rich Felker <dalias@libc.org>
To: musl@lists.openwall.com
Subject: Re: time_t assessment of what needs to be done
Date: Thu, 4 Jul 2019 15:07:57 -0400 [thread overview]
Message-ID: <20190704190757.GD1506@brightrain.aerifal.cx> (raw)
In-Reply-To: <20190701201107.GA6060@brightrain.aerifal.cx>
On Mon, Jul 01, 2019 at 04:11:07PM -0400, Rich Felker wrote:
> Then there are some functions that can get by without using the new
> syscall at all (avoiding the need for fallback logic), but that need
> to convert relative times or such between legacy kernel format and new
> userspace format:
>
> - nanosleep
> - clock_getres
> - sched_rr_get_interval
> - pselect
> - ppoll
> - sigtimedwait
> - recvmmsg
> - __timedwait
> - getrusage
Arnd noted additions to this list:
- setitimer
- getitimer
- wait3
- wait4
And additional functions that have indirect time_t dependency in their
interfaces that may need redirection if redirection is done:
- aio_suspend
- sched_getparam
- sched_setparam
- sched_setscheduler
- pthread_getschedparam
- pthread_setschedparam
- pthread_attr_getschedparam
- pthread_attr_setschedparam
- posix_spawnattr_getschedparam
- posix_spawnattr_setschedparam
My leaning for the schedparam stuff is actually not to do any
redirctions, but instead remove the SCHED_SPORADIC cruft (Linux has
never supported it and almost surely won't) and instead replace the
members with "unused" fields of the same size that we could later
repurpose for something else useful.
Rich
prev parent reply other threads:[~2019-07-04 19:07 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-07-01 20:11 Rich Felker
2019-07-01 22:36 ` A. Wilcox
2019-07-04 19:07 ` Rich Felker [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=20190704190757.GD1506@brightrain.aerifal.cx \
--to=dalias@libc.org \
--cc=musl@lists.openwall.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.
Code repositories for project(s) associated with this public inbox
https://git.vuxu.org/mirror/musl/
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 NNTP newsgroup(s).