linux-kernel - Re: [PATCH] sched/core: Update kernel boot parameters for LAZY preempt.

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: Windows password security audit tool. GUI, reports in PDF.

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

Message-ID: <558763e0-5668-4bce-be93-70fc11050ab8@linux.ibm.com>
Date: Mon, 25 Nov 2024 18:30:24 +0530
From: Shrikanth Hegde <sshegde@...ux.ibm.com>
To: Sebastian Andrzej Siewior <bigeasy@...utronix.de>
Cc: tglx@...utronix.de, Ingo Molnar <mingo@...hat.com>,
        Juri Lelli <juri.lelli@...hat.com>,
        Vincent Guittot <vincent.guittot@...aro.org>,
        Dietmar Eggemann <dietmar.eggemann@....com>,
        Steven Rostedt <rostedt@...dmis.org>, Ben Segall <bsegall@...gle.com>,
        Mel Gorman <mgorman@...e.de>, Valentin Schneider <vschneid@...hat.com>,
        Peter Zijlstra <peterz@...radead.org>, linux-kernel@...r.kernel.org
Subject: Re: [PATCH] sched/core: Update kernel boot parameters for LAZY
 preempt.



On 11/22/24 23:05, Sebastian Andrzej Siewior wrote:
> Update the documentation for the `preempt=' parameter which now also
> accepts `lazy'.
> 
> Fixes: 7c70cb94d29cd ("sched: Add Lazy preemption model")
> Reported-by: Shrikanth Hegde <sshegde@...ux.ibm.com>
> Signed-off-by: Sebastian Andrzej Siewior <bigeasy@...utronix.de>
> ---
>   Documentation/admin-guide/kernel-parameters.txt | 5 +++++
>   1 file changed, 5 insertions(+)
> 
> diff --git a/Documentation/admin-guide/kernel-parameters.txt b/Documentation/admin-guide/kernel-parameters.txt
> index 9cd9cd06538bf..23d9bd5ea7e47 100644
> --- a/Documentation/admin-guide/kernel-parameters.txt
> +++ b/Documentation/admin-guide/kernel-parameters.txt
> @@ -4818,6 +4818,11 @@
>   			       can be preempted anytime.  Tasks will also yield
>   			       contended spinlocks (if the critical section isn't
>   			       explicitly preempt disabled beyond the lock itself).
> +			lazy - Scheduler controlled. Similar to full but instead
> +			       of preempting the task immediately, the task gets
> +			       one HZ tick time to yield itself before the
> +			       preemption will be forced. One preemption is when the
> +			       task returns to user space.
>   
>   	print-fatal-signals=
>   			[KNL] debug: print fatal signals

Reviewed-by: Shrikanth Hegde <sshegde@...ux.ibm.com>