mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Pierre Gondois <pierre.gondois@arm.com>
To: liwei <liwei728@huawei.com>
Cc: linux-acpi@vger.kernel.org, rafael@kernel.org,
	linux-kernel@vger.kernel.org, lenb@kernel.org,
	liwei391@huawei.com, viresh.kumar@linaro.org
Subject: Re: [PATCH] cpufreq/cppc: fix perf_to_khz conversion exception
Date: Fri, 3 May 2024 09:42:02 +0200	[thread overview]
Message-ID: <0f8ccc3d-46ca-4632-9ecf-5da596ad5a1a@arm.com> (raw)
In-Reply-To: <20240430101227.2133288-1-liwei728@huawei.com>

Hello Liwei,

Thanks for the fix. I think there might be a similar issue
in cppc_khz_to_perf(),

Regards,
Pierre

On 4/30/24 12:12, liwei wrote:
> When the nominal_freq recorded by the kernel is equal to lowest_freq and
> the frequency reduction operation is triggered externally, there is a
> conversion logic error in cppc_perf_to_khz(), causing the kernel to be
> unable to feedback the true frequency.
> 
> Fix this by adding the branch processing logic when nominal_freq is equal
> to lowest_freq.
> 
> Fixes: ec1c7ad47664 ("cpufreq: CPPC: Fix performance/frequency conversion")
> Signed-off-by: liwei <liwei728@huawei.com>
> ---
>   drivers/acpi/cppc_acpi.c | 10 ++++++++--
>   1 file changed, 8 insertions(+), 2 deletions(-)
> 
> diff --git a/drivers/acpi/cppc_acpi.c b/drivers/acpi/cppc_acpi.c
> index a40b6f3946ef..92aac6974e0e 100644
> --- a/drivers/acpi/cppc_acpi.c
> +++ b/drivers/acpi/cppc_acpi.c
> @@ -1869,9 +1869,15 @@ unsigned int cppc_perf_to_khz(struct cppc_perf_caps *caps, unsigned int perf)
>   	u64 mul, div;
>   
>   	if (caps->lowest_freq && caps->nominal_freq) {
> -		mul = caps->nominal_freq - caps->lowest_freq;
> +		/* Avoid the special case when nominal_freq is equal to lowest_freq */
> +		if (caps->lowest_freq == caps->nominal_freq) {
> +			mul = caps->nominal_freq;
> +			div = caps->nominal_perf;
> +		} else {
> +			mul = caps->nominal_freq - caps->lowest_freq;
> +			div = caps->nominal_perf - caps->lowest_perf;
> +		}
>   		mul *= KHZ_PER_MHZ;
> -		div = caps->nominal_perf - caps->lowest_perf;
>   		offset = caps->nominal_freq * KHZ_PER_MHZ -
>   			 div64_u64(caps->nominal_perf * mul, div);
>   	} else {

  reply	other threads:[~2024-05-03  7:42 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-04-30 10:12 liwei
2024-05-03  7:42 ` Pierre Gondois [this message]
2024-05-06  2:55   ` liwei (JK)

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=0f8ccc3d-46ca-4632-9ecf-5da596ad5a1a@arm.com \
    --to=pierre.gondois@arm.com \
    --cc=lenb@kernel.org \
    --cc=linux-acpi@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=liwei391@huawei.com \
    --cc=liwei728@huawei.com \
    --cc=rafael@kernel.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

all inboxes | Powered by JetHome®