From: Shuah Khan <shuahkh@osg.samsung.com>
To: Abhishek <huntbag@linux.vnet.ibm.com>,
linux-pm@vger.kernel.org, linux-kernel@vger.kernel.org
Cc: Shuah Khan <shuah@kernel.org>, Thomas Renninger <trenn@suse.com>
Subject: Re: [PATCH v2] cpupower : Fix cpupower working when cpu0 is offline
Date: Tue, 7 Nov 2017 11:20:33 -0700 [thread overview]
Message-ID: <63bf8c5d-2a7e-484b-8d13-81bb6bef175d@osg.samsung.com> (raw)
In-Reply-To: <b1ae1a14-b354-6bc5-6118-87c7b65ce8a1@linux.vnet.ibm.com>
On 11/07/2017 01:58 AM, Abhishek wrote:
> Hi,
>
> Can you have a look at it?
>
> Thanks and Regards,
>
> Abhishek Goel
>
> System Engineer
>
> IBM India Pvt. Ltd.
>
Please refrain from top posting on kernel email thread.
In-lining comments and bottom posting is the norm.
>
> On 11/07/2017 12:50 PM, Abhishek Goel wrote:
>> cpuidle_monitor used to assume that cpu0 is always online which is not
>> a valid assumption on POWER machines. This patch fixes this by searching
>> for the first online cpu and uses it, instead of always using cpu0 for
>> monitoring which may not be online.
>>
>> Signed-off-by: Abhishek Goel <huntbag@linux.vnet.ibm.com>
>> ---
>> v2: Commit message updated.
>> ---
>> tools/power/cpupower/utils/idle_monitor/cpuidle_sysfs.c | 14 +++++++++++---
>> 1 file changed, 11 insertions(+), 3 deletions(-)
>>
>> diff --git a/tools/power/cpupower/utils/idle_monitor/cpuidle_sysfs.c b/tools/power/cpupower/utils/idle_monitor/cpuidle_sysfs.c
>> index 1b5da00..adacf99 100644
>> --- a/tools/power/cpupower/utils/idle_monitor/cpuidle_sysfs.c
>> +++ b/tools/power/cpupower/utils/idle_monitor/cpuidle_sysfs.c
>> @@ -130,15 +130,23 @@ static struct cpuidle_monitor *cpuidle_register(void)
>> {
>> int num;
>> char *tmp;
>> + int first_online_cpu;
>> +
>> + for (num = 0; num < cpu_count; num++) {
>> + if (cpupower_is_cpu_online(num))
>> + break;
>> + };
>> + first_online_cpu = num;
Isn't it simpler to use sched_getcpu()n instead and use that instead
of walking the sysfs nodes since assumption is made that the idle state
count is the same for all CPUs
>>
>> /* Assume idle state count is the same for all CPUs */
>> - cpuidle_sysfs_monitor.hw_states_num = cpuidle_state_count(0);
This simply be:
cpuidle_sysfs_monitor.hw_states_num = cpuidle_state_count(sched_getcpu);
>> + cpuidle_sysfs_monitor.hw_states_num =
>> + cpuidle_state_count(first_online_cpu);
>>
>> if (cpuidle_sysfs_monitor.hw_states_num <= 0)
>> return NULL;
>>
>> for (num = 0; num < cpuidle_sysfs_monitor.hw_states_num; num++) {
>> - tmp = cpuidle_state_name(0, num);
>> + tmp = cpuidle_state_name(first_online_cpu, num);
>> if (tmp == NULL)
>> continue;
>>
>> @@ -146,7 +154,7 @@ static struct cpuidle_monitor *cpuidle_register(void)
>> strncpy(cpuidle_cstates[num].name, tmp, CSTATE_NAME_LEN - 1);
>> free(tmp);
>>
>> - tmp = cpuidle_state_desc(0, num);
>> + tmp = cpuidle_state_desc(first_online_cpu, num);
>> if (tmp == NULL)
>> continue;
>> strncpy(cpuidle_cstates[num].desc, tmp, CSTATE_DESC_LEN - 1);
>
thanks,
-- Shuah
prev parent reply other threads:[~2017-11-07 18:20 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-11-07 7:20 Abhishek Goel
2017-11-07 8:58 ` Abhishek
2017-11-07 18:20 ` Shuah Khan [this message]
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=63bf8c5d-2a7e-484b-8d13-81bb6bef175d@osg.samsung.com \
--to=shuahkh@osg.samsung.com \
--cc=huntbag@linux.vnet.ibm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=shuah@kernel.org \
--cc=trenn@suse.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 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®