linux-kernel - Re: Modifying isolcpus, nohz_full, and rcu

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite for Android: free password hash cracker in your pocket

[<prev] [next>] [day] [month] [year] [list]

Message-Id: <6EE460E1-BDC2-4AD5-B5A9-34AA0692BA05@arista.com>
Date:   Fri, 8 Dec 2023 09:21:11 -0500
From:   Gianfranco Dutka <gianfranco.dutka@...sta.com>
To:     Waiman Long <longman@...hat.com>
Cc:     Tejun Heo <tj@...nel.org>,
        Vincent Guittot <vincent.guittot@...aro.org>,
        linux-kernel@...r.kernel.org, vincent.guittot@...aro.com,
        Ingo Molnar <mingo@...hat.com>,
        Peter Zijlstra <peterz@...radead.org>,
        Juri Lelli <juri.lelli@...hat.com>,
        Dietmar Eggemann <dietmar.eggemann@....com>,
        Steven Rostedt <rostedt@...dmis.org>,
        Ben Segall <bsegall@...gle.com>, Mel Gorman <mgorman@...e.de>,
        Daniel Bristot de Oliveira <bristot@...hat.com>,
        Valentin Schneider <vschneid@...hat.com>,
        "Pandruvada, Srinivas" <srinivas.pandruvada@...el.com>,
        Frederic Weisbecker <frederic@...nel.org>
Subject: Re: Modifying isolcpus, nohz_full, and rcu_nocb kernel parameters at
 runtime


> The isolcpus, nohz_full and rcu_nocbs are boot-time kernel parameters. I am in the process of improving dynamic CPU isolation at runtime. Right now, we are able to do isolcpus=domain with the isolated cpuset partition functionality. Other aspects of CPU isolation are being looked at with the goal of reducing the gap of what one can do at boot time versus what can be done at run time. It will certain take time to reach that goal.
> 
> Cheers,
> Longman

Thank you Waiman for the response. It would seem that getting similar functionality through cgroups/cpusets is the only option at the moment. Is it completely out of the question to possibly patch the kernel to modify these parameters at runtime? Or would that entail a significant change that might not be so trivial to accomplish? For instance, the solution wouldn’t be as simple as patching the kernel to make these writeable and then calling the same functions which run at boot-time when these parameters are originally written? 

Thanks,
Gianfranco