From: Cyril Hrubis <chrubis@suse.cz>
To: ltp@lists.linux.it
Subject: [LTP] [PATCH V3 5/6] syscalls: Don't pass struct timespec to tst_syscall()
Date: Wed, 17 Jun 2020 14:30:29 +0200 [thread overview]
Message-ID: <20200617123029.GC8389@yuki.lan> (raw)
In-Reply-To: <c47220ecab3c7570f5387cd71894c977009ad3d8.1590572545.git.viresh.kumar@linaro.org>
Hi!
> Signed-off-by: Viresh Kumar <viresh.kumar@linaro.org>
> ---
> V3:
> - Run the syscalls at least once to verify they are supported by the
> hardware.
>
> lib/tst_clocks.c | 90 ++++++++++++++++++++++++++++++++++++++++++++++--
> 1 file changed, 87 insertions(+), 3 deletions(-)
>
> diff --git a/lib/tst_clocks.c b/lib/tst_clocks.c
> index 2eaa73b11abe..ddf54b903133 100644
> --- a/lib/tst_clocks.c
> +++ b/lib/tst_clocks.c
> @@ -7,23 +7,107 @@
>
> #define TST_NO_DEFAULT_MAIN
> #include "tst_test.h"
> +#include "tst_timer.h"
> #include "tst_clocks.h"
> #include "lapi/syscalls.h"
> #include "lapi/posix_clocks.h"
>
> +typedef int (*mysyscall)(clockid_t clk_id, void *ts);
> +
> +int syscall_supported_by_kernel(mysyscall func)
> +{
> + int ret;
> +
> + ret = func(0, NULL);
> + if (ret == ENOSYS)
> + return 0;
I guess that we will get -1 here and errno == ENOSYS instead since the
tst_syscall() calls syscall() that passes the error in errno.
> + return 1;
> +}
> +
> int tst_clock_getres(clockid_t clk_id, struct timespec *res)
> {
> - return tst_syscall(__NR_clock_getres, clk_id, res);
> + static struct tst_ts tts = { 0, };
> + static mysyscall func;
> + int ret;
> +
> +#if (__NR_clock_getres_time64 != __LTP__NR_INVALID_SYSCALL)
> + if (!func && syscall_supported_by_kernel(sys_clock_getres64)) {
> + func = sys_clock_getres64;
> + tts.type = TST_KERN_TIMESPEC;
> + }
> +#endif
> +
> + if (!func && syscall_supported_by_kernel(sys_clock_getres)) {
> + func = sys_clock_getres;
> + tts.type = TST_KERN_OLD_TIMESPEC;
> + }
> +
> + if (!func) {
> + tst_res(TCONF, "clock_getres() not available");
> + return ENOSYS;
Here as well, the callers expects the error in errno, so we have to set
the errno to ENOSYS and return -1 instead.
> + }
> +
> + ret = func(clk_id, tst_ts_get(&tts));
> + res->tv_sec = tst_ts_get_sec(tts);
> + res->tv_nsec = tst_ts_get_nsec(tts);
> + return ret;
> }
>
> int tst_clock_gettime(clockid_t clk_id, struct timespec *ts)
> {
> - return tst_syscall(__NR_clock_gettime, clk_id, ts);
> + struct tst_ts tts = { 0, };
> + static mysyscall func;
> + int ret;
> +
> +#if (__NR_clock_gettime64 != __LTP__NR_INVALID_SYSCALL)
> + if (!func && syscall_supported_by_kernel(sys_clock_gettime64)) {
> + func = sys_clock_gettime64;
> + tts.type = TST_KERN_TIMESPEC;
> + }
> +#endif
> +
> + if (!func && syscall_supported_by_kernel(sys_clock_gettime)) {
> + func = sys_clock_gettime;
> + tts.type = TST_KERN_OLD_TIMESPEC;
> + }
> +
> + if (!func) {
> + tst_res(TCONF, "clock_gettime() not available");
> + return ENOSYS;
Here as well.
> + }
> +
> + ret = func(clk_id, tst_ts_get(&tts));
> + ts->tv_sec = tst_ts_get_sec(tts);
> + ts->tv_nsec = tst_ts_get_nsec(tts);
> + return ret;
> }
>
> int tst_clock_settime(clockid_t clk_id, struct timespec *ts)
> {
> - return tst_syscall(__NR_clock_settime, clk_id, ts);
> + struct tst_ts tts = { 0, };
> + static mysyscall func;
> +
> +#if (__NR_clock_settime64 != __LTP__NR_INVALID_SYSCALL)
> + if (!func && syscall_supported_by_kernel(sys_clock_settime64)) {
> + func = sys_clock_settime64;
> + tts.type = TST_KERN_TIMESPEC;
> + }
> +#endif
> +
> + if (!func && syscall_supported_by_kernel(sys_clock_settime)) {
> + func = sys_clock_settime;
> + tts.type = TST_KERN_OLD_TIMESPEC;
> + }
> +
> + if (!func) {
> + tst_res(TCONF, "clock_settime() not available");
> + return ENOSYS;
And here.
> + }
> +
> + tst_ts_set_sec(&tts, ts->tv_sec);
> + tst_ts_set_nsec(&tts, ts->tv_nsec);
> + return func(clk_id, tst_ts_get(&tts));
> }
Other than that it looks good.
--
Cyril Hrubis
chrubis@suse.cz
next prev parent reply other threads:[~2020-06-17 12:30 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-05-22 6:54 [LTP] [PATCH V2 0/6] syscalls: Remove incorrect usage of libc structures Viresh Kumar
2020-05-22 6:54 ` [LTP] [PATCH V2 1/6] tst_safe_clocks: Remove safe_clock_adjtime() Viresh Kumar
2020-05-22 6:54 ` [LTP] [PATCH V2 2/6] syscalls: settimeofday01: Set .restore_wallclock flag Viresh Kumar
2020-05-22 6:54 ` [LTP] [PATCH V2 3/6] syscalls: settimeofday02: Remove time restoration code Viresh Kumar
2020-05-22 6:54 ` [LTP] [PATCH V2 4/6] syscalls: settimeofday: Use gettimeofday() Viresh Kumar
2020-06-17 12:17 ` Cyril Hrubis
2020-05-22 6:54 ` [LTP] [PATCH V2 5/6] syscalls: Don't pass struct timespec to tst_syscall() Viresh Kumar
2020-05-22 8:02 ` Arnd Bergmann
2020-05-22 8:42 ` Viresh Kumar
2020-05-22 8:58 ` Cyril Hrubis
2020-06-17 12:22 ` Cyril Hrubis
2020-05-27 9:43 ` [LTP] [PATCH V3 " Viresh Kumar
2020-05-27 9:49 ` Arnd Bergmann
2020-06-17 12:30 ` Cyril Hrubis [this message]
2020-06-18 5:25 ` [LTP] [PATCH V4 " Viresh Kumar
2020-06-18 11:06 ` Cyril Hrubis
2020-07-03 9:55 ` Li Wang
2020-07-03 12:26 ` Harish
2020-07-03 12:59 ` Cyril Hrubis
2020-07-04 7:14 ` Li Wang
2020-07-06 8:44 ` Harish
2020-07-06 8:57 ` Li Wang
2020-07-06 9:21 ` Harish
2020-07-07 9:03 ` Cyril Hrubis
2020-07-07 9:18 ` Viresh Kumar
2020-07-07 11:49 ` Cyril Hrubis
2020-07-08 2:34 ` Viresh Kumar
2020-07-06 2:21 ` Viresh Kumar
2020-05-22 6:54 ` [LTP] [PATCH V2 6/6] syscalls: Don't pass struct timeval " Viresh Kumar
2020-06-17 14:08 ` Cyril Hrubis
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=20200617123029.GC8389@yuki.lan \
--to=chrubis@suse.cz \
--cc=ltp@lists.linux.it \
/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