From: Aaron Tomlin <atomlin@atomlin.com>
To: mingo@redhat.com, peterz@infradead.org, juri.lelli@redhat.com,
vincent.guittot@linaro.org, dietmar.eggemann@arm.com,
rostedt@goodmis.org, bsegall@google.com, mgorman@suse.de,
vschneid@redhat.com
Cc: sshegde@linux.ibm.com, neelx@suse.com, sean@ashe.io,
mproche@gmail.com, linux-kernel@vger.kernel.org
Subject: [PATCH 0/1] sched/deadline: Log Fair Server re-enablement
Date: Thu, 8 Jan 2026 22:19:58 -0500 [thread overview]
Message-ID: <20260109031959.2786873-1-atomlin@atomlin.com> (raw)
Hi Ingo, Peter, Juri, Vincent,
During a recent audit of the Fair Server related code, I observed that
whilst disabling the server via the debugfs interface emits a console
notification, re-enabling it remains silent. This patch rectifies that
asymmetry by ensuring a corresponding message is logged when runtime is
restored.
This omission was identified during the investigation and code review
following the recent discussion regarding
SCHED_FEAT(RT_SUPPRESS_FAIR_SERVER) [1]. Please note that this patch is
standalone and does not depend upon the aforementioned RFC patch.
[1]: https://lore.kernel.org/lkml/20260106034209.2703289-2-atomlin@atomlin.com/
Aaron Tomlin (1):
sched/deadline: Log Fair Server re-enablement for symmetry with
debugfs
kernel/sched/deadline.c | 6 ++++++
1 file changed, 6 insertions(+)
--
2.51.0
next reply other threads:[~2026-01-09 3:20 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-01-09 3:19 Aaron Tomlin [this message]
2026-01-09 3:19 ` [PATCH 1/1] sched/deadline: Log Fair Server re-enablement for symmetry with debugfs Aaron Tomlin
2026-01-09 6:17 ` K Prateek Nayak
2026-01-09 14:30 ` Aaron Tomlin
2026-01-12 5:14 ` K Prateek Nayak
2026-01-12 14:32 ` Aaron Tomlin
2026-01-12 18:48 ` Shrikanth Hegde
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=20260109031959.2786873-1-atomlin@atomlin.com \
--to=atomlin@atomlin.com \
--cc=bsegall@google.com \
--cc=dietmar.eggemann@arm.com \
--cc=juri.lelli@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mgorman@suse.de \
--cc=mingo@redhat.com \
--cc=mproche@gmail.com \
--cc=neelx@suse.com \
--cc=peterz@infradead.org \
--cc=rostedt@goodmis.org \
--cc=sean@ashe.io \
--cc=sshegde@linux.ibm.com \
--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
all inboxes | Powered by JetHome®