From: "Zhang, Rui" <rui.zhang@intel.com>
To: "linux-pm@vger.kernel.org" <linux-pm@vger.kernel.org>,
"rjw@rjwysocki.net" <rjw@rjwysocki.net>
Cc: "srinivas.pandruvada@linux.intel.com"
<srinivas.pandruvada@linux.intel.com>,
"viresh.kumar@linaro.org" <viresh.kumar@linaro.org>,
"Wang, Quanxian" <quanxian.wang@intel.com>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"daniel.lezcano@linaro.org" <daniel.lezcano@linaro.org>,
"linux-acpi@vger.kernel.org" <linux-acpi@vger.kernel.org>
Subject: Re: [PATCH v1 4/4] ACPI: processor: thermal: Update CPU cooling devices on cpufreq policy changes
Date: Tue, 7 Mar 2023 16:43:38 +0000 [thread overview]
Message-ID: <f8c87ea7a1fd8f763ff4ccf3c43706ae43f81ede.camel@intel.com> (raw)
In-Reply-To: <1936685.PYKUYFuaPT@kreacher>
On Fri, 2023-03-03 at 20:23 +0100, Rafael J. Wysocki wrote:
> From: Rafael J. Wysocki <rafael.j.wysocki@intel.com>
>
> When a cpufreq policy appears or goes away, the CPU cooling devices
> for
> the CPUs covered by that policy need to be updated so that the new
> processor_get_max_state() value is stored as max_state and the
> statistics in sysfs are rearranged for each of them.
>
> Do that accordingly in acpi_thermal_cpufreq_init() and
> acpi_thermal_cpufreq_exit().
>
> Fixes: a365105c685c("thermal: sysfs: Reuse cdev->max_state")
> Reported-by: Wang, Quanxian <quanxian.wang@intel.com>
> Link:
> https://lore.kernel.org/linux-pm/53ec1f06f61c984100868926f282647e57ecfb2d.camel@intel.com/
> Signed-off-by: Rafael J. Wysocki <rafael.j.wysocki@intel.com>
> ---
> drivers/acpi/processor_thermal.c | 16 +++++++++++++---
> 1 file changed, 13 insertions(+), 3 deletions(-)
>
> Index: linux-pm/drivers/acpi/processor_thermal.c
> ===================================================================
> --- linux-pm.orig/drivers/acpi/processor_thermal.c
> +++ linux-pm/drivers/acpi/processor_thermal.c
> @@ -140,9 +140,14 @@ void acpi_thermal_cpufreq_init(struct cp
> ret = freq_qos_add_request(&policy->constraints,
> &pr->thermal_req,
> FREQ_QOS_MAX, INT_MAX);
> - if (ret < 0)
> + if (ret < 0) {
> pr_err("Failed to add freq constraint for CPU%d
> (%d)\n",
> cpu, ret);
> + continue;
> + }
> +
> + if (!IS_ERR(pr->cdev))
> + thermal_cooling_device_update(pr->cdev);
Although thermal_cooling_device_update() handles "pr->cdev == NULL"
case, I think it is better to use !IS_ERR_OR_NULL() here.
thanks,
rui
> }
> }
>
> @@ -153,8 +158,13 @@ void acpi_thermal_cpufreq_exit(struct cp
> for_each_cpu(cpu, policy->related_cpus) {
> struct acpi_processor *pr = per_cpu(processors, cpu);
>
> - if (pr)
> - freq_qos_remove_request(&pr->thermal_req);
> + if (!pr)
> + continue;
> +
> + freq_qos_remove_request(&pr->thermal_req);
> +
> + if (!IS_ERR(pr->cdev))
> + thermal_cooling_device_update(pr->cdev);
> }
> }
> #else /* ! CONFIG_CPU_FREQ */
>
>
>
next prev parent reply other threads:[~2023-03-07 16:47 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-03 19:18 [PATCH v1 0/4] thermal: core/ACPI: Fix processor cooling device regression Rafael J. Wysocki
2023-03-03 19:19 ` [PATCH v1 1/4] ACPI: processor: Reorder acpi_processor_driver_init() Rafael J. Wysocki
2023-03-07 16:51 ` Zhang, Rui
2023-03-10 18:31 ` Rafael J. Wysocki
2023-03-12 16:08 ` Zhang, Rui
2023-03-13 13:48 ` Rafael J. Wysocki
2023-03-13 14:54 ` Zhang, Rui
2023-03-13 14:58 ` Rafael J. Wysocki
2023-03-03 19:21 ` [PATCH v1 2/4] thermal: core: Introduce thermal_cooling_device_present() Rafael J. Wysocki
2023-03-03 19:23 ` [PATCH v1 3/4] thermal: core: Introduce thermal_cooling_device_update() Rafael J. Wysocki
2023-03-07 16:40 ` Zhang, Rui
2023-03-10 18:25 ` Rafael J. Wysocki
2023-03-27 20:57 ` Imre Deak
2023-03-28 15:35 ` Rafael J. Wysocki
2023-03-03 19:23 ` [PATCH v1 4/4] ACPI: processor: thermal: Update CPU cooling devices on cpufreq policy changes Rafael J. Wysocki
2023-03-07 16:43 ` Zhang, Rui [this message]
2023-03-10 18:29 ` Rafael J. Wysocki
2023-03-12 14:44 ` Zhang, Rui
2023-03-13 13:50 ` 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=f8c87ea7a1fd8f763ff4ccf3c43706ae43f81ede.camel@intel.com \
--to=rui.zhang@intel.com \
--cc=daniel.lezcano@linaro.org \
--cc=linux-acpi@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=quanxian.wang@intel.com \
--cc=rjw@rjwysocki.net \
--cc=srinivas.pandruvada@linux.intel.com \
--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