From: Cyril Hrubis <chrubis@suse.cz>
To: ltp@lists.linux.it
Subject: [LTP] [PATCH v3 3/4] tst_timer: Create interface for using multiple timers
Date: Thu, 16 Aug 2018 14:22:48 +0200 [thread overview]
Message-ID: <20180816122247.GD6547@rei> (raw)
In-Reply-To: <20180816120020.11042-3-rpalethorpe@suse.com>
Hi!
> +/**
> + * Encapsulates a stopwatch timer.
> + *
> + * Useful when you need to use multiple timers in a single test.
> + */
> +struct tst_timer {
> + /** The POSIX clock type */
> + clockid_t clock_id;
> + /** How much time can pass before tst_timer_expired_st() returns true */
> + struct timespec limit;
> + /** Where to start measuring time from */
> + struct timespec start_time;
> +};
> +
> /*
> * Converts timespec to microseconds.
> */
> @@ -251,6 +265,14 @@ void tst_timer_check(clockid_t clk_id);
> */
> void tst_timer_start(clockid_t clk_id);
>
> +/**
> + * Sets the start time for timer tim.
> + *
> + * @relates tst_timer
> + * @param tim The timer to start
> + */
> +void tst_timer_start_st(struct tst_timer *tim);
So user is expected to fill in the tst_timer structure before this call
is called, right?
Maybe it would be easier to pass the timeout and CLOCK_ID to this
function and keep the initialization in the test library, that way we
can also check if the timer is supported first before we return from the
start function.
And lastly but not least, we were also discussion special timer id,
something as TST_TIMER_DEFAULT that would select appropriate timer,
althoug I guess that CLOCK_MONOTONIC is supporoted on anything that we
care for these days.
> /*
> * Returns true if timer started by tst_timer_start() has been running for
> * longer than ms seconds.
> @@ -259,6 +281,14 @@ void tst_timer_start(clockid_t clk_id);
> */
> int tst_timer_expired_ms(long long ms);
>
> +/**
> + * Returns true if timer tim has been running for longer than tst_timer::limit
> + *
> + * @relates tst_timer
> + * @param tim The timer to check
> + */
> +int tst_timer_expired_st(struct tst_timer *tim);
> +
> /*
> * Marks timer end time.
> */
> diff --git a/lib/tst_timer.c b/lib/tst_timer.c
> index d5e4c49d2..baec18280 100644
> --- a/lib/tst_timer.c
> +++ b/lib/tst_timer.c
> @@ -79,6 +79,12 @@ void tst_timer_start(clockid_t clk_id)
> tst_res(TWARN | TERRNO, "tst_clock_gettime() failed");
> }
>
> +void tst_timer_start_st(struct tst_timer *tim)
> +{
> + if (tst_clock_gettime(tim->clock_id, &tim->start_time))
> + tst_res(TWARN | TERRNO, "tst_clock_gettime() failed");
> +}
> +
> int tst_timer_expired_ms(long long ms)
> {
> struct timespec cur_time;
> @@ -89,6 +95,17 @@ int tst_timer_expired_ms(long long ms)
> return tst_timespec_diff_ms(cur_time, start_time) >= ms;
> }
>
> +int tst_timer_expired_st(struct tst_timer *tim)
> +{
> + struct timespec cur_time;
> +
> + if (tst_clock_gettime(tim->clock_id, &cur_time))
> + tst_res(TWARN | TERRNO, "tst_clock_gettime() failed");
> +
> + return tst_timespec_lt(tim->limit,
> + tst_timespec_diff(cur_time, tim->start_time));
> +}
> +
> void tst_timer_stop(void)
> {
> if (tst_clock_gettime(clock_id, &stop_time))
> --
> 2.18.0
>
>
> --
> Mailing list info: https://lists.linux.it/listinfo/ltp
--
Cyril Hrubis
chrubis@suse.cz
next prev parent reply other threads:[~2018-08-16 12:22 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-08-16 12:00 [LTP] [PATCH v3 1/4] lib: Allow user to easily get LTP_TIMEOUT_MUL value Richard Palethorpe
2018-08-16 12:00 ` [LTP] [PATCH v3 2/4] tst_timer: Convert to new library Richard Palethorpe
2018-08-16 12:08 ` Cyril Hrubis
2018-08-16 12:00 ` [LTP] [PATCH v3 3/4] tst_timer: Create interface for using multiple timers Richard Palethorpe
2018-08-16 12:22 ` Cyril Hrubis [this message]
2018-08-16 12:27 ` Cyril Hrubis
2018-08-16 13:06 ` Richard Palethorpe
2018-08-16 12:58 ` Richard Palethorpe
2018-08-16 12:59 ` Cyril Hrubis
2018-08-16 12:00 ` [LTP] [PATCH v3 4/4] fzsync: Limit execution time to prevent test timeouts Richard Palethorpe
2018-08-17 7:43 ` Li Wang
2018-08-17 9:04 ` Li Wang
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=20180816122247.GD6547@rei \
--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