OpenVZ / Virtuozzo kernel development (devel@openvz.org)
 help / color / mirror / Atom feed
From: Eva Kurchatova <eva.kurchatova@virtuozzo.com>
To: vasileios.almpanis@virtuozzo.com
Cc: devel@openvz.org
Subject: [Devel] [PATCH vz10 v2 0/3] selftests: timers: raw_skew fixes
Date: Mon, 21 Sep 2026 23:46:27 +0300	[thread overview]
Message-ID: <20260921204643.2692341-1-eva.kurchatova@virtuozzo.com> (raw)

Changes since v1:
- Use CLOCK_MONOTONIC based on the kernel implementation
- Use a switch to choose a clock
- Re-verified on a dev node with CPU stressing

Eva Kurchatova (2):
  selftests: timers: count what tick is worth in the drift estimate
  selftests: timers: measure each timer on the clock it is armed with

John Stultz (1):
  ms/selftests/posix_timers: Use CLOCK_THREAD_CPUTIME_ID for ITIMER_PROF
    measurements

 tools/testing/selftests/timers/posix_timers.c | 68 +++++++++++--------
 tools/testing/selftests/timers/raw_skew.c     | 12 ++++
 2 files changed, 51 insertions(+), 29 deletions(-)

-- 
2.55.0

_______________________________________________
Devel mailing list
Devel@openvz.org
https://lists.openvz.org/mailman/listinfo/devel

             reply	other threads:[~2026-09-21 20:48 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-09-21 20:46 Eva Kurchatova [this message]
2026-09-21 20:46 ` [Devel] [PATCH vz10 v2 1/3] ms/selftests/posix_timers: Use CLOCK_THREAD_CPUTIME_ID for ITIMER_PROF measurements Eva Kurchatova
2026-09-21 20:46 ` [Devel] [PATCH vz10 v2 2/3] selftests: timers: count what tick is worth in the drift estimate Eva Kurchatova
2026-09-21 20:46 ` [Devel] [PATCH vz10 v2 3/3] selftests: timers: measure each timer on the clock it is armed with Eva Kurchatova
2026-09-23 17:49 ` [Devel] [PATCH vz10 v2 0/3] selftests: timers: raw_skew fixes Konstantin Khorenko
2026-09-23 17:53 ` Konstantin Khorenko

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=20260921204643.2692341-1-eva.kurchatova@virtuozzo.com \
    --to=eva.kurchatova@virtuozzo.com \
    --cc=devel@openvz.org \
    --cc=vasileios.almpanis@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