From: Petr Vorel <pvorel@suse.cz>
To: ltp@lists.linux.it
Cc: Martin Doucha <martin.doucha@suse.com>
Subject: Re: [LTP] [PATCH 5/6] runtest/sched: Add sched_football
Date: Mon, 29 Jul 2024 09:32:26 +0200 [thread overview]
Message-ID: <20240729073226.GA1223191@pevik> (raw)
In-Reply-To: <20240717171713.687339-6-pvorel@suse.cz>
Hi all,
> sched_football is useful not only for testing realtime,
> therefore add it also to runtest/sched.
> This depends on previous commit which enabled realtime by default.
> We ignore the possibility realtime tests are disabled.
> Suggested-by: Cyril Hrubis <chrubis@suse.cz>
> Signed-off-by: Petr Vorel <pvorel@suse.cz>
> ---
> runtest/sched | 2 ++
> 1 file changed, 2 insertions(+)
> diff --git a/runtest/sched b/runtest/sched
> index 5dab7a4c27..ecedd1a92b 100644
> --- a/runtest/sched
> +++ b/runtest/sched
> @@ -18,3 +18,5 @@ sched_cli_serv run_sched_cliserv.sh
> sched_stress sched_stress.sh
> autogroup01 autogroup01
> +
> +sched_football sched_football
I'm sorry, I haven't noticed, that realtime installs into a different directory:
cd ltp/testcases/realtime/func/sched_football
# make install
mkdir -p "/opt/ltp/testcases/realtime/func/sched_football"
install -m 00775 "ltp/testcases/realtime/func/sched_football/run_auto.sh" /opt/ltp/testcases/realtime/func/sched_football/run_auto.sh
install -m 00775 "ltp/testcases/realtime/func/sched_football/sched_football" /opt/ltp/testcases/realtime/func/sched_football/sched_football
Therefore scripts which expect it to have in the usual path $LTPROOT/testcases/bin
(e.g. /opt/ltp/testcases/bin) fail.
As temporary solution is to add $LTPROOT/testcases/realtime/func/sched_football/
to $PATH, for proper fix we have possibilities:
1) Either move sched_football.c out of realtime package (thus have some
duplicity, because it needs some of librealtime.a code),
2) or fully integrate realtime testsuite to LTP (e.g. convert librealtime.a to
normal LTP library in libs/ directory).
3) Change realtime make install target to install to $LTPROOT/testcases/bin and
ignore that some tests are not much useful for non-realtime kernels.
Just a reminder, to help which decision is better we have ticket for realtime
where is Mel Gorman's realtime usability investigation [1].
Because some time ago we planned to move tests to rt-tests testsuite [2] (we did
not consider to run them for non-realtime kernels, but recently Cyril saw
sched_football useful also for non-realtime kernels).
Do we plan to keep only sched_football in LTP or all tests? I suppose LTP should
only contains tests which are useful also for non-realtime kernels.
Kind regards,
Petr
[1] https://github.com/linux-test-project/ltp/issues/1078#issuecomment-2212913818
[2] https://git.kernel.org/pub/scm/utils/rt-tests/rt-tests.git
--
Mailing list info: https://lists.linux.it/listinfo/ltp
next prev parent reply other threads:[~2024-07-29 7:32 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-07-17 17:17 [LTP] [PATCH 0/6] sched_football in runtest/sched + configure cleanup Petr Vorel
2024-07-17 17:17 ` [LTP] [PATCH 1/6] configure: Print info about TI-RPC testsuite in summary Petr Vorel
2024-07-17 17:17 ` [LTP] [PATCH 2/6] configure: Don't assume testcases/realtime/configure.ac Petr Vorel
2024-07-17 17:17 ` [LTP] [PATCH 3/6] configure: Print info about KVM testsuite in summary Petr Vorel
2024-07-17 17:17 ` [LTP] [PATCH 4/6] configure: Enable realtime testsuite by default Petr Vorel
2024-07-17 17:17 ` [LTP] [PATCH 5/6] runtest/sched: Add sched_football Petr Vorel
2024-07-29 7:32 ` Petr Vorel [this message]
2024-07-29 9:47 ` Cyril Hrubis
2024-07-29 11:41 ` Petr Vorel
2024-07-17 17:17 ` [LTP] [PATCH 6/6] realtime: Use proper syntax for non-system include Petr Vorel
2024-07-18 8:22 ` [LTP] [PATCH 0/6] sched_football in runtest/sched + configure cleanup Cyril Hrubis
2024-07-18 10:29 ` Li Wang
2024-07-26 10:09 ` Petr Vorel
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=20240729073226.GA1223191@pevik \
--to=pvorel@suse.cz \
--cc=ltp@lists.linux.it \
--cc=martin.doucha@suse.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