Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 2620:137:e000::1:20 as permitted sender) client-ip=2620:137:e000::1:20;
Message-ID: <9e6a7216-9cb9-cba4-f150-1a0eaf56353c@canonical.com>
Date:   Thu, 18 Aug 2022 15:53:28 -0400
MIME-Version: 1.0
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:91.0) Gecko/20100101
 Thunderbird/91.11.0
Content-Language: en-US
To:     linux-rt-users@vger.kernel.org, williams@redhat.com,
        bigeasy@linutronix.de
Cc:     peterz@infradead.org, valentin.schneider@arm.com,
        linux-kernel@vger.kernel.org
From:   Joseph Salisbury <joseph.salisbury@canonical.com>
Subject: [RFC} Commit 8a99b6833c88 Moves Important Real-time Settings To
 DebugFS
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 8bit
Precedence: bulk

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!


Thanks in advance,

Joe