From: Vasileios Almpanis <vasileios.almpanis@virtuozzo.com>
To: Eva Kurchatova <eva.kurchatova@virtuozzo.com>
Cc: devel@openvz.org
Subject: Re: [Devel] [PATCH vz10 3/3] selftests: timers: measure the cpu timers on the clock they count
Date: Fri, 18 Sep 2026 10:44:19 +0000 [thread overview]
Message-ID: <178972825916.648180.13792516922333639549.b4-review@b4> (raw)
In-Reply-To: <20260831224603.1641737-3-eva.kurchatova@virtuozzo.com>
> Commit b00385b8d081 ("selftests/posix_timers: Use CLOCK_THREAD_CPUTIME_ID
> for ITIMER_PROF measurements") gave ITIMER_PROF the clock it counts,
> as measuring a cpu timer against the wall says nothing on a machine
> where the task does not have a cpu to itself. The other cpu timers
> are still measured against CLOCK_REALTIME and fail the same way.
> With four busy loops on the two cpus of a test machine:
>
> not ok 2 ITIMER_VIRTUAL
> not ok 5 timer_create() per CLOCK_THREAD_CPUTIME_ID
> not ok 6 timer_create() per CLOCK_PROCESS_CPUTIME_ID
>
> ITIMER_VIRTUAL counts the time the task spends in userspace, so take
> CLOCK_THREAD_CPUTIME_ID for it as well; the loop it runs stays in
> userspace, so what that clock adds for system time is far inside the
> half a second the check allows. check_timer_create() arms its timer on
> the clock it is given, so measure on that one.
>
> The test then passes whole on that machine, 19 of 19, busy or idle.
>
> https://virtuozzo.atlassian.net/browse/VSTOR-143363
> Feature: fix selftests
> Signed-off-by: Eva Kurchatova <eva.kurchatova@virtuozzo.com>
>
> diff --git a/tools/testing/selftests/timers/posix_timers.c b/tools/testing/selftests/timers/posix_timers.c
> index 077a98fb1b1d..66993bd632ec 100644
> --- a/tools/testing/selftests/timers/posix_timers.c
> +++ b/tools/testing/selftests/timers/posix_timers.c
> @@ -112,9 +112,10 @@ static void check_itimer(int which, const char *name)
>
> done = 0;
>
> - if (which == ITIMER_VIRTUAL)
> + if (which == ITIMER_VIRTUAL) {
> + clock_id = CLOCK_THREAD_CPUTIME_ID;
> signal(SIGVTALRM, sig_handler);
> - else if (which == ITIMER_PROF) {
> + } else if (which == ITIMER_PROF) {
> clock_id = CLOCK_THREAD_CPUTIME_ID;
> signal(SIGPROF, sig_handler);
> }
ITIMER_REAL is measured with CLOCK_REALTIME but the kernel arms it with
CLOCK_MONOTONIC.
hrtimer_setup(&sig->real_timer, it_real_fn, CLOCK_MONOTONIC, HRTIMER_MODE_REL)
in kernel/fork.c
Set it for this arm too. Since realtime will also get
its own clock maybe it would read better to have a switch instead of an
if/else if/else if.
--
Vasileios Almpanis <vasileios.almpanis@virtuozzo.com>
_______________________________________________
Devel mailing list
Devel@openvz.org
https://lists.openvz.org/mailman/listinfo/devel
prev parent reply other threads:[~2026-09-18 10:45 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-08-31 22:45 [Devel] [PATCH vz10 1/3] ms/selftests/posix_timers: Use CLOCK_THREAD_CPUTIME_ID for ITIMER_PROF measurements Eva Kurchatova
2026-08-31 22:45 ` [Devel] [PATCH vz10 2/3] selftests: timers: count what tick is worth in the drift estimate Eva Kurchatova
2026-08-31 22:46 ` [Devel] [PATCH vz10 3/3] selftests: timers: measure the cpu timers on the clock they count Eva Kurchatova
2026-09-18 10:44 ` Vasileios Almpanis [this message]
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=178972825916.648180.13792516922333639549.b4-review@b4 \
--to=vasileios.almpanis@virtuozzo.com \
--cc=devel@openvz.org \
--cc=eva.kurchatova@virtuozzo.com \
/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