From: Gabriele Monaco <gmonaco@redhat.com>
To: Nam Cao <namcao@linutronix.de>,
Steven Rostedt <rostedt@goodmis.org>,
Masami Hiramatsu <mhiramat@kernel.org>,
Mathieu Desnoyers <mathieu.desnoyers@efficios.com>,
linux-trace-kernel@vger.kernel.org,
linux-kernel@vger.kernel.org
Cc: Ingo Molnar <mingo@redhat.com>,
Peter Zijlstra <peterz@infradead.org>,
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: Fri, 08 Aug 2025 09:30:09 +0200 [thread overview]
Message-ID: <c0ae826c9a3d828ac8ab2088495e671cd9384a86.camel@redhat.com> (raw)
In-Reply-To: <87ikiypei8.fsf@yellow.woof>
On Fri, 2025-08-08 at 07:29 +0200, Nam Cao wrote:
> Gabriele Monaco <gmonaco@redhat.com> writes:
> > The monitor shows a violation also in case of priority inversion
> > boosting, e.g.:
> >
> > stress-ng --prio-inv 2
>
> This looks like something that would trigger the fair deadline server
> or RT throttling. Can you please try disabling both of them:
>
> echo 0 | tee /sys/kernel/debug/sched/fair_server/cpu*/runtime
> sysctl -w kernel.sched_rt_runtime_us=-1
>
> and see if the problem persists?
My bad, that was the fair server's doing, ignore what I said.
>
> > It seems perfectly reasonable from the monitor description but it's
> > actually a behaviour meant to improve real time response.
> > Is the user seeing this type of violation supposed to make sure all
> > locks held by RT tasks are never shared by fair tasks? If that's
> > the case I'd mention it in the description.
>
> Boosted fair tasks are treated as RT tasks ;)
>
> > Also very rarely I see failures while cleaning up the monitor, not
> > sure exactly what caused it but I could reproduce it with something
> > like:
> >
> > for i in $(seq 100); do timeout -s INT 2 rv mon rts -r printk;
> > done
> >
> > Running the monitor without stopping for the same amount of time
> > doesn't seem to show violations (until I terminate it).
>
> This one is strange, I cannot reproduce this issue. Did you run only
> that command, or did you have other things running as well?
>
> And does the problem still appears after disabling the fair deadline
> server and RT throttling?
Also here, I don't seem to reproduce it with both disabled..
Sorry for that, looks good for me then.
Reviewed-by: Gabriele Monaco <gmonaco@redhat.com>
Thanks,
Gabriele
next prev parent reply other threads:[~2025-08-08 7:30 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 [this message]
2025-08-15 13:48 ` Peter Zijlstra
2025-08-19 7:54 ` Nam Cao
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=c0ae826c9a3d828ac8ab2088495e671cd9384a86.camel@redhat.com \
--to=gmonaco@redhat.com \
--cc=bsegall@google.com \
--cc=dietmar.eggemann@arm.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=namcao@linutronix.de \
--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).