From: Cyril Hrubis <chrubis@suse.cz>
To: ltp@lists.linux.it
Subject: [LTP] [PATCH 2/3] lib: implement rtctime_save and rtctime_restore function
Date: Thu, 7 Jan 2021 14:57:44 +0100 [thread overview]
Message-ID: <X/cTWFNvtJ5NCyOh@yuki.lan> (raw)
In-Reply-To: <20201223033517.1464263-3-gengcixi@gmail.com>
> static struct timespec real_begin, mono_begin;
>
> +static struct rtc_time rtc_begin;
> +
> static int clock_saved;
>
> void tst_wallclock_save(void)
> @@ -58,3 +61,42 @@ void tst_wallclock_restore(void)
> if (tst_clock_settime(CLOCK_REALTIME, &adjust))
> tst_brk(TBROK | TERRNO, "tst_clock_settime() realtime failed");
> }
> +
> +void tst_rtctime_save(void)
> +{
> + /* save initial monotonic time to restore it when needed */
> + if (tst_rtc_gettime(&rtc_begin))
> + tst_brk(TBROK | TERRNO, "tst_rtc_gettime() realtime failed");
> +
> + if (tst_clock_gettime(CLOCK_MONOTONIC_RAW, &mono_begin))
> + tst_brk(TBROK | TERRNO, "tst_clock_gettime() monotonic failed");
> +
> + clock_saved = 1;
It would be better if we defined rtc_clock_saved for the rtc* functions
instead.
> +}
> +
> +void tst_rtctime_restore(void)
> +{
> + static struct timespec mono_end, elapsed;
> + static struct timespec rtc_begin_tm, rtc_adjust;
> + static struct rtc_time rtc_restore;
> +
> + if (!clock_saved)
> + return;
> +
> + clock_saved = 0;
> +
> + if (tst_clock_gettime(CLOCK_MONOTONIC_RAW, &mono_end))
> + tst_brk(TBROK | TERRNO, "tst_clock_gettime() monotonic failed");
> +
> + elapsed = tst_timespec_diff(mono_end, mono_begin);
> +
> + rtc_begin_tm.tv_sec = tst_rtc_tm_to_time(&rtc_begin);
We should clear the tv_nsec here otherwise it will contain garbage.
> + rtc_adjust = tst_timespec_add(rtc_begin_tm, elapsed);
> +
> + tst_rtc_time_to_tm(rtc_adjust.tv_sec, &rtc_restore);
> +
> + /* restore realtime clock based on monotonic delta */
> + if (tst_rtc_settime(&rtc_restore))
> + tst_brk(TBROK | TERRNO, "tst_rtc_settime() realtime failed");
> +}
Other than this, it looks good.
--
Cyril Hrubis
chrubis@suse.cz
next prev parent reply other threads:[~2021-01-07 13:57 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-12-23 3:35 [LTP] [PATCH 0/3] add rtctime libs and rtc02 case gengcixi
2020-12-23 3:35 ` [LTP] [PATCH 1/3] lib: add tst_rtctime* for rtc test gengcixi
2021-01-07 13:50 ` Cyril Hrubis
2021-01-08 8:30 ` Cixi Geng
2020-12-23 3:35 ` [LTP] [PATCH 2/3] lib: implement rtctime_save and rtctime_restore function gengcixi
2021-01-07 13:57 ` Cyril Hrubis [this message]
2021-01-08 9:19 ` Cixi Geng
2021-01-08 9:34 ` Cyril Hrubis
2021-01-08 9:45 ` Cixi Geng
2020-12-23 3:35 ` [LTP] [PATCH 3/3] rtc02: add rtc set time verify case gengcixi
2021-01-07 14:32 ` Cyril Hrubis
2021-01-07 14:33 ` [LTP] [PATCH 0/3] add rtctime libs and rtc02 case 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=X/cTWFNvtJ5NCyOh@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