Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > linux.kernel > #1223866
| From | Viresh Kumar <viresh.kumar@linaro.org> |
|---|---|
| Newsgroups | linux.kernel |
| Subject | Re: [PATCH] cpufreq : powernv: Report Pmax throttling if capped below nominal frequency |
| Date | 2015-09-14 09:10 +0200 |
| Message-ID | <q8w3M-7rr-17@gated-at.bofh.it> (permalink) |
| References | <q8ulj-4Xm-1@gated-at.bofh.it> |
| Organization | linux.* mail to news gateway |
On 14-09-15, 10:47, Shilpasri G Bhat wrote:
> Log a 'critical' message if the max frequency is reduced below nominal
> frequency. We already log 'info' message if the max frequency is
> capped below turbo frequency. CPU should guarantee atleast nominal
> frequency, but not turbo frequency in all system configurations and
> environments. So report the pmax throttling with severity when Pmax is
> dipped below nominal frequency.
>
> Signed-off-by: Shilpasri G Bhat <shilpa.bhat@linux.vnet.ibm.com>
> ---
> drivers/cpufreq/powernv-cpufreq.c | 9 +++++++--
> 1 file changed, 7 insertions(+), 2 deletions(-)
>
> diff --git a/drivers/cpufreq/powernv-cpufreq.c b/drivers/cpufreq/powernv-cpufreq.c
> index 64994e1..2d9ed42 100644
> --- a/drivers/cpufreq/powernv-cpufreq.c
> +++ b/drivers/cpufreq/powernv-cpufreq.c
> @@ -327,8 +327,13 @@ static void powernv_cpufreq_throttle_check(void *data)
> if (chips[i].throttled)
> goto next;
> chips[i].throttled = true;
> - pr_info("CPU %d on Chip %u has Pmax reduced to %d\n", cpu,
> - chips[i].id, pmsr_pmax);
> + if (pmsr_pmax < powernv_pstate_info.nominal)
> + pr_crit("CPU %d on Chip %u has Pmax reduced to %d\n",
> + cpu, chips[i].id, pmsr_pmax);
> + else
> + pr_info("CPU %d on Chip %u has Pmax reduced to %d\n",
> + cpu, chips[i].id, pmsr_pmax);
I think the messages here can be improved a bit here to something
like:
pr_warn("CPU %d on Chip %u has Pmax reduced below nominal freq (%d < %d)\n",
cpu, chips[i].id, pmsr_pmax, powernv_pstate_info.nominal);
And similarly for the pr_info case as well.
--
viresh
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Back to linux.kernel | Previous | Next — Previous in thread | Next in thread | Find similar | Unroll thread
[PATCH] cpufreq : powernv: Report Pmax throttling if capped below nominal frequency Shilpasri G Bhat <shilpa.bhat@linux.vnet.ibm.com> - 2015-09-14 07:20 +0200
Re: [PATCH] cpufreq : powernv: Report Pmax throttling if capped below nominal frequency Viresh Kumar <viresh.kumar@linaro.org> - 2015-09-14 09:10 +0200
[PATCH v2] cpufreq : powernv: Report Pmax throttling if capped below nominal frequency Shilpasri G Bhat <shilpa.bhat@linux.vnet.ibm.com> - 2015-09-14 10:50 +0200
Re: [PATCH v2] cpufreq : powernv: Report Pmax throttling if capped below nominal frequency Viresh Kumar <viresh.kumar@linaro.org> - 2015-09-14 12:30 +0200
csiph-web