All of lore.kernel.org
 help / color / mirror / Atom feed
From: Preeti U Murthy <preeti@linux.vnet.ibm.com>
To: Shilpasri G Bhat <shilpa.bhat@linux.vnet.ibm.com>,
	linuxppc-dev@ozlabs.org, linux-kernel@vger.kernel.org
Cc: rjw@rjwysocki.net, viresh.kumar@linaro.org, linux-pm@vger.kernel.org
Subject: Re: [PATCH v3 6/6] cpufreq: powernv: Restore cpu frequency to policy->cur on unthrottling
Date: Tue, 05 May 2015 15:09:57 +0530	[thread overview]
Message-ID: <55488FED.4080909@linux.vnet.ibm.com> (raw)
In-Reply-To: <1430729652-14813-7-git-send-email-shilpa.bhat@linux.vnet.ibm.com>

On 05/04/2015 02:24 PM, Shilpasri G Bhat wrote:
> If frequency is throttled due to OCC reset then cpus will be in Psafe
> frequency, so restore the frequency on all cpus to policy->cur when
> OCCs are active again. And if frequency is throttled due to Pmax
> capping then restore the frequency of all the cpus  in the chip on
> unthrottling.
> 
> Signed-off-by: Shilpasri G Bhat <shilpa.bhat@linux.vnet.ibm.com>
> ---
>  drivers/cpufreq/powernv-cpufreq.c | 31 +++++++++++++++++++++++++++++--
>  1 file changed, 29 insertions(+), 2 deletions(-)
> 
> diff --git a/drivers/cpufreq/powernv-cpufreq.c b/drivers/cpufreq/powernv-cpufreq.c
> index 0a59d5b..b2915bc 100644
> --- a/drivers/cpufreq/powernv-cpufreq.c
> +++ b/drivers/cpufreq/powernv-cpufreq.c
> @@ -51,6 +51,7 @@ static struct chip {
>  	bool throttled;
>  	cpumask_t mask;
>  	struct work_struct throttle;
> +	bool restore;
>  } *chips;
> 
>  static int nr_chips;
> @@ -418,9 +419,29 @@ static struct notifier_block powernv_cpufreq_reboot_nb = {
>  void powernv_cpufreq_work_fn(struct work_struct *work)
>  {
>  	struct chip *chip = container_of(work, struct chip, throttle);
> +	unsigned int cpu;
> +	cpumask_var_t mask;
> 
>  	smp_call_function_any(&chip->mask,
>  			      powernv_cpufreq_throttle_check, NULL, 0);
> +
> +	if (!chip->restore)
> +		return;
> +
> +	chip->restore = false;
> +	cpumask_copy(mask, &chip->mask);
> +	for_each_cpu_and(cpu, mask, cpu_online_mask) {
> +		int index, tcpu;
> +		struct cpufreq_policy policy;
> +
> +		cpufreq_get_policy(&policy, cpu);
> +		cpufreq_frequency_table_target(&policy, policy.freq_table,
> +					       policy.cur,
> +					       CPUFREQ_RELATION_C, &index);
> +		powernv_cpufreq_target_index(&policy, index);
> +		for_each_cpu(tcpu, policy.cpus)
> +			cpumask_clear_cpu(tcpu, mask);
> +	}
>  }
> 
>  static char throttle_reason[][30] = {
> @@ -473,8 +494,10 @@ static int powernv_cpufreq_occ_msg(struct notifier_block *nb,
>  			throttled = false;
>  			pr_info("OCC: Active\n");
> 
> -			for (i = 0; i < nr_chips; i++)
> +			for (i = 0; i < nr_chips; i++) {
> +				chips[i].restore = true;
>  				schedule_work(&chips[i].throttle);
> +			}
> 
>  			return 0;
>  		}
> @@ -490,8 +513,11 @@ static int powernv_cpufreq_occ_msg(struct notifier_block *nb,
>  			return 0;
> 
>  		for (i = 0; i < nr_chips; i++)
> -			if (chips[i].id == chip_id)
> +			if (chips[i].id == chip_id) {
> +				if (!reason)
> +					chips[i].restore = true;
>  				schedule_work(&chips[i].throttle);
> +			}
>  	}
>  	return 0;
>  }
> @@ -545,6 +571,7 @@ static int init_chip_info(void)
>  		chips[i].throttled = false;
>  		cpumask_copy(&chips[i].mask, cpumask_of_node(chip[i]));
>  		INIT_WORK(&chips[i].throttle, powernv_cpufreq_work_fn);
> +		chips[i].restore = false;
>  	}
> 
>  	return 0;
> 

Reviewed-by: Preeti U Murthy <preeti@linux.vnet.ibm.com>


WARNING: multiple messages have this Message-ID (diff)
From: Preeti U Murthy <preeti@linux.vnet.ibm.com>
To: Shilpasri G Bhat <shilpa.bhat@linux.vnet.ibm.com>,
	linuxppc-dev@ozlabs.org, linux-kernel@vger.kernel.org
Cc: viresh.kumar@linaro.org, rjw@rjwysocki.net, linux-pm@vger.kernel.org
Subject: Re: [PATCH v3 6/6] cpufreq: powernv: Restore cpu frequency to policy->cur on unthrottling
Date: Tue, 05 May 2015 15:09:57 +0530	[thread overview]
Message-ID: <55488FED.4080909@linux.vnet.ibm.com> (raw)
In-Reply-To: <1430729652-14813-7-git-send-email-shilpa.bhat@linux.vnet.ibm.com>

On 05/04/2015 02:24 PM, Shilpasri G Bhat wrote:
> If frequency is throttled due to OCC reset then cpus will be in Psafe
> frequency, so restore the frequency on all cpus to policy->cur when
> OCCs are active again. And if frequency is throttled due to Pmax
> capping then restore the frequency of all the cpus  in the chip on
> unthrottling.
> 
> Signed-off-by: Shilpasri G Bhat <shilpa.bhat@linux.vnet.ibm.com>
> ---
>  drivers/cpufreq/powernv-cpufreq.c | 31 +++++++++++++++++++++++++++++--
>  1 file changed, 29 insertions(+), 2 deletions(-)
> 
> diff --git a/drivers/cpufreq/powernv-cpufreq.c b/drivers/cpufreq/powernv-cpufreq.c
> index 0a59d5b..b2915bc 100644
> --- a/drivers/cpufreq/powernv-cpufreq.c
> +++ b/drivers/cpufreq/powernv-cpufreq.c
> @@ -51,6 +51,7 @@ static struct chip {
>  	bool throttled;
>  	cpumask_t mask;
>  	struct work_struct throttle;
> +	bool restore;
>  } *chips;
> 
>  static int nr_chips;
> @@ -418,9 +419,29 @@ static struct notifier_block powernv_cpufreq_reboot_nb = {
>  void powernv_cpufreq_work_fn(struct work_struct *work)
>  {
>  	struct chip *chip = container_of(work, struct chip, throttle);
> +	unsigned int cpu;
> +	cpumask_var_t mask;
> 
>  	smp_call_function_any(&chip->mask,
>  			      powernv_cpufreq_throttle_check, NULL, 0);
> +
> +	if (!chip->restore)
> +		return;
> +
> +	chip->restore = false;
> +	cpumask_copy(mask, &chip->mask);
> +	for_each_cpu_and(cpu, mask, cpu_online_mask) {
> +		int index, tcpu;
> +		struct cpufreq_policy policy;
> +
> +		cpufreq_get_policy(&policy, cpu);
> +		cpufreq_frequency_table_target(&policy, policy.freq_table,
> +					       policy.cur,
> +					       CPUFREQ_RELATION_C, &index);
> +		powernv_cpufreq_target_index(&policy, index);
> +		for_each_cpu(tcpu, policy.cpus)
> +			cpumask_clear_cpu(tcpu, mask);
> +	}
>  }
> 
>  static char throttle_reason[][30] = {
> @@ -473,8 +494,10 @@ static int powernv_cpufreq_occ_msg(struct notifier_block *nb,
>  			throttled = false;
>  			pr_info("OCC: Active\n");
> 
> -			for (i = 0; i < nr_chips; i++)
> +			for (i = 0; i < nr_chips; i++) {
> +				chips[i].restore = true;
>  				schedule_work(&chips[i].throttle);
> +			}
> 
>  			return 0;
>  		}
> @@ -490,8 +513,11 @@ static int powernv_cpufreq_occ_msg(struct notifier_block *nb,
>  			return 0;
> 
>  		for (i = 0; i < nr_chips; i++)
> -			if (chips[i].id == chip_id)
> +			if (chips[i].id == chip_id) {
> +				if (!reason)
> +					chips[i].restore = true;
>  				schedule_work(&chips[i].throttle);
> +			}
>  	}
>  	return 0;
>  }
> @@ -545,6 +571,7 @@ static int init_chip_info(void)
>  		chips[i].throttled = false;
>  		cpumask_copy(&chips[i].mask, cpumask_of_node(chip[i]));
>  		INIT_WORK(&chips[i].throttle, powernv_cpufreq_work_fn);
> +		chips[i].restore = false;
>  	}
> 
>  	return 0;
> 

Reviewed-by: Preeti U Murthy <preeti@linux.vnet.ibm.com>

  reply	other threads:[~2015-05-05  9:40 UTC|newest]

Thread overview: 40+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-05-04  8:54 [PATCH v3 0/6] powernv: cpufreq: Report frequency throttle by OCC Shilpasri G Bhat
2015-05-04  8:54 ` Shilpasri G Bhat
2015-05-04  8:54 ` [PATCH v3 1/6] cpufreq: poowernv: Handle throttling due to Pmax capping at chip level Shilpasri G Bhat
2015-05-04  8:54   ` Shilpasri G Bhat
2015-05-05  3:51   ` Preeti U Murthy
2015-05-05  3:51     ` Preeti U Murthy
2015-05-05  6:06     ` Shilpasri G Bhat
2015-05-05  6:06       ` Shilpasri G Bhat
2015-05-05  8:38       ` Preeti U Murthy
2015-05-07 10:35         ` Shilpasri G Bhat
2015-05-07 12:15           ` Preeti U Murthy
2015-05-04  8:54 ` [PATCH v3 2/6] powerpc/powernv: Add definition of OPAL_MSG_OCC message type Shilpasri G Bhat
2015-05-04  8:54   ` Shilpasri G Bhat
2015-05-04  8:54 ` [PATCH v3 3/6] cpufreq: powernv: Register for OCC related opal_message notification Shilpasri G Bhat
2015-05-04  8:54   ` Shilpasri G Bhat
2015-05-05  3:42   ` Preeti U Murthy
2015-05-05  3:42     ` Preeti U Murthy
2015-05-04  8:54 ` [PATCH v3 4/6] cpufreq: powernv: Call throttle_check() on receiving OCC_THROTTLE Shilpasri G Bhat
2015-05-04  8:54   ` Shilpasri G Bhat
2015-05-05  4:00   ` Preeti U Murthy
2015-05-05  4:00     ` Preeti U Murthy
2015-05-05  6:33     ` Shilpasri G Bhat
2015-05-05  6:33       ` Shilpasri G Bhat
2015-05-05  8:41       ` Preeti U Murthy
2015-05-07 12:19         ` Preeti U Murthy
2015-05-07 20:59           ` Rafael J. Wysocki
2015-05-07 20:59             ` Rafael J. Wysocki
2015-05-08  3:46             ` Preeti U Murthy
2015-05-08  3:46               ` Preeti U Murthy
2015-05-08 14:11               ` Rafael J. Wysocki
2015-05-08 14:11                 ` Rafael J. Wysocki
2015-05-04  8:54 ` [PATCH v3 5/6] cpufreq: powernv: Report Psafe only if PMSR.psafe_mode_active bit is set Shilpasri G Bhat
2015-05-04  8:54   ` Shilpasri G Bhat
2015-05-05  3:46   ` Preeti U Murthy
2015-05-04  8:54 ` [PATCH v3 6/6] cpufreq: powernv: Restore cpu frequency to policy->cur on unthrottling Shilpasri G Bhat
2015-05-04  8:54   ` Shilpasri G Bhat
2015-05-05  9:39   ` Preeti U Murthy [this message]
2015-05-05  9:39     ` Preeti U Murthy
2015-05-08  5:12 ` [PATCH v3 0/6] powernv: cpufreq: Report frequency throttle by OCC Viresh Kumar
2015-05-08  5:12   ` Viresh Kumar

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=55488FED.4080909@linux.vnet.ibm.com \
    --to=preeti@linux.vnet.ibm.com \
    --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=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 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.