On Wed, Jul 30, 2025 at 03:53:14PM +0200, Gabriele Monaco wrote:

On Wed, 2025-07-30 at 14:45 +0200, Nam Cao wrote:

quoted

Add trace points into enqueue_task_rt() and dequeue_task_rt(). They
are useful to implement RV monitor which validates RT scheduling.

I get it's much simpler this way, but is it that different to follow
the task's existing tracepoints?

* task going to sleep (switch:prev_state != RUNNING) is dequeued
* task waking up is enqueued
* changing the tasks's policy (setpolicy and setattr syscalls) should
enqueue/dequeue as well

This is more thinking out loud, but I'm doing right now something
rather similar with the deadline tasks and this seems reasonable, at
least on paper.

What do you think?

I think more or less the same. The fewer tracepoints, the better. But the
monitor is way more obvious this way.

Let me see how hard it is to use the existing tracepoints...

Nam