From: Cyril Hrubis <chrubis@suse.cz>
To: Li Wang <liwang@redhat.com>
Cc: Philip Auld <pauld@redhat.com>, ltp@lists.linux.it
Subject: Re: [LTP] [RFC PATCH] starvation: set a baseline for maximum runtime
Date: Tue, 26 Nov 2024 11:28:05 +0100 [thread overview]
Message-ID: <Z0WitZsMZat6wdA2@yuki.lan> (raw)
In-Reply-To: <20241126100445.17133-1-liwang@redhat.com>
Hi!
> The commit ec14f4572 ("sched: starvation: Autocallibrate the timeout")
> introduced a runtime calibration mechanism to dynamically adjust test
> timeouts based on CPU speed.
>
> While this works well for slower systems like microcontrollers or ARM
> boards, it struggles to determine appropriate runtimes for modern CPUs,
> especially when debugging kernels with significant overhead.
Wouldn't it be better to either skip the test on kernels with debuging
confing options on? Or multiply the timeout we got from the callibration
when we detect a debugging kernel?
The problem is that any number we put there will not be correct in a few
years as CPU and RAM speed increase and the test will be effectively
doing nothing because the default we put there will cover kernels that
are overly slow on a future hardware.
--
Cyril Hrubis
chrubis@suse.cz
--
Mailing list info: https://lists.linux.it/listinfo/ltp
next prev parent reply other threads:[~2024-11-26 10:28 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-11-26 10:04 [LTP] [RFC PATCH] starvation: set a baseline for maximum runtime Li Wang
2024-11-26 10:28 ` Cyril Hrubis [this message]
2024-11-26 10:59 ` Li Wang
2024-11-26 11:23 ` Cyril Hrubis
2024-11-27 4:15 ` Li Wang
2024-11-27 7:48 ` [LTP] [Draft PATCH] lib: add TST_DYNAMICAL_RUNTIME option Li Wang
2024-11-27 8:21 ` Li Wang
2024-11-27 9:46 ` [LTP] [RFC PATCH] starvation: set a baseline for maximum runtime Cyril Hrubis
2024-11-27 10:08 ` Li Wang
2024-11-27 10:40 ` Cyril Hrubis
2024-11-27 10:56 ` 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=Z0WitZsMZat6wdA2@yuki.lan \
--to=chrubis@suse.cz \
--cc=liwang@redhat.com \
--cc=ltp@lists.linux.it \
--cc=pauld@redhat.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