From: Peter Zijlstra <peterz@infradead.org>
To: Joseph Salisbury <joseph.salisbury@canonical.com>
Cc: linux-rt-users@vger.kernel.org, williams@redhat.com,
bigeasy@linutronix.de, valentin.schneider@arm.com,
linux-kernel@vger.kernel.org
Subject: Re: [RFC} Commit 8a99b6833c88 Moves Important Real-time Settings To DebugFS
Date: Thu, 18 Aug 2022 22:31:19 +0200 [thread overview]
Message-ID: <Yv6hl3D2TRL6jzrL@worktop.programming.kicks-ass.net> (raw)
In-Reply-To: <9e6a7216-9cb9-cba4-f150-1a0eaf56353c@canonical.com>
On Thu, Aug 18, 2022 at 03:53:28PM -0400, Joseph Salisbury wrote:
> Hello,
>
> Some Ubuntu users are using the tuned package with a 5.15.x based real-time
> kernel. Tuned adjusts various sysctl options based on a specified profile.
> This userspace package has stopped working > 5.13 due to the following
> commit:
>
> 8a99b6833c88 "(sched: Move SCHED_DEBUG sysctl to debugfs)"
>
> This commit moved some important real-time sysctl knobs to debugfs in
> 5.13-rc1. It also appears some of the sysctl options were not moved,
> sched_min_granularity_ns, for example.
>
> I was hoping to get some feedback on how to approach this. Would upstream
> real-time consider accepting a patch to the 5.15 real-time patch set that
> reverts this commit? Or a new patch that adds the sysctl settings back?
> Any other ideas or feedback would be appreciated!
None of those knobs were available when SCHED_DEBUG=n, so relying on
them is your error to begin with.
Secondly, real-time? Which if those values affects anything in
SCHED_FIFO/RR/DEADLINE ?
next prev parent reply other threads:[~2022-08-18 20:31 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-08-18 19:53 [RFC} Commit 8a99b6833c88 Moves Important Real-time Settings To DebugFS Joseph Salisbury
2022-08-18 20:31 ` Peter Zijlstra [this message]
2022-08-19 1:38 ` Joseph Salisbury
2022-08-19 14:28 ` Joseph Salisbury
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=Yv6hl3D2TRL6jzrL@worktop.programming.kicks-ass.net \
--to=peterz@infradead.org \
--cc=bigeasy@linutronix.de \
--cc=joseph.salisbury@canonical.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-rt-users@vger.kernel.org \
--cc=valentin.schneider@arm.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