From: Clark Williams <clark.williams@gmail.com>
To: Sebastian Andrzej Siewior <bigeasy@linutronix.de>
Cc: Florian Bezdeka <florian.bezdeka@siemens.com>,
Steven Rostedt <rostedt@goodmis.org>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
driver-core@lists.linux.dev, linux-rt-devel@lists.linux.dev,
linux-rt-users@vger.kernel.org,
"Rafael J. Wysocki" <rafael@kernel.org>,
Arnd Bergmann <arnd@arndb.de>,
Clark Williams <williams@redhat.com>,
Danilo Krummrich <dakr@kernel.org>,
Peter Zijlstra <peterz@infradead.org>,
Clark Williams <clrkwllms@kernel.org>,
Thomas Gleixner <tglx@linutronix.de>,
Jan Kiszka <jan.kiszka@siemens.com>
Subject: Re: [RFC PATCH] sysfs: Add /sys/kernel/realtime entry
Date: Wed, 15 Jul 2026 12:18:21 -0500 [thread overview]
Message-ID: <alfA3ZaM1kmFaicG@demetrius> (raw)
In-Reply-To: <20260714110718.E5qV5-Hf@linutronix.de>
On Tue, Jul 14, 2026 at 01:07:18PM +0200, Sebastian Andrzej Siewior wrote:
> On 2026-07-10 18:01:20 [+0200], Florian Bezdeka wrote:
> > Depends on what you consider a valid update scenario. Updating from 6.1-
> > rt with sysfs available to something like 6.18 (no sysfs anymore) will
> > still break - as long as you do not (force) update userspace in
> > lockstep.
>
> v6.1-RT to v6-18 no-rt will not provide the file. Also will not provide
> ARM, PowerPC or 8250-nbcon support. So it is not just that single thing
> that you "lose" if you don't apply the RT patch. It is just what you
> notice because you don't use the other things.
>
> > I learned meanwhile that our detection moved to uname meanwhile, so this
> > is not a problem for us anymore.
>
> Okay. So you yelled loudly that you need it, now not anymore.
>
> So can we state that this it does not provide anything of value, is not
> considered needed and can be dropped?
>
> Clark, what is the status on your end?
>
I still carry it in v6.1-rt and v6.6-rt and don't really see a reason
not to. I don't believe it's a security risk since a write to
/sys/kernel/realtime gets ignored; it's just there to say that this is a
PREEMPT_RT kernel.
So, I'm ambivalent on the keep or drop question. I'll go ahead and clean
up what I'm carrying in v6.1-rt and v6.6-rt and if we decide to keep it
I'll send you the updated changes.
Clark
--
The United States Coast Guard
Ruining Natural Selection since 1790
next prev parent reply other threads:[~2026-07-15 17:18 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-07-09 14:31 [RFC PATCH] sysfs: Add /sys/kernel/realtime entry Sebastian Andrzej Siewior
2026-07-09 14:38 ` sashiko-bot
2026-07-09 14:46 ` Greg Kroah-Hartman
2026-07-09 15:22 ` Sebastian Andrzej Siewior
2026-07-09 16:02 ` Clark Williams
2026-07-10 7:02 ` Sebastian Andrzej Siewior
2026-07-10 7:05 ` Tomas Glozar
2026-07-10 7:23 ` Florian Bezdeka
2026-07-10 15:51 ` Steven Rostedt
2026-07-10 15:57 ` Sebastian Andrzej Siewior
2026-07-10 16:01 ` Florian Bezdeka
2026-07-10 16:12 ` Steven Rostedt
2026-07-14 11:07 ` Sebastian Andrzej Siewior
2026-07-15 17:18 ` Clark Williams [this message]
2026-07-10 16:05 ` Greg Kroah-Hartman
2026-07-10 16:14 ` Steven Rostedt
2026-07-09 15:54 ` Steven Rostedt
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=alfA3ZaM1kmFaicG@demetrius \
--to=clark.williams@gmail.com \
--cc=arnd@arndb.de \
--cc=bigeasy@linutronix.de \
--cc=clrkwllms@kernel.org \
--cc=dakr@kernel.org \
--cc=driver-core@lists.linux.dev \
--cc=florian.bezdeka@siemens.com \
--cc=gregkh@linuxfoundation.org \
--cc=jan.kiszka@siemens.com \
--cc=linux-rt-devel@lists.linux.dev \
--cc=linux-rt-users@vger.kernel.org \
--cc=peterz@infradead.org \
--cc=rafael@kernel.org \
--cc=rostedt@goodmis.org \
--cc=tglx@linutronix.de \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.