linux-kernel - Re: v5.8+ powersave governor breakage?

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] [day] [month] [year] [list]

Date:   Fri, 06 Nov 2020 02:36:05 +0100
From:   Mike Galbraith <efault@....de>
To:     "Rafael J. Wysocki" <rjw@...ysocki.net>
Cc:     lkml <linux-kernel@...r.kernel.org>,
        Peter Zijlstra <peterz@...radead.org>,
        Linux PM <linux-pm@...r.kernel.org>
Subject: Re: v5.8+ powersave governor breakage?

On Thu, 2020-11-05 at 19:02 +0100, Rafael J. Wysocki wrote:
> On Thursday, November 5, 2020 4:08:30 PM CET Mike Galbraith wrote:
> > On Thu, 2020-11-05 at 15:31 +0100, Rafael J. Wysocki wrote:
> > > On Monday, November 2, 2020 7:18:41 AM CET Mike Galbraith wrote:
> > >
> > > > Desktop box did, it gained a working ondemand, while its previously
> > > > working powersave went broke.
> > >
> > > Most likely that's because it was handled by intel_pstate in the "active" mode
> > > previously, while it is now handled by it in the "passive" mode...
> >
> > Perhaps the user interface should then nak switching to powersave as it
> > used to nak switching to ondemand?
>
> It cannot do that if the powersave governor is configured in.
>
> [Essentially, the problem is that the "powersave" thing advertised by
> intel_pstate in the "active" mode is not really the powersave governor,
> but that is a mistake made in the past and cannot be undone.  Sorry about
> that.]

Hohum.  A little unfortunate, but it probably only affects a few aging
boxen like mine, and I now know better that to ever again do that.