From: Juri Lelli <juri.lelli@redhat.com>
To: Gabriele Monaco <gmonaco@redhat.com>
Cc: Shuah Khan <shuah@kernel.org>,
Peter Zijlstra <peterz@infradead.org>,
Ingo Molnar <mingo@redhat.com>,
Vincent Guittot <vincent.guittot@linaro.org>,
Dietmar Eggemann <dietmar.eggemann@arm.com>,
Steven Rostedt <rostedt@goodmis.org>,
Valentin Schneider <vschneid@redhat.com>,
Clark Williams <williams@redhat.com>,
Tommaso Cucinotta <tommaso.cucinotta@santannapisa.it>,
Luca Abeni <luca.abeni@santannapisa.it>,
linux-kernel@vger.kernel.org, linux-kselftest@vger.kernel.org
Subject: Re: [PATCH RFC 4/7] selftests/sched: Add basic SCHED_DEADLINE functionality tests
Date: Mon, 9 Mar 2026 10:11:29 +0100 [thread overview]
Message-ID: <aa6OwVhOn2sHyMcc@jlelli-thinkpadt14gen4.remote.csb> (raw)
In-Reply-To: <64fa81f453d7909e5669cc32284f7c9f48f2fea9.camel@redhat.com>
On 09/03/26 09:15, Gabriele Monaco wrote:
> Hello,
>
> On Fri, 2026-03-06 at 17:10 +0100, Juri Lelli wrote:
> > Add initial test coverage for SCHED_DEADLINE scheduler functionality.
> > This patch introduces two fundamental tests that validate core
> > SCHED_DEADLINE behavior using the test framework and utility library.
> >
> > The basic_scheduling test creates a cpuhog process with SCHED_DEADLINE
> > policy and verifies the scheduling policy is correctly set to policy 6
> > (SCHED_DEADLINE). It confirms the task executes successfully for the
> > specified duration using reasonable parameters with 30ms runtime, 100ms
> > deadline, and 100ms period. This validates the fundamental operation of
> > setting SCHED_DEADLINE policy and running deadline-scheduled tasks.
> >
> > The parameter_validation test ensures the kernel properly validates
> > SCHED_DEADLINE parameters. It tests that invalid parameter combinations
> > such as runtime greater than deadline are correctly rejected with
> > EINVAL, while valid parameter configurations are accepted. This confirms
> > the kernel's parameter validation logic is working correctly and
> > prevents misconfigured deadline tasks from being scheduled.
> >
> > Both tests use the dl_util library for SCHED_DEADLINE operations and
> > follow the framework pattern with automatic registration via
> > REGISTER_DL_TEST(). The tests pass cleanly in VM environments with 2
> > tests passing, 0 skipped, and 0 failed.
> >
> > Assisted-by: Claude Code: claude-sonnet-4-5@20250929
> > Signed-off-by: Juri Lelli <juri.lelli@redhat.com>
> > ---
> ...
> >
> > +# Test files
> > +$(OUTPUT)/basic.o: basic.c dl_test.h dl_util.h | $(OUTPUT_DIR)
> > + $(CC) $(CFLAGS) -c $< -o $@
> > +
>
> This seems a constant in all tests, what about just having make do the trick:
>
> $(OUTPUT)/%.o: %.c dl_test.h dl_util.h | $(OUTPUT_DIR)
> $(CC) $(CFLAGS) -c $< -o $@
That should work, thanks!
> The rest looks neat.
Cool. Thanks again for reviewing.
Best,
Juri
next prev parent reply other threads:[~2026-03-09 9:11 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-03-06 16:10 [PATCH RFC 0/7] selftests/sched: Add comprehensive SCHED_DEADLINE test suite Juri Lelli
2026-03-06 16:10 ` [PATCH RFC 1/7] selftests/sched: Add SCHED_DEADLINE test framework infrastructure Juri Lelli
2026-03-09 8:20 ` Gabriele Monaco
2026-03-09 9:10 ` Juri Lelli
2026-03-06 16:10 ` [PATCH RFC 2/7] selftests/sched: Add SCHED_DEADLINE utility library Juri Lelli
2026-03-11 9:39 ` Christian Loehle
2026-03-11 13:15 ` Juri Lelli
2026-03-06 16:10 ` [PATCH RFC 3/7] selftests/sched: Integrate SCHED_DEADLINE tests into kselftest framework Juri Lelli
2026-03-06 16:10 ` [PATCH RFC 4/7] selftests/sched: Add basic SCHED_DEADLINE functionality tests Juri Lelli
2026-03-09 8:15 ` Gabriele Monaco
2026-03-09 9:11 ` Juri Lelli [this message]
2026-03-06 16:10 ` [PATCH RFC 5/7] selftests/sched: Add SCHED_DEADLINE bandwidth tests to kselftest Juri Lelli
2026-03-11 9:31 ` Christian Loehle
2026-03-11 13:23 ` Juri Lelli
2026-03-11 13:44 ` Christian Loehle
2026-03-11 14:26 ` Christian Loehle
2026-03-12 10:43 ` Christian Loehle
2026-03-12 11:30 ` Christian Loehle
2026-03-12 14:13 ` Juri Lelli
2026-03-06 16:10 ` [PATCH RFC 6/7] selftests/sched: Add SCHED_DEADLINE fair_server " Juri Lelli
2026-03-06 16:10 ` [PATCH RFC 7/7] selftests/sched: Add SCHED_DEADLINE ENQUEUE_REPLENISH bug test Juri Lelli
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=aa6OwVhOn2sHyMcc@jlelli-thinkpadt14gen4.remote.csb \
--to=juri.lelli@redhat.com \
--cc=dietmar.eggemann@arm.com \
--cc=gmonaco@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-kselftest@vger.kernel.org \
--cc=luca.abeni@santannapisa.it \
--cc=mingo@redhat.com \
--cc=peterz@infradead.org \
--cc=rostedt@goodmis.org \
--cc=shuah@kernel.org \
--cc=tommaso.cucinotta@santannapisa.it \
--cc=vincent.guittot@linaro.org \
--cc=vschneid@redhat.com \
--cc=williams@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