linux-kernel - Re: [RFC PATCH] kernel: allow to configure PREEMPT_NONE, 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]

Date:   Fri, 9 Oct 2020 12:14:31 +0200
From:   Peter Zijlstra <peterz@...radead.org>
To:     Michal Hocko <mhocko@...e.com>
Cc:     Thomas Gleixner <tglx@...utronix.de>,
        Frederic Weisbecker <fweisbecker@...e.de>,
        LKML <linux-kernel@...r.kernel.org>,
        Mel Gorman <mgorman@...e.de>, Ingo Molnar <mingo@...hat.com>
Subject: Re: [RFC PATCH] kernel: allow to configure PREEMPT_NONE,
 PREEMPT_VOLUNTARY on kernel command line

On Fri, Oct 09, 2020 at 12:10:44PM +0200, Michal Hocko wrote:
> On Fri 09-10-20 11:42:45, Peter Zijlstra wrote:
> > On Fri, Oct 09, 2020 at 11:12:18AM +0200, Michal Hocko wrote:
> > > Is there any additional feedback? Should I split up the patch and repost
> > > for inclusion?
> > 
> > Maybe remove PREEMPT_NONE after that?  Since that's then equivalent to
> > building with VOLUNTARY and booting with preempt=none.
> 
> So do you mean that I should post an additional patch which does this on
> top? With a justification that there is one option less to chose from?

Exactly!