From: John Ogness <john.ogness@linutronix.de>
To: Sebastian Andrzej Siewior <bigeasy@linutronix.de>,
Steven Rostedt <rostedt@goodmis.org>
Cc: "Ahmed S. Darwish" <darwi@linutronix.de>,
Jonathan Corbet <corbet@lwn.net>,
Clark Williams <clrkwllms@kernel.org>,
linux-rt-devel@lists.linux.dev,
Matthew Wilcox <willy@infradead.org>,
Derek Barbosa <debarbos@redhat.com>,
linux-doc@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v4 1/1] Documentation: real-time: Add kernel configuration guide
Date: Tue, 21 Jul 2026 17:58:00 +0206 [thread overview]
Message-ID: <87wluo49y7.fsf@jogness.linutronix.de> (raw)
In-Reply-To: <20260721152114.wTED4bR5@linutronix.de>
On 2026-07-21, Sebastian Andrzej Siewior <bigeasy@linutronix.de> wrote:
> On 2026-07-21 10:48:06 [-0400], Steven Rostedt wrote:
>> On Tue, 21 Jul 2026 16:36:06 +0200
>> Sebastian Andrzej Siewior <bigeasy@linutronix.de> wrote:
>>
>>>> Unfortunately, debugfs is needed to configure the fair deadline server:
>>>>
>>>> /sys/kernel/debug/sched/fair_server/cpu*/runtime
>>>
>>> So drop the reference to it. It is not "bad" to have it enabled. It is
>>
>> I believe that some distros feel that it is bad to enable because there's
>> no real auditing of its interface. Although, it is now only accessible by
>> root.
>
> Yeah. Either way, there shouldn't be anything real-time specific that
> requires the user have it enabled or disabled.
The fair deadline server is certainly real-time specific. It is the
new/additional RT throttling mechanism. Generally speaking, RT systems
will want to disable it or at least reduce the 50ms default.
This document is not about runtime settings, but if debugfs is not
enabled, the user will have no way to configure the fair deadline server
at runtime.
I am OK if it is completely dropped from this document. But if there are
distros that think it is bad, it might be worth mentioning that this
config is important (if not critical) for real-time systems.
John
next prev parent reply other threads:[~2026-07-21 15:52 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-07-16 19:57 [PATCH v4 0/1] Documentation: Add real-time kernel configuration guide Ahmed S. Darwish
2026-07-16 19:57 ` [PATCH v4 1/1] Documentation: real-time: Add " Ahmed S. Darwish
2026-07-21 13:02 ` Sebastian Andrzej Siewior
2026-07-21 14:34 ` John Ogness
2026-07-21 14:36 ` Sebastian Andrzej Siewior
2026-07-21 14:48 ` Steven Rostedt
2026-07-21 15:21 ` Sebastian Andrzej Siewior
2026-07-21 15:52 ` John Ogness [this message]
2026-07-21 18:08 ` Sebastian Andrzej Siewior
2026-07-22 19:40 ` Ahmed S. Darwish
2026-07-21 13:05 ` Sebastian Andrzej Siewior
-- strict thread matches above, loose matches on Subject: below --
2026-04-14 17:41 [PATCH v2 0/1] Documentation: Add real-time " Ahmed S. Darwish
2026-04-14 17:41 ` [PATCH v2 1/1] Documentation: real-time: Add " Ahmed S. Darwish
2026-04-14 17:54 ` [PATCH v3 " Ahmed S. Darwish
2026-04-14 18:12 ` [PATCH v4 " Ahmed S. Darwish
2026-05-13 20:42 ` Ahmed S. Darwish
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=87wluo49y7.fsf@jogness.linutronix.de \
--to=john.ogness@linutronix.de \
--cc=bigeasy@linutronix.de \
--cc=clrkwllms@kernel.org \
--cc=corbet@lwn.net \
--cc=darwi@linutronix.de \
--cc=debarbos@redhat.com \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-rt-devel@lists.linux.dev \
--cc=rostedt@goodmis.org \
--cc=willy@infradead.org \
/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