Linux Test Project
 help / color / mirror / Atom feed
From: Waiman Long <longman@redhat.com>
To: Li Wang <liwang@redhat.com>, ltp@lists.linux.it
Cc: Viresh Kumar <viresh.kumar@linaro.org>,
	Eirik Fuller <efuller@redhat.com>, Waiman Long <llong@redhat.com>
Subject: Re: [LTP] [PATCH] clock_gettime04: set threshold based on the clock tick rate
Date: Fri, 25 Mar 2022 10:26:13 -0400	[thread overview]
Message-ID: <badfd854-f6c6-24ea-eeec-e2772aff2578@redhat.com> (raw)
In-Reply-To: <20220325040057.544211-1-liwang@redhat.com>

On 3/25/22 00:00, Li Wang wrote:
> This is to get rid of the intermittent failures in clock_gettime04,
> which are likely caused by different clock tick rates on platforms.
> Here set the threshold no less than each clock tick in millisecond:
>
> 	delta = 1000(ms)/ticks_number_per_sec + 5;
>
> Error log:
>    clock_gettime04.c:163: TFAIL: CLOCK_REALTIME_COARSE(syscall with old kernel spec):
>          Difference between successive readings greater than 5 ms (1): 10
>    clock_gettime04.c:163: TFAIL: CLOCK_MONOTONIC_COARSE(vDSO with old kernel spec):
> 	Difference between successive readings greater than 5 ms (2): 10
>
>  From Waiman Long:
>    That failure happens for CLOCK_REALTIME_COARSE which is a faster but less
>    precise version of CLOCK_REALTIME. The time resolution is actually a clock
>    tick. Since arm64 has a HZ rate of 100. That means each tick is 10ms. So a
>    CLOCK_REALTIME_COARSE threshold of 5ms is probably not enough. I would say
>    in the case of CLOCK_REALTIME_COARSE, we have to increase the threshold based
>    on the clock tick rate of the system. This is more a test failure than is
>    an inherent problem in the kernel.
>
> Fixes #898
>
> Reported-by: Eirik Fuller <efuller@redhat.com>
> Signed-off-by: Li Wang <liwang@redhat.com>
> Cc: Waiman Long <llong@redhat.com>
> Cc: Viresh Kumar <viresh.kumar@linaro.org>
> ---
>   testcases/kernel/syscalls/clock_gettime/clock_gettime04.c | 3 ++-
>   1 file changed, 2 insertions(+), 1 deletion(-)
>
> diff --git a/testcases/kernel/syscalls/clock_gettime/clock_gettime04.c b/testcases/kernel/syscalls/clock_gettime/clock_gettime04.c
> index a8d2c5b38..cccbc9383 100644
> --- a/testcases/kernel/syscalls/clock_gettime/clock_gettime04.c
> +++ b/testcases/kernel/syscalls/clock_gettime/clock_gettime04.c
> @@ -35,7 +35,7 @@ clockid_t clks[] = {
>   };
>   
>   static gettime_t ptr_vdso_gettime, ptr_vdso_gettime64;
> -static long long delta = 5;
> +static long long delta;
>   
>   static inline int do_vdso_gettime(gettime_t vdso, clockid_t clk_id, void *ts)
>   {
> @@ -92,6 +92,7 @@ static struct time64_variants variants[] = {
>   
>   static void setup(void)
>   {
> +	delta = 1000/sysconf(_SC_CLK_TCK) + 5;
>   	if (tst_is_virt(VIRT_ANY)) {
>   		tst_res(TINFO, "Running in a virtual machine, multiply the delta by 10.");
>   		delta *= 10;

Actually, only CLOCK_REALTIME_COARSE and CLOCK_MONOTONIC_COARSE use 
clock tick for its time measurement. The rests use a higher resolution 
internal timer. Perhaps, we could have a separate coarse_delta for these 
two cases and use delta for the rest.

Cheers,
Longman


-- 
Mailing list info: https://lists.linux.it/listinfo/ltp

  parent reply	other threads:[~2022-03-28  9:02 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-03-25  4:00 [LTP] [PATCH] clock_gettime04: set threshold based on the clock tick rate Li Wang
2022-03-25 10:13 ` Cyril Hrubis
2022-03-26 13:17   ` Li Wang
2022-03-28  8:58     ` Cyril Hrubis
2022-03-28  9:54       ` Li Wang
2022-03-28 10:13         ` Li Wang
2022-03-28 10:24           ` Li Wang
2022-03-28 12:41             ` Cyril Hrubis
2022-03-25 14:26 ` Waiman Long [this message]
2022-03-26 13:28   ` 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=badfd854-f6c6-24ea-eeec-e2772aff2578@redhat.com \
    --to=longman@redhat.com \
    --cc=efuller@redhat.com \
    --cc=liwang@redhat.com \
    --cc=llong@redhat.com \
    --cc=ltp@lists.linux.it \
    --cc=viresh.kumar@linaro.org \
    /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