From: "Rafael J. Wysocki" <rjw@rjwysocki.net>
To: Mike Galbraith <efault@gmx.de>
Cc: lkml <linux-kernel@vger.kernel.org>,
Peter Zijlstra <peterz@infradead.org>,
Linux PM <linux-pm@vger.kernel.org>
Subject: Re: v5.8+ powersave governor breakage?
Date: Thu, 05 Nov 2020 15:31:19 +0100 [thread overview]
Message-ID: <2948497.iyA2Nh11HS@kreacher> (raw)
In-Reply-To: <59d0b9516ce9a553b1e526c6495ac302f1f73e0d.camel@gmx.de>
On Monday, November 2, 2020 7:18:41 AM CET Mike Galbraith wrote:
> On Sun, 2020-11-01 at 17:23 +0100, Mike Galbraith wrote:
> > Greetings,
> >
> > As you can see in the data below, my i4790 box used to default to the
> > powersave governor despite CONFIG_CPU_FREQ_DEFAULT_GOV_ONDEMAND=y, and
> > disallowed switching to ondemand.
>
> Ok, my HP lappy running master.today still defaults to powersave, with
> CONFIG_CPU_FREQ_DEFAULT_GOV_SCHEDUTIL=y, still disallows selecting
> ondemand as before, and powersave still works. IOW for lappy, it was
> business as usual, no change.
OK
> 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 (the modes are
described in detail in Documentation/admin-guide/pm/intel_pstate.rst) and the
default governor should be "schedutil".
Which should be slightly better from the functionality perspective.
> Box had schedutil forced upon it, but it
> seems perfectly fine with that performance wise.
Which is the expected outcome (sorry for the confusion).
Cheers!
next parent reply other threads:[~2020-11-05 14:31 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <580d12716f6363d7404805fd4bc50e2d5ab459b0.camel@gmx.de>
[not found] ` <59d0b9516ce9a553b1e526c6495ac302f1f73e0d.camel@gmx.de>
2020-11-05 14:31 ` Rafael J. Wysocki [this message]
2020-11-05 15:08 ` v5.8+ powersave governor breakage? Mike Galbraith
2020-11-05 18:02 ` Rafael J. Wysocki
2020-11-06 1:36 ` Mike Galbraith
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=2948497.iyA2Nh11HS@kreacher \
--to=rjw@rjwysocki.net \
--cc=efault@gmx.de \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=peterz@infradead.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox