From: Gabriele Monaco <gmonaco@redhat.com>
To: Juri Lelli <juri.lelli@redhat.com>
Cc: linux-kernel@vger.kernel.org,
Steven Rostedt <rostedt@goodmis.org>,
Nam Cao <namcao@linutronix.de>, Juri Lelli <jlelli@redhat.com>,
Jonathan Corbet <corbet@lwn.net>,
Masami Hiramatsu <mhiramat@kernel.org>,
linux-trace-kernel@vger.kernel.org, linux-doc@vger.kernel.org,
Peter Zijlstra <peterz@infradead.org>,
Tomas Glozar <tglozar@redhat.com>,
Clark Williams <williams@redhat.com>,
John Kacur <jkacur@redhat.com>
Subject: Re: [PATCH v4 14/15] rv: Add deadline monitors
Date: Mon, 19 Jan 2026 12:35:10 +0100 [thread overview]
Message-ID: <5df16facba05b84857ad09cee12df0c19a551285.camel@redhat.com> (raw)
In-Reply-To: <aW4PvcDxBJnDLJFq@jlelli-thinkpadt14gen4.remote.csb>
On Mon, 2026-01-19 at 12:04 +0100, Juri Lelli wrote:
> Why use pi_of() in above cases?
>
> For the first, in case the macro is called while the task is actually
> boosted, we then might continue to use that even after such task gets
> deboosted?
Mmh, yeah thinking about it again it doesn't make much sense considering we are
not tracking when a task is deboosted, unless that always corresponds to a
replenish. Thought that doesn't seem the case..
> For the second, current PI implementation (even if admittedly not ideal)
> uses donor's static dl_runtime to replenish boosted task runtime, but
> then accounting is performed again the task dynamic runtime, not the
> donor's (this all will hopefully change soon with proxy exec..)?
At this point I should probably just ignore the pi_of() right?
I'm assuming the original (non-boosted) parameters are more conservative anyway
so it shouldn't be a problem for the model.
Thanks,
Gabriele
next prev parent reply other threads:[~2026-01-19 11:35 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-01-16 12:38 [PATCH v4 00/15] rv: Add Hybrid Automata monitor type, per-object and deadline monitors Gabriele Monaco
2026-01-16 12:38 ` [PATCH v4 01/15] rv: Unify DA event handling functions across monitor types Gabriele Monaco
2026-01-16 12:38 ` [PATCH v4 02/15] rv: Add Hybrid Automata monitor type Gabriele Monaco
2026-01-16 12:38 ` [PATCH v4 03/15] verification/rvgen: Allow spaces in and events strings Gabriele Monaco
2026-01-16 12:39 ` [PATCH v4 04/15] verification/rvgen: Add support for Hybrid Automata Gabriele Monaco
2026-01-16 12:39 ` [PATCH v4 05/15] Documentation/rv: Add documentation about hybrid automata Gabriele Monaco
2026-01-16 12:39 ` [PATCH v4 06/15] rv: Add sample hybrid monitors stall Gabriele Monaco
2026-01-16 12:39 ` [PATCH v4 07/15] rv: Convert the opid monitor to a hybrid automaton Gabriele Monaco
2026-01-16 12:39 ` [PATCH v4 08/15] sched: Export hidden tracepoints to modules Gabriele Monaco
2026-01-16 14:00 ` Phil Auld
2026-01-16 14:24 ` Gabriele Monaco
2026-01-16 12:39 ` [PATCH v4 09/15] sched: Add deadline tracepoints Gabriele Monaco
2026-01-19 10:20 ` Juri Lelli
2026-01-16 12:39 ` [PATCH v4 10/15] sched: Add task enqueue/dequeue trace points Gabriele Monaco
2026-01-16 14:50 ` K Prateek Nayak
2026-01-16 15:01 ` Gabriele Monaco
2026-01-16 12:39 ` [PATCH v4 11/15] rv: Add support for per-object monitors in DA/HA Gabriele Monaco
2026-01-16 12:39 ` [PATCH v4 12/15] verification/rvgen: Add support for per-obj monitors Gabriele Monaco
2026-01-16 12:39 ` [PATCH v4 13/15] sched/deadline: Move some utility functions to deadline.h Gabriele Monaco
2026-01-19 10:08 ` Juri Lelli
2026-01-16 12:39 ` [PATCH v4 14/15] rv: Add deadline monitors Gabriele Monaco
2026-01-19 11:04 ` Juri Lelli
2026-01-19 11:35 ` Gabriele Monaco [this message]
2026-01-19 13:16 ` Juri Lelli
2026-01-16 12:39 ` [PATCH v4 15/15] rv: Add dl_server specific monitors Gabriele Monaco
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=5df16facba05b84857ad09cee12df0c19a551285.camel@redhat.com \
--to=gmonaco@redhat.com \
--cc=corbet@lwn.net \
--cc=jkacur@redhat.com \
--cc=jlelli@redhat.com \
--cc=juri.lelli@redhat.com \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-trace-kernel@vger.kernel.org \
--cc=mhiramat@kernel.org \
--cc=namcao@linutronix.de \
--cc=peterz@infradead.org \
--cc=rostedt@goodmis.org \
--cc=tglozar@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