From: Peter Zijlstra <peterz@infradead.org>
To: Viresh Kumar <viresh.kumar@linaro.org>
Cc: Rafael Wysocki <rjw@rjwysocki.net>,
Qian Cai <quic_qiancai@quicinc.com>,
Sudeep Holla <sudeep.holla@arm.com>,
Ingo Molnar <mingo@redhat.com>,
Juri Lelli <juri.lelli@redhat.com>,
Vincent Guittot <vincent.guittot@linaro.org>,
Dietmar Eggemann <dietmar.eggemann@arm.com>,
Steven Rostedt <rostedt@goodmis.org>,
Ben Segall <bsegall@google.com>, Mel Gorman <mgorman@suse.de>,
Daniel Bristot de Oliveira <bristot@redhat.com>,
Ionela Voinescu <ionela.voinescu@arm.com>,
linux-pm@vger.kernel.org, "Rafael J. Wysocki" <rafael@kernel.org>,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH V2] Revert "cpufreq: CPPC: Add support for frequency invariance"
Date: Fri, 11 Jun 2021 09:37:27 +0200 [thread overview]
Message-ID: <YMMSt65aj0KKHy1A@hirez.programming.kicks-ass.net> (raw)
In-Reply-To: <a71c48fb0150f505680da68a82b4e4fca9a18439.1623381430.git.viresh.kumar@linaro.org>
On Fri, Jun 11, 2021 at 08:48:02AM +0530, Viresh Kumar wrote:
> This reverts commit 4c38f2df71c8e33c0b64865992d693f5022eeaad.
>
> There are few races in the frequency invariance support for CPPC driver,
> namely the driver doesn't stop the kthread_work and irq_work on policy
> exit during suspend/resume or CPU hotplug.
>
> A proper fix won't be possible for the 5.13-rc, as it requires a lot of
> changes. Lets revert the patch instead for now.
>
> Fixes: 4c38f2df71c8 ("cpufreq: CPPC: Add support for frequency invariance")
> Reported-by: Qian Cai <quic_qiancai@quicinc.com>
> Signed-off-by: Viresh Kumar <viresh.kumar@linaro.org>
> ---
> V2: Revert the original patch instead of marking it broken.
>
> drivers/cpufreq/Kconfig.arm | 10 --
> drivers/cpufreq/cppc_cpufreq.c | 245 ++-------------------------------
> include/linux/arch_topology.h | 1 -
> kernel/sched/core.c | 1 -
> 4 files changed, 12 insertions(+), 245 deletions(-)
>
> diff --git a/drivers/cpufreq/Kconfig.arm b/drivers/cpufreq/Kconfig.arm
> index a5c5f70acfc9..e65e0a43be64 100644
> --- a/drivers/cpufreq/Kconfig.arm
> +++ b/drivers/cpufreq/Kconfig.arm
> @@ -19,16 +19,6 @@ config ACPI_CPPC_CPUFREQ
>
> If in doubt, say N.
>
> -config ACPI_CPPC_CPUFREQ_FIE
> - bool "Frequency Invariance support for CPPC cpufreq driver"
> - depends on ACPI_CPPC_CPUFREQ && GENERIC_ARCH_TOPOLOGY
> - default y
> - help
> - This extends frequency invariance support in the CPPC cpufreq driver,
> - by using CPPC delivered and reference performance counters.
> -
> - If in doubt, say N.
> -
Alternatively: "depends on BROKEN" ?
next prev parent reply other threads:[~2021-06-11 7:38 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-06-11 3:18 [PATCH V2] Revert "cpufreq: CPPC: Add support for frequency invariance" Viresh Kumar
2021-06-11 7:37 ` Peter Zijlstra [this message]
2021-06-11 7:40 ` Viresh Kumar
2021-06-11 10:54 ` Rafael J. Wysocki
2021-06-14 13:56 ` Rafael J. Wysocki
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=YMMSt65aj0KKHy1A@hirez.programming.kicks-ass.net \
--to=peterz@infradead.org \
--cc=bristot@redhat.com \
--cc=bsegall@google.com \
--cc=dietmar.eggemann@arm.com \
--cc=ionela.voinescu@arm.com \
--cc=juri.lelli@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=mgorman@suse.de \
--cc=mingo@redhat.com \
--cc=quic_qiancai@quicinc.com \
--cc=rafael@kernel.org \
--cc=rjw@rjwysocki.net \
--cc=rostedt@goodmis.org \
--cc=sudeep.holla@arm.com \
--cc=vincent.guittot@linaro.org \
--cc=viresh.kumar@linaro.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