From: Nam Cao <namcao@linutronix.de>
To: Peter Zijlstra <peterz@infradead.org>
Cc: Steven Rostedt <rostedt@goodmis.org>,
Masami Hiramatsu <mhiramat@kernel.org>,
Mathieu Desnoyers <mathieu.desnoyers@efficios.com>,
Gabriele Monaco <gmonaco@redhat.com>,
linux-trace-kernel@vger.kernel.org, linux-kernel@vger.kernel.org,
Ingo Molnar <mingo@redhat.com>,
Juri Lelli <juri.lelli@redhat.com>,
Vincent Guittot <vincent.guittot@linaro.org>,
Dietmar Eggemann <dietmar.eggemann@arm.com>,
Ben Segall <bsegall@google.com>, Mel Gorman <mgorman@suse.de>,
Valentin Schneider <vschneid@redhat.com>,
K Prateek Nayak <kprateek.nayak@amd.com>
Subject: Re: [PATCH v2 5/5] rv: Add rts monitor
Date: Tue, 19 Aug 2025 09:54:57 +0200 [thread overview]
Message-ID: <20250819075457.AqRdkkvf@linutronix.de> (raw)
In-Reply-To: <20250815134851.GC3289052@noisy.programming.kicks-ass.net>
On Fri, Aug 15, 2025 at 03:48:51PM +0200, Peter Zijlstra wrote:
> On Wed, Aug 06, 2025 at 10:01:21AM +0200, Nam Cao wrote:
> > Add "real-time scheduling" monitor, which validates that SCHED_RR and
> > SCHED_FIFO tasks are scheduled before tasks with normal and extensible
> > scheduling policies
>
> The actual monitor seems to know about deadline too. Surely changelog
> and document need updating?
Yes.
> While there, you should probably extend to cover at least STOP class,
> but possibly also IDLE class, no? Validating: IDLE < EXT < FAIR <
> FIFO/RR < DL < STOP.
Right, I forgot that idle and stop exists. Thanks for the reminder.
Nam
prev parent reply other threads:[~2025-08-19 7:55 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-08-06 8:01 [PATCH v2 0/5] rv: LTL per-cpu monitor type and real-time scheduling monitor Nam Cao
2025-08-06 8:01 ` [PATCH v2 1/5] rv/ltl: Prepare for other monitor types Nam Cao
2025-08-06 8:01 ` [PATCH v2 2/5] rv/ltl: Support per-cpu monitors Nam Cao
2025-08-07 13:28 ` Gabriele Monaco
2025-08-06 8:01 ` [PATCH v2 3/5] verification/rvgen/ltl: Support per-cpu monitor generation Nam Cao
2025-08-07 13:06 ` Gabriele Monaco
2025-08-08 5:12 ` Nam Cao
2025-08-08 6:21 ` Gabriele Monaco
2025-08-08 6:30 ` Nam Cao
2025-08-06 8:01 ` [PATCH v2 4/5] sched: Add task enqueue/dequeue trace points Nam Cao
2025-08-15 13:40 ` Peter Zijlstra
2025-08-15 13:52 ` Peter Zijlstra
2025-08-21 7:05 ` Nam Cao
2025-08-21 8:43 ` K Prateek Nayak
2025-08-19 7:49 ` Nam Cao
2025-08-19 8:24 ` Peter Zijlstra
2025-08-06 8:01 ` [PATCH v2 5/5] rv: Add rts monitor Nam Cao
2025-08-06 20:28 ` kernel test robot
2025-08-07 13:33 ` Gabriele Monaco
2025-08-08 5:13 ` Nam Cao
2025-08-07 14:34 ` Gabriele Monaco
2025-08-08 5:29 ` Nam Cao
2025-08-08 7:30 ` Gabriele Monaco
2025-08-15 13:48 ` Peter Zijlstra
2025-08-19 7:54 ` Nam Cao [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=20250819075457.AqRdkkvf@linutronix.de \
--to=namcao@linutronix.de \
--cc=bsegall@google.com \
--cc=dietmar.eggemann@arm.com \
--cc=gmonaco@redhat.com \
--cc=juri.lelli@redhat.com \
--cc=kprateek.nayak@amd.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-trace-kernel@vger.kernel.org \
--cc=mathieu.desnoyers@efficios.com \
--cc=mgorman@suse.de \
--cc=mhiramat@kernel.org \
--cc=mingo@redhat.com \
--cc=peterz@infradead.org \
--cc=rostedt@goodmis.org \
--cc=vincent.guittot@linaro.org \
--cc=vschneid@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;
as well as URLs for NNTP newsgroup(s).