From: "Liao, Chang" <liaochang1@huawei.com>
To: Viresh Kumar <viresh.kumar@linaro.org>
Cc: <rafael@kernel.org>, <linux-pm@vger.kernel.org>,
<linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] cpufreq: Fix inconsistency in error messages of cpufreq_resume/suspend()
Date: Mon, 28 Aug 2023 20:31:07 +0800 [thread overview]
Message-ID: <b7be717c-41d8-bbbf-3e97-3799948ab757@huawei.com> (raw)
In-Reply-To: <20230828070000.ooymfbw3qhs5xl5y@vireshk-i7>
Hi, Viresh
在 2023/8/28 15:00, Viresh Kumar 写道:
> On 26-08-23, 09:52, Liao Chang wrote:
>> The error message printed by cpufreq_resume() currently is the pointer
>> value of the policy structure, while the error message printed by
>> cpufreq_suspend() is the name of the driver. In order to make the error
>> messages more consistent and easier to understand, change the error
>> message printed by cpufreq_resume() to the name of driver.
>
> Also I don't think printing kernel addresses will help much anyway,
> and it also may not be recommended.
>
>> Signed-off-by: Liao Chang <liaochang1@huawei.com>
>> ---
>> drivers/cpufreq/cpufreq.c | 4 ++--
>> 1 file changed, 2 insertions(+), 2 deletions(-)
>>
>> diff --git a/drivers/cpufreq/cpufreq.c b/drivers/cpufreq/cpufreq.c
>> index c835ff117386..2199c04ac64d 100644
>> --- a/drivers/cpufreq/cpufreq.c
>> +++ b/drivers/cpufreq/cpufreq.c
>> @@ -1943,8 +1943,8 @@ void cpufreq_resume(void)
>>
>> for_each_active_policy(policy) {
>> if (cpufreq_driver->resume && cpufreq_driver->resume(policy)) {
>> - pr_err("%s: Failed to resume driver: %p\n", __func__,
>> - policy);
>> + pr_err("%s: Failed to resume driver: %s\n", __func__,
>> + cpufreq_driver->name);
>> } else if (has_target()) {
>> down_write(&policy->rwsem);
>> ret = cpufreq_start_governor(policy);
>
> There is another print down here which prints policy, please update
> that too in a similar way.
What about printing message like this below when cpufreq_start_governor() fails.
diff --git a/drivers/cpufreq/cpufreq.c b/drivers/cpufreq/cpufreq.c
index 50bbc969ffe5..b78b509429a6 100644
--- a/drivers/cpufreq/cpufreq.c
+++ b/drivers/cpufreq/cpufreq.c
@@ -1943,16 +1943,16 @@ void cpufreq_resume(void)
if (ret)
- pr_err("%s: Failed to start governor for policy: %p\n",
- __func__, policy);
+ pr_err("%s: Failed to start governor for policy%u\n",
+ __func__, policy->cpu);
}
}
}
>
--
BR
Liao, Chang
next prev parent reply other threads:[~2023-08-28 12:32 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-08-26 9:52 Liao Chang
2023-08-28 7:00 ` Viresh Kumar
2023-08-28 12:31 ` Liao, Chang [this message]
2023-08-29 6:01 ` Viresh Kumar
2023-08-29 6:22 ` Liao, Chang
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=b7be717c-41d8-bbbf-3e97-3799948ab757@huawei.com \
--to=liaochang1@huawei.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--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®