linux-pm.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Gautham R Shenoy <ego@linux.vnet.ibm.com>
To: Abhishek Goel <huntbag@linux.vnet.ibm.com>
Cc: trenn@suse.com, linux-pm@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] cpupower : Fix cpupower working when cpu0 is offline
Date: Tue, 26 Sep 2017 15:42:36 +0530	[thread overview]
Message-ID: <20170926101236.GA25906@in.ibm.com> (raw)
In-Reply-To: <20170922110218.120948-1-huntbag@linux.vnet.ibm.com>

On Fri, Sep 22, 2017 at 04:32:18PM +0530, Abhishek Goel wrote:
> cpuidle_monitor used to assume that cpu0 is always online.

On what platform is this assumption not valid and what is the problem
caused due to this.

> Now the
> cpuidle_monitor function searches for the first online cpu and use
> it, instead of always using cpu0 which may not be online.

Mention that this is the fix performed by this patch.

> 
> Signed-off-by: Abhishek Goel <huntbag@linux.vnet.ibm.com>
> ---
>  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;
> +	};

Don't we have an API that gives the list by parsing
"/sys/devices/system/cpu/online" ?


> +	first_online_cpu = num;
>
>  	/* Assume idle state count is the same for all CPUs */
> -	cpuidle_sysfs_monitor.hw_states_num = cpuidle_state_count(0);
> +	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);


Looks ok to me otherwise.

> -- 
> 2.9.3
> 

  reply	other threads:[~2017-09-26 10:12 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-09-22 11:02 [PATCH] cpupower : Fix cpupower working when cpu0 is offline Abhishek Goel
2017-09-26 10:12 ` Gautham R Shenoy [this message]
  -- strict thread matches above, loose matches on Subject: below --
2017-09-22  8:47 Abhishek Goel

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=20170926101236.GA25906@in.ibm.com \
    --to=ego@linux.vnet.ibm.com \
    --cc=huntbag@linux.vnet.ibm.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-pm@vger.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;
as well as URLs for NNTP newsgroup(s).