[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CAJZ5v0j2u7MrO82+ubx01kvyhDUKo11mfyofF-TAqdSLx_i3Ng@mail.gmail.com>
Date: Tue, 8 Dec 2020 18:13:56 +0100
From: "Rafael J. Wysocki" <rafael@...nel.org>
To: Giovanni Gherdovich <ggherdovich@...e.com>
Cc: "Rafael J. Wysocki" <rjw@...ysocki.net>,
Linux PM <linux-pm@...r.kernel.org>,
LKML <linux-kernel@...r.kernel.org>,
Viresh Kumar <viresh.kumar@...aro.org>,
Srinivas Pandruvada <srinivas.pandruvada@...ux.intel.com>,
Peter Zijlstra <peterz@...radead.org>,
Doug Smythies <dsmythies@...us.net>
Subject: Re: [PATCH v1 0/4] cpufreq: Allow drivers to receive more information
from the governor
On Tue, Dec 8, 2020 at 5:31 PM Giovanni Gherdovich <ggherdovich@...e.com> wrote:
>
> On Mon, 2020-12-07 at 17:25 +0100, Rafael J. Wysocki wrote:
> > Hi,
> >
> > This is based on the RFC posted a few days ago:
> >
> > https://lore.kernel.org/linux-pm/1817571.2o5Kk4Ohv2@kreacher/
> >
> > The majority of the original cover letter still applies, so let me quote it
> > here:
> > [...]
>
> Hello Rafael,
>
> I'd like to test this patch, as I have concerns on how it performs against the
> current intel_pstate passive + HWP + schedutil (which leaves HWP.REQ.DESIRED
> untouched).
The performance will be worse in some cases, which is to be expected,
but the point here is to counter the problem that in some cases the
frequency is excessive now.
> I'll get results within a week. Do you mind holding back the merge until then?
Sure, the series is still under review.
Powered by blists - more mailing lists