Commit message (Collapse) | Author | Age | Files | Lines | |
---|---|---|---|---|---|
* | linux: Only use 64-bit syscall if required for ppoll | Adhemerval Zanella | 2021-06-22 | 1 | -0/+15 |
| | | | | | | | | | | | | | For !__ASSUME_TIME64_SYSCALLS there is no need to issue a 64-bit syscall if the provided timeout fits in a 32-bit one. The 64-bit usage should be rare since the timeout is a relative one. This also avoids the need to use supports_time64() (which breaks the usage case of live migration like CRIU or similar). Checked on i686-linux-gnu on a 4.15 kernel and on a 5.11 kernel (with and without --enable-kernel=5.1) and on x86_64-linux-gnu. Reviewed-by: Lukasz Majewski <lukma@denx.de> | ||||
* | tst: Provide test for ppoll | Lukasz Majewski | 2021-02-08 | 1 | -0/+56 |
This change adds new test to assess ppoll()'s timeout related functionality (the struct pollfd does not provide valid fd to wait for - just wait for timeout). To be more specific - two use cases are checked: - if ppoll() times out immediately when passed struct timespec has zero values of tv_nsec and tv_sec. - if ppoll() times out after timeout specified in passed argument |