From: John Ogness <john.ogness@linutronix.de>
To: Sebastian Andrzej Siewior <bigeasy@linutronix.de>,
"Ahmed S. Darwish" <darwi@linutronix.de>
Cc: Jonathan Corbet <corbet@lwn.net>,
Clark Williams <clrkwllms@kernel.org>,
Steven Rostedt <rostedt@goodmis.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 16:40:10 +0206 [thread overview]
Message-ID: <874ihs5s4d.fsf@jogness.linutronix.de> (raw)
In-Reply-To: <20260721130248.ndwsFtHE@linutronix.de>
On 2026-07-21, Sebastian Andrzej Siewior <bigeasy@linutronix.de> wrote:
>> +``CONFIG_DEBUG_FS``
>> +^^^^^^^^^^^^^^^^^^^
>> +
>> +This is safe to include in real-time kernels, *provided that debugfs is
>> +not accessed during production runtime*.
>
> It is safe to have as long as you don't use it.
>
> I would drop it. That filesystem is not dangerous on its own. It depends
> on the options you change and how this affect the system.
> We used to have it always enabled because you needed it for tracing.
> This is no longer the case as it has its own tracefs which has its own
> live outside of debugfs. So I don't think it is needed to mention it.
Unfortunately, debugfs is needed to configure the fair deadline server:
/sys/kernel/debug/sched/fair_server/cpu*/runtime
John Ogness
next prev parent reply other threads:[~2026-07-21 14:34 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 [this message]
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
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=874ihs5s4d.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