From: Viresh Kumar <viresh.kumar@linaro.org>
To: Shilpasri G Bhat <shilpa.bhat@linux.vnet.ibm.com>
Cc: rjw@rjwysocki.net, stewart@linux.vnet.ibm.com,
linuxppc-dev@ozlabs.org, linux-kernel@vger.kernel.org,
linux-pm@vger.kernel.org
Subject: Re: [PATCH] cpufreq: powernv: Increase the verbosity of OCC console messages
Date: Thu, 27 Aug 2015 17:59:40 +0530 [thread overview]
Message-ID: <20150827122940.GW8784@linux> (raw)
In-Reply-To: <1440666704-10666-1-git-send-email-shilpa.bhat@linux.vnet.ibm.com>
On 27-08-15, 14:41, Shilpasri G Bhat wrote:
> Modify the OCC reset/load/active event message to make it clearer for
> the user to understand the event and effect of the event.
>
> Suggested-by: Stewart Smith <stewart@linux.vnet.ibm.com>
> Signed-off-by: Shilpasri G Bhat <shilpa.bhat@linux.vnet.ibm.com>
> ---
> This patch is based on top of linux-next/master
>
> drivers/cpufreq/powernv-cpufreq.c | 9 +++++----
> 1 file changed, 5 insertions(+), 4 deletions(-)
>
> diff --git a/drivers/cpufreq/powernv-cpufreq.c b/drivers/cpufreq/powernv-cpufreq.c
> index 546e056..64994e1 100644
> --- a/drivers/cpufreq/powernv-cpufreq.c
> +++ b/drivers/cpufreq/powernv-cpufreq.c
> @@ -465,6 +465,7 @@ static int powernv_cpufreq_occ_msg(struct notifier_block *nb,
> switch (omsg.type) {
> case OCC_RESET:
> occ_reset = true;
> + pr_info("OCC (On Chip Controller - enforces hard thermal/power limits) Resetting\n");
> /*
> * powernv_cpufreq_throttle_check() is called in
> * target() callback which can detect the throttle state
> @@ -474,12 +475,12 @@ static int powernv_cpufreq_occ_msg(struct notifier_block *nb,
> */
> if (!throttled) {
> throttled = true;
> - pr_crit("CPU Frequency is throttled\n");
> + pr_crit("CPU frequency is throttled for duration\n");
> }
> - pr_info("OCC: Reset\n");
> +
> break;
> case OCC_LOAD:
> - pr_info("OCC: Loaded\n");
> + pr_info("OCC Loading, CPU frequency is throttled until OCC is started\n");
> break;
> case OCC_THROTTLE:
> omsg.chip = be64_to_cpu(msg->params[1]);
> @@ -488,7 +489,7 @@ static int powernv_cpufreq_occ_msg(struct notifier_block *nb,
> if (occ_reset) {
> occ_reset = false;
> throttled = false;
> - pr_info("OCC: Active\n");
> + pr_info("OCC Active, CPU frequency is no longer throttled\n");
>
> for (i = 0; i < nr_chips; i++) {
> chips[i].restore = true;
Acked-by: Viresh Kumar <viresh.kumar@linaro.org>
--
viresh
next prev parent reply other threads:[~2015-08-27 12:29 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-08-27 9:11 [PATCH] cpufreq: powernv: Increase the verbosity of OCC console messages Shilpasri G Bhat
2015-08-27 12:29 ` Viresh Kumar [this message]
2015-08-31 21:39 ` Stewart Smith
2015-08-31 21:39 ` Stewart Smith
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=20150827122940.GW8784@linux \
--to=viresh.kumar@linaro.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=linuxppc-dev@ozlabs.org \
--cc=rjw@rjwysocki.net \
--cc=shilpa.bhat@linux.vnet.ibm.com \
--cc=stewart@linux.vnet.ibm.com \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.