From: Gautham R. Shenoy <hidden> Date: 2014-03-20 12:10:55
From: "Gautham R. Shenoy" <redacted>
Hi,
This is the v3 of the consolidated patchset consisting
patches for enabling cpufreq on IBM POWERNV platforms
along with some enhancements. I have incorporated the review
for v2 (which can be found at [1]).
- This patchset contains code for the platform driver to support CPU
frequency scaling on IBM POWERNV platforms.
- In addition to the standard control and status files exposed by the
cpufreq core, the patchset exposes the nominal frequency through the
file named "cpuinfo_nominal_freq".
The changes from from v2:
- Updated the changelog for "powernv: cpufreq driver for powernv platform"
to record the fact that policy->cpus must be populated with a sibling mask
that includes even the offlined siblings.
- Dropped the patch named
"powernv:cpufreq: Create a powernv_cpu_to_core_mask() helper"
since the driver->get() method can use cpu_sibling_mask().
- Updated "powernv:cpufreq: Implement the driver->get() method" to
use cpu_sibling_mask() in powernv_cpufreq_get()
The patchset is based against commit 4907cdca7210c5895311bddcf05a4c85b67d8566
of the mainline tree.
[1]: https://lists.ozlabs.org/pipermail/linuxppc-dev/2014-March/115861.html
Gautham R. Shenoy (3):
powernv:cpufreq: Create pstate_id_to_freq() helper
powernv:cpufreq: Export nominal frequency via sysfs.
powernv:cpufreq: Implement the driver->get() method
Srivatsa S. Bhat (1):
powernv,cpufreq:Add per-core locking to serialize frequency
transitions
Vaidyanathan Srinivasan (1):
powernv: cpufreq driver for powernv platform
arch/powerpc/include/asm/reg.h | 4 +
arch/powerpc/platforms/powernv/Kconfig | 1 +
drivers/cpufreq/Kconfig | 1 +
drivers/cpufreq/Kconfig.powerpc | 13 ++
drivers/cpufreq/Makefile | 1 +
drivers/cpufreq/powernv-cpufreq.c | 375 +++++++++++++++++++++++++++++++++
6 files changed, 395 insertions(+)
create mode 100644 drivers/cpufreq/powernv-cpufreq.c
--
1.8.3.1
From: Gautham R. Shenoy <hidden> Date: 2014-03-20 12:11:13
From: Vaidyanathan Srinivasan <redacted>
Backend driver to dynamically set voltage and frequency on
IBM POWER non-virtualized platforms. Power management SPRs
are used to set the required PState.
This driver works in conjunction with cpufreq governors
like 'ondemand' to provide a demand based frequency and
voltage setting on IBM POWER non-virtualized platforms.
PState table is obtained from OPAL v3 firmware through device
tree.
powernv_cpufreq back-end driver would parse the relevant device-tree
nodes and initialise the cpufreq subsystem on powernv platform.
The policy->cpus needs to be populated in a hotplug-invariant manner
instead of using cpu_sibling_mask() which varies with cpu-hotplug. This
is because the cpufreq core code copies this content into policy->related_cpus
mask which is should not vary on cpu-hotplug.
[Change log updated by ego@linux.vnet.ibm.com]
Signed-off-by: Vaidyanathan Srinivasan <redacted>
Signed-off-by: Srivatsa S. Bhat <redacted>
Signed-off-by: Anton Blanchard <redacted>
Signed-off-by: Gautham R. Shenoy <redacted>
---
arch/powerpc/include/asm/reg.h | 4 +
arch/powerpc/platforms/powernv/Kconfig | 1 +
drivers/cpufreq/Kconfig | 1 +
drivers/cpufreq/Kconfig.powerpc | 13 ++
drivers/cpufreq/Makefile | 1 +
drivers/cpufreq/powernv-cpufreq.c | 277 +++++++++++++++++++++++++++++++++
6 files changed, 297 insertions(+)
create mode 100644 drivers/cpufreq/powernv-cpufreq.c
@@ -54,3 +54,16 @@ config PPC_PASEMI_CPUFREQhelpThisaddsthesupportforfrequencyswitchingonPASemiPWRficientprocessors.++configPOWERNV_CPUFREQ+tristate"CPU frequency scaling for IBM POWERNV platform"+depends onPPC_POWERNV+selectCPU_FREQ_GOV_PERFORMANCE+selectCPU_FREQ_GOV_POWERSAVE+selectCPU_FREQ_GOV_USERSPACE+selectCPU_FREQ_GOV_ONDEMAND+selectCPU_FREQ_GOV_CONSERVATIVE+defaulty+help+ThisaddssupportforCPUfrequencyswitchingonIBMPOWERNV+platform
@@ -0,0 +1,277 @@+/*+*POWERNVcpufreqdriverfortheIBMPOWERprocessors+*+*(C)CopyrightIBM2014+*+*Author:VaidyanathanSrinivasan<svaidyatlinux.vnet.ibm.com>+*+*Thisprogramisfreesoftware;youcanredistributeitand/ormodify+*itunderthetermsoftheGNUGeneralPublicLicenseaspublishedby+*theFreeSoftwareFoundation;eitherversion2,or(atyouroption)+*anylaterversion.+*+*Thisprogramisdistributedinthehopethatitwillbeuseful,+*butWITHOUTANYWARRANTY;withouteventheimpliedwarrantyof+*MERCHANTABILITYorFITNESSFORAPARTICULARPURPOSE.Seethe+*GNUGeneralPublicLicenseformoredetails.+*+*/++#define pr_fmt(fmt) "powernv-cpufreq: " fmt++#include<linux/module.h>+#include<linux/cpufreq.h>+#include<linux/of.h>+#include<asm/cputhreads.h>++/* FIXME: Make this per-core */+staticDEFINE_MUTEX(freq_switch_mutex);++#define POWERNV_MAX_PSTATES 256++staticstructcpufreq_frequency_tablepowernv_freqs[POWERNV_MAX_PSTATES+1];+staticintpowernv_pstate_ids[POWERNV_MAX_PSTATES+1];++/*+*Initializethefreqtablebasedondataobtained+*fromthefirmwarepassedviadevice-tree+*/++staticintinit_powernv_pstates(void)+{+structdevice_node*power_mgt;+intnr_pstates=0;+intpstate_min,pstate_max,pstate_nominal;+const__be32*pstate_ids,*pstate_freqs;+inti;+u32len_ids,len_freqs;++power_mgt=of_find_node_by_path("/ibm,opal/power-mgt");+if(!power_mgt){+pr_warn("power-mgt node not found\n");+return-ENODEV;+}++if(of_property_read_u32(power_mgt,"ibm,pstate-min",&pstate_min)){+pr_warn("ibm,pstate-min node not found\n");+return-ENODEV;+}++if(of_property_read_u32(power_mgt,"ibm,pstate-max",&pstate_max)){+pr_warn("ibm,pstate-max node not found\n");+return-ENODEV;+}++if(of_property_read_u32(power_mgt,"ibm,pstate-nominal",+&pstate_nominal)){+pr_warn("ibm,pstate-nominal not found\n");+return-ENODEV;+}+pr_info("cpufreq pstate min %d nominal %d max %d\n",pstate_min,+pstate_nominal,pstate_max);++pstate_ids=of_get_property(power_mgt,"ibm,pstate-ids",&len_ids);+if(!pstate_ids){+pr_warn("ibm,pstate-ids not found\n");+return-ENODEV;+}++pstate_freqs=of_get_property(power_mgt,"ibm,pstate-frequencies-mhz",+&len_freqs);+if(!pstate_freqs){+pr_warn("ibm,pstate-frequencies-mhz not found\n");+return-ENODEV;+}++WARN_ON(len_ids!=len_freqs);+nr_pstates=min(len_ids,len_freqs)/sizeof(u32);+WARN_ON(!nr_pstates);++pr_debug("NR PStates %d\n",nr_pstates);+for(i=0;i<nr_pstates;i++){+u32id=be32_to_cpu(pstate_ids[i]);+u32freq=be32_to_cpu(pstate_freqs[i]);++pr_debug("PState id %d freq %d MHz\n",id,freq);+powernv_freqs[i].driver_data=i;+powernv_freqs[i].frequency=freq*1000;/* kHz */+powernv_pstate_ids[i]=id;+}+/* End of list marker entry */+powernv_freqs[i].driver_data=0;+powernv_freqs[i].frequency=CPUFREQ_TABLE_END;++/* Print frequency table */+for(i=0;powernv_freqs[i].frequency!=CPUFREQ_TABLE_END;i++)+pr_debug("%d: %d\n",i,powernv_freqs[i].frequency);++return0;+}++staticstructfreq_attr*powernv_cpu_freq_attr[]={+&cpufreq_freq_attr_scaling_available_freqs,+NULL,+};++/* Helper routines */++/* Access helpers to power mgt SPR */++staticinlineunsignedlongget_pmspr(unsignedlongsprn)+{+switch(sprn){+caseSPRN_PMCR:+returnmfspr(SPRN_PMCR);++caseSPRN_PMICR:+returnmfspr(SPRN_PMICR);++caseSPRN_PMSR:+returnmfspr(SPRN_PMSR);+}+BUG();+}++staticinlinevoidset_pmspr(unsignedlongsprn,unsignedlongval)+{+switch(sprn){+caseSPRN_PMCR:+mtspr(SPRN_PMCR,val);+return;++caseSPRN_PMICR:+mtspr(SPRN_PMICR,val);+return;++caseSPRN_PMSR:+mtspr(SPRN_PMSR,val);+return;+}+BUG();+}++staticvoidset_pstate(void*pstate)+{+unsignedlongval;+unsignedlongpstate_ul=*(unsignedlong*)pstate;++val=get_pmspr(SPRN_PMCR);+val=val&0x0000ffffffffffffULL;+/* Set both global(bits 56..63) and local(bits 48..55) PStates */+val=val|(pstate_ul<<56)|(pstate_ul<<48);+pr_debug("Setting cpu %d pmcr to %016lX\n",smp_processor_id(),val);+set_pmspr(SPRN_PMCR,val);+}++staticintpowernv_set_freq(cpumask_var_tcpus,unsignedintnew_index)+{+unsignedlongval=(unsignedlong)powernv_pstate_ids[new_index];++/*+*Usesmp_call_functiontosendIPIandexecutethe+*mtsprontargetcpu.WecoulddothatwithoutIPI+*ifcurrentCPUiswithinpolicy->cpus(core)+*/++val=val&0xFF;+smp_call_function_any(cpus,set_pstate,&val,1);+return0;+}++staticintpowernv_cpufreq_cpu_init(structcpufreq_policy*policy)+{+intbase,i;++#ifdef CONFIG_SMP+base=cpu_first_thread_sibling(policy->cpu);++for(i=0;i<threads_per_core;i++)+cpumask_set_cpu(base+i,policy->cpus);+#endif+policy->cpuinfo.transition_latency=25000;++policy->cur=powernv_freqs[0].frequency;+cpufreq_frequency_table_get_attr(powernv_freqs,policy->cpu);+returncpufreq_frequency_table_cpuinfo(policy,powernv_freqs);+}++staticintpowernv_cpufreq_cpu_exit(structcpufreq_policy*policy)+{+cpufreq_frequency_table_put_attr(policy->cpu);+return0;+}++staticintpowernv_cpufreq_verify(structcpufreq_policy*policy)+{+returncpufreq_frequency_table_verify(policy,powernv_freqs);+}++staticintpowernv_cpufreq_target(structcpufreq_policy*policy,+unsignedinttarget_freq,+unsignedintrelation)+{+intrc;+structcpufreq_freqsfreqs;+unsignedintnew_index;++cpufreq_frequency_table_target(policy,powernv_freqs,target_freq,+relation,&new_index);++freqs.old=policy->cur;+freqs.new=powernv_freqs[new_index].frequency;+freqs.cpu=policy->cpu;++mutex_lock(&freq_switch_mutex);+cpufreq_notify_transition(policy,&freqs,CPUFREQ_PRECHANGE);++pr_debug("setting frequency for cpu %d to %d kHz index %d pstate %d",+policy->cpu,+powernv_freqs[new_index].frequency,+new_index,+powernv_pstate_ids[new_index]);++rc=powernv_set_freq(policy->cpus,new_index);++cpufreq_notify_transition(policy,&freqs,CPUFREQ_POSTCHANGE);+mutex_unlock(&freq_switch_mutex);++returnrc;+}++staticstructcpufreq_driverpowernv_cpufreq_driver={+.verify=powernv_cpufreq_verify,+.target=powernv_cpufreq_target,+.init=powernv_cpufreq_cpu_init,+.exit=powernv_cpufreq_cpu_exit,+.name="powernv-cpufreq",+.flags=CPUFREQ_CONST_LOOPS,+.attr=powernv_cpu_freq_attr,+};++staticint__initpowernv_cpufreq_init(void)+{+intrc=0;++/* Discover pstates from device tree and init */++rc=init_powernv_pstates();++if(rc){+pr_info("powernv-cpufreq disabled\n");+returnrc;+}++rc=cpufreq_register_driver(&powernv_cpufreq_driver);+returnrc;+}++staticvoid__exitpowernv_cpufreq_exit(void)+{+cpufreq_unregister_driver(&powernv_cpufreq_driver);+}++module_init(powernv_cpufreq_init);+module_exit(powernv_cpufreq_exit);++MODULE_LICENSE("GPL");+MODULE_AUTHOR("Vaidyanathan Srinivasan <svaidy at linux.vnet.ibm.com>");
From: Gautham R. Shenoy <hidden> Date: 2014-03-20 12:11:14
From: "Srivatsa S. Bhat" <redacted>
On POWER systems, the CPU frequency is controlled at a core-level and
hence we need to serialize so that only one of the threads in the core
switches the core's frequency at a time.
Using a global mutex lock would needlessly serialize _all_ frequency
transitions in the system (across all cores). So introduce per-core
locking to enable finer-grained synchronization and thereby enhance
the speed and responsiveness of the cpufreq driver to varying workload
demands.
The design of per-core locking is very simple and straight-forward: we
first define a Per-CPU lock and use the ones that belongs to the first
thread sibling of the core.
cpu_first_thread_sibling() macro is used to find the *common* lock for
all thread siblings belonging to a core.
Signed-off-by: Srivatsa S. Bhat <redacted>
Signed-off-by: Vaidyanathan Srinivasan <redacted>
Signed-off-by: Gautham R. Shenoy <redacted>
---
drivers/cpufreq/powernv-cpufreq.c | 21 ++++++++++++++++-----
1 file changed, 16 insertions(+), 5 deletions(-)
@@ -24,8 +24,15 @@#include<linux/of.h>#include<asm/cputhreads.h>-/* FIXME: Make this per-core */-staticDEFINE_MUTEX(freq_switch_mutex);+/* Per-Core locking for frequency transitions */+staticDEFINE_PER_CPU(structmutex,freq_switch_lock);++#define lock_core_freq(cpu) \+mutex_lock(&per_cpu(freq_switch_lock,\+cpu_first_thread_sibling(cpu)));+#define unlock_core_freq(cpu) \+mutex_unlock(&per_cpu(freq_switch_lock,\+cpu_first_thread_sibling(cpu)));#define POWERNV_MAX_PSTATES 256
@@ -221,7 +228,7 @@ static int powernv_cpufreq_target(struct cpufreq_policy *policy,freqs.new=powernv_freqs[new_index].frequency;freqs.cpu=policy->cpu;-mutex_lock(&freq_switch_mutex);+lock_core_freq(policy->cpu);cpufreq_notify_transition(policy,&freqs,CPUFREQ_PRECHANGE);pr_debug("setting frequency for cpu %d to %d kHz index %d pstate %d",
@@ -233,7 +240,7 @@ static int powernv_cpufreq_target(struct cpufreq_policy *policy,rc=powernv_set_freq(policy->cpus,new_index);cpufreq_notify_transition(policy,&freqs,CPUFREQ_POSTCHANGE);-mutex_unlock(&freq_switch_mutex);+unlock_core_freq(policy->cpu);returnrc;}
@@ -250,7 +257,7 @@ static struct cpufreq_driver powernv_cpufreq_driver = {staticint__initpowernv_cpufreq_init(void){-intrc=0;+intcpu,rc=0;/* Discover pstates from device tree and init */
From: Gautham R. Shenoy <hidden> Date: 2014-03-20 12:11:16
From: "Gautham R. Shenoy" <redacted>
Create a driver attribute named cpuinfo_nominal_freq which
creates a sysfs read-only file named cpuinfo_nominal_freq. Export
the frequency corresponding to the nominal_pstate through this
interface.
Nominal frequency is the highest non-turbo frequency for the
platform. This is generally used for setting governor policies from
user space for optimal energy efficiency.
Signed-off-by: Gautham R. Shenoy <redacted>
---
drivers/cpufreq/powernv-cpufreq.c | 22 ++++++++++++++++++++++
1 file changed, 22 insertions(+)
From: Gautham R. Shenoy <hidden> Date: 2014-03-20 12:11:44
From: "Gautham R. Shenoy" <redacted>
Create a helper routine that can return the cpu-frequency for the
corresponding pstate_id.
Also, cache the values of the pstate_max, pstate_min and
pstate_nominal and nr_pstates in a static structure so that they can
be reused in the future to perform any validations.
Signed-off-by: Gautham R. Shenoy <redacted>
---
drivers/cpufreq/powernv-cpufreq.c | 27 +++++++++++++++++++++++++++
1 file changed, 27 insertions(+)
From: Gautham R. Shenoy <hidden> Date: 2014-03-20 12:11:46
From: "Gautham R. Shenoy" <redacted>
The current frequency of a cpu is reported through the sysfs file
cpuinfo_cur_freq. This requires the driver to implement a
"->get(unsigned int cpu)" method which will return the current
operating frequency.
Implement a function named powernv_cpufreq_get() which reads the local
pstate from the PMSR and returns the corresponding frequency.
Set the powernv_cpufreq_driver.get hook to powernv_cpufreq_get().
Signed-off-by: Gautham R. Shenoy <redacted>
---
drivers/cpufreq/powernv-cpufreq.c | 38 ++++++++++++++++++++++++++++++++++++++
1 file changed, 38 insertions(+)
@@ -206,6 +206,43 @@ static inline void set_pmspr(unsigned long sprn, unsigned long val)BUG();}+/*+*Computesthecurrentfrequencyonthiscpu+*andstorestheresultin*ret_freq.+*/+staticvoidpowernv_read_cpu_freq(void*ret_freq)+{+unsignedlongpmspr_val;+s8local_pstate_id;+int*cur_freq,freq,pstate_id;++cur_freq=(int*)ret_freq;+pmspr_val=get_pmspr(SPRN_PMSR);++/* The local pstate id corresponds bits 48..55 in the PMSR.+*Note:Watchoutforthesign!*/+local_pstate_id=(pmspr_val>>48)&0xFF;+pstate_id=local_pstate_id;++freq=pstate_id_to_freq(pstate_id);+pr_debug("cpu %d pmsr %lx pstate_id %d frequency %d \n",+smp_processor_id(),pmspr_val,pstate_id,freq);+*cur_freq=freq;+}++/*+*Returnsthecpufrequencyasreportedbythefirmwarefor'cpu'.+*Thisvalueisreportedthroughthesysfsfilecpuinfo_cur_freq.+*/+unsignedintpowernv_cpufreq_get(unsignedintcpu)+{+intret_freq;++smp_call_function_any(cpu_sibling_mask(cpu),powernv_read_cpu_freq,+&ret_freq,1);+returnret_freq;+}+staticvoidset_pstate(void*pstate){unsignedlongval;
@@ -297,6 +334,7 @@ static int powernv_cpufreq_target(struct cpufreq_policy *policy,staticstructcpufreq_driverpowernv_cpufreq_driver={.verify=powernv_cpufreq_verify,.target=powernv_cpufreq_target,+.get=powernv_cpufreq_get,.init=powernv_cpufreq_cpu_init,.exit=powernv_cpufreq_cpu_exit,.name="powernv-cpufreq",
From: Gautham R Shenoy <hidden> Date: 2014-03-21 06:24:18
On Thu, Mar 20, 2014 at 05:40:57PM +0530, Gautham R. Shenoy wrote:
From: "Srivatsa S. Bhat" <redacted>
On POWER systems, the CPU frequency is controlled at a core-level and
hence we need to serialize so that only one of the threads in the core
switches the core's frequency at a time.
Using a global mutex lock would needlessly serialize _all_ frequency
transitions in the system (across all cores). So introduce per-core
locking to enable finer-grained synchronization and thereby enhance
the speed and responsiveness of the cpufreq driver to varying workload
demands.
The design of per-core locking is very simple and straight-forward: we
first define a Per-CPU lock and use the ones that belongs to the first
thread sibling of the core.
cpu_first_thread_sibling() macro is used to find the *common* lock for
all thread siblings belonging to a core.
Forgot to add the following line.
Reviewed-by: Preeti U Murthy <redacted>
@@ -24,8 +24,15 @@#include<linux/of.h>#include<asm/cputhreads.h>-/* FIXME: Make this per-core */-staticDEFINE_MUTEX(freq_switch_mutex);+/* Per-Core locking for frequency transitions */+staticDEFINE_PER_CPU(structmutex,freq_switch_lock);++#define lock_core_freq(cpu) \+mutex_lock(&per_cpu(freq_switch_lock,\+cpu_first_thread_sibling(cpu)));+#define unlock_core_freq(cpu) \+mutex_unlock(&per_cpu(freq_switch_lock,\+cpu_first_thread_sibling(cpu)));#define POWERNV_MAX_PSTATES 256
@@ -221,7 +228,7 @@ static int powernv_cpufreq_target(struct cpufreq_policy *policy,freqs.new=powernv_freqs[new_index].frequency;freqs.cpu=policy->cpu;-mutex_lock(&freq_switch_mutex);+lock_core_freq(policy->cpu);cpufreq_notify_transition(policy,&freqs,CPUFREQ_PRECHANGE);pr_debug("setting frequency for cpu %d to %d kHz index %d pstate %d",
@@ -233,7 +240,7 @@ static int powernv_cpufreq_target(struct cpufreq_policy *policy,rc=powernv_set_freq(policy->cpus,new_index);cpufreq_notify_transition(policy,&freqs,CPUFREQ_POSTCHANGE);-mutex_unlock(&freq_switch_mutex);+unlock_core_freq(policy->cpu);returnrc;}
@@ -250,7 +257,7 @@ static struct cpufreq_driver powernv_cpufreq_driver = {staticint__initpowernv_cpufreq_init(void){-intrc=0;+intcpu,rc=0;/* Discover pstates from device tree and init */
From: Gautham R Shenoy <hidden> Date: 2014-03-21 06:25:06
On Thu, Mar 20, 2014 at 05:40:58PM +0530, Gautham R. Shenoy wrote:
From: "Gautham R. Shenoy" <redacted>
Create a helper routine that can return the cpu-frequency for the
corresponding pstate_id.
Also, cache the values of the pstate_max, pstate_min and
pstate_nominal and nr_pstates in a static structure so that they can
be reused in the future to perform any validations.
Forgot to add the following line:
Reviewed-by: Preeti U Murthy [off-list ref]
From: Gautham R Shenoy <hidden> Date: 2014-03-21 06:25:29
On Thu, Mar 20, 2014 at 05:41:00PM +0530, Gautham R. Shenoy wrote:
From: "Gautham R. Shenoy" <redacted>
The current frequency of a cpu is reported through the sysfs file
cpuinfo_cur_freq. This requires the driver to implement a
"->get(unsigned int cpu)" method which will return the current
operating frequency.
Implement a function named powernv_cpufreq_get() which reads the local
pstate from the PMSR and returns the corresponding frequency.
Set the powernv_cpufreq_driver.get hook to powernv_cpufreq_get().
Forgot to add
Reviewed-by: Preeti U Murthy [off-list ref]
@@ -206,6 +206,43 @@ static inline void set_pmspr(unsigned long sprn, unsigned long val)BUG();}+/*+*Computesthecurrentfrequencyonthiscpu+*andstorestheresultin*ret_freq.+*/+staticvoidpowernv_read_cpu_freq(void*ret_freq)+{+unsignedlongpmspr_val;+s8local_pstate_id;+int*cur_freq,freq,pstate_id;++cur_freq=(int*)ret_freq;+pmspr_val=get_pmspr(SPRN_PMSR);++/* The local pstate id corresponds bits 48..55 in the PMSR.+*Note:Watchoutforthesign!*/+local_pstate_id=(pmspr_val>>48)&0xFF;+pstate_id=local_pstate_id;++freq=pstate_id_to_freq(pstate_id);+pr_debug("cpu %d pmsr %lx pstate_id %d frequency %d \n",+smp_processor_id(),pmspr_val,pstate_id,freq);+*cur_freq=freq;+}++/*+*Returnsthecpufrequencyasreportedbythefirmwarefor'cpu'.+*Thisvalueisreportedthroughthesysfsfilecpuinfo_cur_freq.+*/+unsignedintpowernv_cpufreq_get(unsignedintcpu)+{+intret_freq;++smp_call_function_any(cpu_sibling_mask(cpu),powernv_read_cpu_freq,+&ret_freq,1);+returnret_freq;+}+staticvoidset_pstate(void*pstate){unsignedlongval;
@@ -297,6 +334,7 @@ static int powernv_cpufreq_target(struct cpufreq_policy *policy,staticstructcpufreq_driverpowernv_cpufreq_driver={.verify=powernv_cpufreq_verify,.target=powernv_cpufreq_target,+.get=powernv_cpufreq_get,.init=powernv_cpufreq_cpu_init,.exit=powernv_cpufreq_cpu_exit,.name="powernv-cpufreq",
On Thu, Mar 20, 2014 at 5:40 PM, Gautham R. Shenoy
[off-list ref] wrote:
This is the v3 of the consolidated patchset consisting
patches for enabling cpufreq on IBM POWERNV platforms
along with some enhancements.
This is the first time I saw them. Looks like you never Cc'd linux-pm list.
Also, would be better to keep Maintainers in --to field so that they can
review them as soon as possible. Otherwise they might stay on lists for
a long time..
From: Gautham R Shenoy <hidden> Date: 2014-03-21 08:20:05
Hi Viresh,
On Fri, Mar 21, 2014 at 01:16:03PM +0530, Viresh Kumar wrote:
On Thu, Mar 20, 2014 at 5:40 PM, Gautham R. Shenoy
[off-list ref] wrote:
quoted
This is the v3 of the consolidated patchset consisting
patches for enabling cpufreq on IBM POWERNV platforms
along with some enhancements.
This is the first time I saw them. Looks like you never Cc'd linux-pm list.
Also, would be better to keep Maintainers in --to field so that they can
review them as soon as possible. Otherwise they might stay on lists for
a long time..
Yes, I hadn't Cc'ed linux-pm list last time around. Sorry about
that. Will keep this in mind the next time around. Also, your
suggestion regarding keeping the Maintainers in --to field is well
taken.
--
Thanks and Regards
gautham.
Probably we should remove SA1100's entry as well from here. This is
not the right way of doing it. Imagine 100 platforms having entries here.
If you want it, then select it from your platforms Kconfig.
@@ -54,3 +54,16 @@ config PPC_PASEMI_CPUFREQhelpThisaddsthesupportforfrequencyswitchingonPASemiPWRficientprocessors.++configPOWERNV_CPUFREQ+tristate"CPU frequency scaling for IBM POWERNV platform"+depends onPPC_POWERNV+selectCPU_FREQ_GOV_PERFORMANCE+selectCPU_FREQ_GOV_POWERSAVE+selectCPU_FREQ_GOV_USERSPACE+selectCPU_FREQ_GOV_ONDEMAND+selectCPU_FREQ_GOV_CONSERVATIVE
Nice :)
People normally do this from the defconfigs instead. And logically speaking
we might better have only dependencies here, isn't it? And obviously
governors aren't a dependency for this driver. :)
quoted hunk
+ default y+ help+ This adds support for CPU frequency switching on IBM POWERNV+ platform
+/* Helper routines */++/* Access helpers to power mgt SPR */++static inline unsigned long get_pmspr(unsigned long sprn)
Looks big enough not be inlined?
quoted hunk
+{+ switch (sprn) {+ case SPRN_PMCR:+ return mfspr(SPRN_PMCR);++ case SPRN_PMICR:+ return mfspr(SPRN_PMICR);++ case SPRN_PMSR:+ return mfspr(SPRN_PMSR);+ }+ BUG();+}++static inline void set_pmspr(unsigned long sprn, unsigned long val)+{
Same here..
quoted hunk
+ switch (sprn) {+ case SPRN_PMCR:+ mtspr(SPRN_PMCR, val);+ return;++ case SPRN_PMICR:+ mtspr(SPRN_PMICR, val);+ return;++ case SPRN_PMSR:+ mtspr(SPRN_PMSR, val);+ return;+ }+ BUG();+}++static void set_pstate(void *pstate)+{+ unsigned long val;+ unsigned long pstate_ul = *(unsigned long *) pstate;
Why not sending value only to this routine instead of pointer?
quoted hunk
++ val = get_pmspr(SPRN_PMCR);+ val = val & 0x0000ffffffffffffULL;
Maybe a blank line here?
+ /* Set both global(bits 56..63) and local(bits 48..55) PStates */
+ val = val | (pstate_ul << 56) | (pstate_ul << 48);
here as well?
quoted hunk
+ pr_debug("Setting cpu %d pmcr to %016lX\n", smp_processor_id(), val);+ set_pmspr(SPRN_PMCR, val);+}++static int powernv_set_freq(cpumask_var_t cpus, unsigned int new_index)+{+ unsigned long val = (unsigned long) powernv_pstate_ids[new_index];
I think automatic type conversion will happen here.
quoted hunk
++ /*+ * Use smp_call_function to send IPI and execute the+ * mtspr on target cpu. We could do that without IPI+ * if current CPU is within policy->cpus (core)+ */
Hmm, interesting I also feel there are cases where this routine can
get called from other CPUs. Can you list those use cases where it can
happen? Governors will mostly call this from one of the CPUs present
in policy->cpus.
quoted hunk
+ val = val & 0xFF;+ smp_call_function_any(cpus, set_pstate, &val, 1);+ return 0;+}++static int powernv_cpufreq_cpu_init(struct cpufreq_policy *policy)+{+ int base, i;++#ifdef CONFIG_SMP
What will break if you don't have this ifdef here? Without that as well
below code should work?
quoted hunk
+ base = cpu_first_thread_sibling(policy->cpu);++ for (i = 0; i < threads_per_core; i++)+ cpumask_set_cpu(base + i, policy->cpus);+#endif+ policy->cpuinfo.transition_latency = 25000;++ policy->cur = powernv_freqs[0].frequency;+ cpufreq_frequency_table_get_attr(powernv_freqs, policy->cpu);
Have you written this driver long time back? CPUFreq core has been
cleaned up heavily since last few kernel releases and I think there are
better helper routines available now.
quoted hunk
+}++static int powernv_cpufreq_cpu_exit(struct cpufreq_policy *policy)+{+ cpufreq_frequency_table_put_attr(policy->cpu);+ return 0;+}
You don't need this..
quoted hunk
+static int powernv_cpufreq_verify(struct cpufreq_policy *policy)+{+ return cpufreq_frequency_table_verify(policy, powernv_freqs);+}
use generic verify function pointer instead..
quoted hunk
+static int powernv_cpufreq_target(struct cpufreq_policy *policy,+ unsigned int target_freq,+ unsigned int relation)
On Thu, Mar 20, 2014 at 5:40 PM, Gautham R. Shenoy
[off-list ref] wrote:
From: "Srivatsa S. Bhat" <redacted>
On POWER systems, the CPU frequency is controlled at a core-level and
hence we need to serialize so that only one of the threads in the core
switches the core's frequency at a time.
On Thu, Mar 20, 2014 at 5:40 PM, Gautham R. Shenoy
[off-list ref] wrote:
quoted hunk
From: "Gautham R. Shenoy" <redacted>
Create a driver attribute named cpuinfo_nominal_freq which
creates a sysfs read-only file named cpuinfo_nominal_freq. Export
the frequency corresponding to the nominal_pstate through this
interface.
Nominal frequency is the highest non-turbo frequency for the
platform. This is generally used for setting governor policies from
user space for optimal energy efficiency.
Signed-off-by: Gautham R. Shenoy <redacted>
---
drivers/cpufreq/powernv-cpufreq.c | 22 ++++++++++++++++++++++
1 file changed, 22 insertions(+)
On Thu, Mar 20, 2014 at 5:41 PM, Gautham R. Shenoy
[off-list ref] wrote:
From: "Gautham R. Shenoy" <redacted>
The current frequency of a cpu is reported through the sysfs file
cpuinfo_cur_freq. This requires the driver to implement a
"->get(unsigned int cpu)" method which will return the current
operating frequency.
Implement a function named powernv_cpufreq_get() which reads the local
pstate from the PMSR and returns the corresponding frequency.
Set the powernv_cpufreq_driver.get hook to powernv_cpufreq_get().
Signed-off-by: Gautham R. Shenoy <redacted>
---
drivers/cpufreq/powernv-cpufreq.c | 38 ++++++++++++++++++++++++++++++++++++++
1 file changed, 38 insertions(+)
Please merge these fixups with the first patch which is creating the driver.
I understand that a different guy has created this patch and so wanted
to have a patch on his name but its really difficult to review this way.
Better add your signed-off in the first patch instead. Sending such changes
once the driver is mainlined looks fine.
@@ -206,6 +206,43 @@ static inline void set_pmspr(unsigned long sprn, unsigned long val)BUG();}+/*+*Computesthecurrentfrequencyonthiscpu+*andstorestheresultin*ret_freq.+*/+staticvoidpowernv_read_cpu_freq(void*ret_freq)+{+unsignedlongpmspr_val;+s8local_pstate_id;+int*cur_freq,freq,pstate_id;++cur_freq=(int*)ret_freq;
You don't need cur_freq variable at all..
quoted hunk
+ pmspr_val = get_pmspr(SPRN_PMSR);++ /* The local pstate id corresponds bits 48..55 in the PMSR.+ * Note: Watch out for the sign! */+ local_pstate_id = (pmspr_val >> 48) & 0xFF;+ pstate_id = local_pstate_id;
Move above print here after a blank line. Also remove freq variable as
well and use *cur_freq directly.. And then you can rename it to freq as well.
quoted hunk
+}++/*+ * Returns the cpu frequency as reported by the firmware for 'cpu'.+ * This value is reported through the sysfs file cpuinfo_cur_freq.+ */+unsigned int powernv_cpufreq_get(unsigned int cpu)+{+ int ret_freq;++ smp_call_function_any(cpu_sibling_mask(cpu), powernv_read_cpu_freq,+ &ret_freq, 1);+ return ret_freq;+}+ static void set_pstate(void *pstate) { unsigned long val;
1.8.3.1
--
To unsubscribe from this list: send the line "unsubscribe linux-pm" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Probably the use of ATTR_RO(cpuinfo_nominal_freq) and renaming
show_cpuinfo_nominal_freq to cpuinfo_nominal_freq_show() would be even
better. What do you think ?
From: Srivatsa S. Bhat <hidden> Date: 2014-03-21 09:56:35
On 03/21/2014 02:12 PM, Viresh Kumar wrote:
On Thu, Mar 20, 2014 at 5:40 PM, Gautham R. Shenoy
[off-list ref] wrote:
quoted
From: "Srivatsa S. Bhat" <redacted>
On POWER systems, the CPU frequency is controlled at a core-level and
hence we need to serialize so that only one of the threads in the core
switches the core's frequency at a time.
On 21 March 2014 15:25, Gautham R Shenoy [off-list ref] wrote:
Probably the use of ATTR_RO(cpuinfo_nominal_freq) and renaming
show_cpuinfo_nominal_freq to cpuinfo_nominal_freq_show() would be even
better. What do you think ?
Probably we should remove SA1100's entry as well from here. This is
not the right way of doing it. Imagine 100 platforms having entries here.
If you want it, then select it from your platforms Kconfig.
Sure. Will move these bits and the other governor related bits to the
Powernv Kconfig.
Good point. We might be better off exiting at this point.
quoted
+ pr_debug("NR PStates %d\n", nr_pstates);+ for (i = 0; i < nr_pstates; i++) {+ u32 id = be32_to_cpu(pstate_ids[i]);+ u32 freq = be32_to_cpu(pstate_freqs[i]);++ pr_debug("PState id %d freq %d MHz\n", id, freq);+ powernv_freqs[i].driver_data = i;
I don't think you are using this field at all and this is the field you can
use for driver_data and so you can get rid of powernv_pstate_ids[ ].
Using driver_data to record powernv_pstate_ids won't work since
powernv_pstate_ids can be negative. So a pstate_id -3 can be confused
with CPUFREQ_BOOST_FREQ thereby not displaying the frequency
corresponding to pstate id -3. So for now I think we will be retaining
powernv_pstate_ids.
quoted
+ powernv_freqs[i].frequency = freq * 1000; /* kHz */+ powernv_pstate_ids[i] = id;+ }+ /* End of list marker entry */+ powernv_freqs[i].driver_data = 0;
Not required.
Ok.
quoted
+ powernv_freqs[i].frequency = CPUFREQ_TABLE_END;++ /* Print frequency table */+ for (i = 0; powernv_freqs[i].frequency != CPUFREQ_TABLE_END; i++)+ pr_debug("%d: %d\n", i, powernv_freqs[i].frequency);
In this patch yes. But later patch introduces an additional attribute
for displaying the nominal frequency. Will handle that part in a clean
way in the next version.
quoted
+/* Helper routines */++/* Access helpers to power mgt SPR */++static inline unsigned long get_pmspr(unsigned long sprn)
Looks big enough not be inlined?
It is called from one function. It has been defined separately for
readability.
quoted
+{+ switch (sprn) {+ case SPRN_PMCR:+ return mfspr(SPRN_PMCR);++ case SPRN_PMICR:+ return mfspr(SPRN_PMICR);++ case SPRN_PMSR:+ return mfspr(SPRN_PMSR);+ }+ BUG();+}++static inline void set_pmspr(unsigned long sprn, unsigned long val)+{
Same here..
Same reason as above.
quoted
+ switch (sprn) {+ case SPRN_PMCR:+ mtspr(SPRN_PMCR, val);+ return;++ case SPRN_PMICR:+ mtspr(SPRN_PMICR, val);+ return;++ case SPRN_PMSR:+ mtspr(SPRN_PMSR, val);+ return;+ }+ BUG();+}++static void set_pstate(void *pstate)+{+ unsigned long val;+ unsigned long pstate_ul = *(unsigned long *) pstate;
Why not sending value only to this routine instead of pointer?
Well this function is called via an smp_call_function. so, cannot send
a value :(
quoted
++ val = get_pmspr(SPRN_PMCR);+ val = val & 0x0000ffffffffffffULL;
Maybe a blank line here?
Ok.
quoted
+ /* Set both global(bits 56..63) and local(bits 48..55) PStates */
+ val = val | (pstate_ul << 56) | (pstate_ul << 48);
here as well?
Ok.
quoted
+ pr_debug("Setting cpu %d pmcr to %016lX\n", smp_processor_id(), val);+ set_pmspr(SPRN_PMCR, val);+}++static int powernv_set_freq(cpumask_var_t cpus, unsigned int new_index)+{+ unsigned long val = (unsigned long) powernv_pstate_ids[new_index];
I think automatic type conversion will happen here.
Ok. Will fix this.
quoted
++ /*+ * Use smp_call_function to send IPI and execute the+ * mtspr on target cpu. We could do that without IPI+ * if current CPU is within policy->cpus (core)+ */
Hmm, interesting I also feel there are cases where this routine can
get called from other CPUs. Can you list those use cases where it can
happen? Governors will mostly call this from one of the CPUs present
in policy->cpus.
Consider the case when the governor is userspace and we are executing
# echo freqvalue >
/sys/devices/system/cpu/cpu<i>/cpufreq/scaling_setspeed
from a cpu <j> which is not in policy->cpus of cpu i.
quoted
+static int powernv_cpufreq_cpu_init(struct cpufreq_policy *policy)+{+ int base, i;++#ifdef CONFIG_SMP
What will break if you don't have this ifdef here? Without that as well
below code should work?
quoted
+ base = cpu_first_thread_sibling(policy->cpu);++ for (i = 0; i < threads_per_core; i++)+ cpumask_set_cpu(base + i, policy->cpus);+#endif+ policy->cpuinfo.transition_latency = 25000;++ policy->cur = powernv_freqs[0].frequency;+ cpufreq_frequency_table_get_attr(powernv_freqs, policy->cpu);
Have you written this driver long time back? CPUFreq core has been
cleaned up heavily since last few kernel releases and I think there are
better helper routines available now.
Yup it was written quite a while ago. And yeah, CPUFreq has changed
quite a bit since the last time I saw it :-)
quoted
+}++static int powernv_cpufreq_cpu_exit(struct cpufreq_policy *policy)+{+ cpufreq_frequency_table_put_attr(policy->cpu);+ return 0;+}
You don't need this..
Why not ?
quoted
+static int powernv_cpufreq_verify(struct cpufreq_policy *policy)+{+ return cpufreq_frequency_table_verify(policy, powernv_freqs);+}
use generic verify function pointer instead..
quoted
+static int powernv_cpufreq_target(struct cpufreq_policy *policy,+ unsigned int target_freq,+ unsigned int relation)
I guess it was to serialize accesses to PMCR. But Srivatsa's patch
converts this to a per-core lock which probably is no longer required
after your cpufreq_freq_transition_begin/end() patch series.
quoted
+ cpufreq_notify_transition(policy, &freqs, CPUFREQ_PRECHANGE);++ pr_debug("setting frequency for cpu %d to %d kHz index %d pstate %d",+ policy->cpu,+ powernv_freqs[new_index].frequency,+ new_index,+ powernv_pstate_ids[new_index]);++ rc = powernv_set_freq(policy->cpus, new_index);++ cpufreq_notify_transition(policy, &freqs, CPUFREQ_POSTCHANGE);+ mutex_unlock(&freq_switch_mutex);++ return rc;+}++static struct cpufreq_driver powernv_cpufreq_driver = {+ .verify = powernv_cpufreq_verify,+ .target = powernv_cpufreq_target,
I think you have Srivatsa there who has seen lots of cpufreq code and
could have helped you a lot :)
I don't think you are using this field at all and this is the field you can
use for driver_data and so you can get rid of powernv_pstate_ids[ ].
Using driver_data to record powernv_pstate_ids won't work since
powernv_pstate_ids can be negative. So a pstate_id -3 can be confused
with CPUFREQ_BOOST_FREQ thereby not displaying the frequency
corresponding to pstate id -3. So for now I think we will be retaining
powernv_pstate_ids.
As I said earlier, this field is only used by cpufreq drivers and cpufreq core
isn't supposed to touch it. CPUFREQ_BOOST_FREQ and other macros
are there for .frequency field and not this one.
quoted
quoted
+static int powernv_cpufreq_cpu_init(struct cpufreq_policy *policy)+{+ int base, i;++#ifdef CONFIG_SMP
What will break if you don't have this ifdef here? Without that as well
below code should work?
Missed this one?
quoted
quoted
+ base = cpu_first_thread_sibling(policy->cpu);++ for (i = 0; i < threads_per_core; i++)+ cpumask_set_cpu(base + i, policy->cpus);+#endif+ policy->cpuinfo.transition_latency = 25000;++ policy->cur = powernv_freqs[0].frequency;+ cpufreq_frequency_table_get_attr(powernv_freqs, policy->cpu);
Place these right after the routines without any blank lines in
between.
Is this the new convention ?
Don't know I have been following this since long time, probably from the
time I started with Mainline stuff.. I have seen many maintainers advising this
as it make code more readable, specially if these routines are quite big..
Probably it isn't mentioned in coding guidelines but people follow it most of
the times.
From: Gautham R Shenoy <hidden> Date: 2014-03-21 11:04:55
On Fri, Mar 21, 2014 at 03:01:29PM +0530, Viresh Kumar wrote:
On Thu, Mar 20, 2014 at 5:41 PM, Gautham R. Shenoy
[off-list ref] wrote:
quoted
From: "Gautham R. Shenoy" <redacted>
The current frequency of a cpu is reported through the sysfs file
cpuinfo_cur_freq. This requires the driver to implement a
"->get(unsigned int cpu)" method which will return the current
operating frequency.
Implement a function named powernv_cpufreq_get() which reads the local
pstate from the PMSR and returns the corresponding frequency.
Set the powernv_cpufreq_driver.get hook to powernv_cpufreq_get().
Signed-off-by: Gautham R. Shenoy <redacted>
---
drivers/cpufreq/powernv-cpufreq.c | 38 ++++++++++++++++++++++++++++++++++++++
1 file changed, 38 insertions(+)
Please merge these fixups with the first patch which is creating the driver.
I understand that a different guy has created this patch and so wanted
to have a patch on his name but its really difficult to review this
way.
Heh! Well, that wasn't the reason why this was sent out as a separate
patch, but never mind. Though I don't understand why it would be
difficult to review the patch though.
Better add your signed-off in the first patch instead. Sending such changes
once the driver is mainlined looks fine.
@@ -206,6 +206,43 @@ static inline void set_pmspr(unsigned long sprn, unsigned long val)BUG();}+/*+*Computesthecurrentfrequencyonthiscpu+*andstorestheresultin*ret_freq.+*/+staticvoidpowernv_read_cpu_freq(void*ret_freq)+{+unsignedlongpmspr_val;+s8local_pstate_id;+int*cur_freq,freq,pstate_id;++cur_freq=(int*)ret_freq;
You don't need cur_freq variable at all..
I don't like it either. But the compiler complains without this hack
:-(
quoted
+ pmspr_val = get_pmspr(SPRN_PMSR);++ /* The local pstate id corresponds bits 48..55 in the PMSR.+ * Note: Watch out for the sign! */+ local_pstate_id = (pmspr_val >> 48) & 0xFF;+ pstate_id = local_pstate_id;
similarly local_pstate_id
well, I am interested in the bits 48..55 of pmspr_val. That's the
pstate_id which can be negative. So I'll like to keep
local_pstate_id.
+static int powernv_cpufreq_cpu_init(struct cpufreq_policy *policy)+{+ int base, i;++#ifdef CONFIG_SMP
What will break if you don't have this ifdef here? Without that as well
below code should work?
Missed this one?
Nothing will break, its just that the code size will be a tiny bit
lesser on UP configs, that's all :-) Anyway, I think removing the ifdef
improves the readability (and doesn't add any noticeable overhead on UP
kernels), so let's get rid of it.
Regards,
Srivatsa S. Bhat
quoted
quoted
quoted
+ base = cpu_first_thread_sibling(policy->cpu);++ for (i = 0; i < threads_per_core; i++)+ cpumask_set_cpu(base + i, policy->cpus);+#endif+ policy->cpuinfo.transition_latency = 25000;++ policy->cur = powernv_freqs[0].frequency;+ cpufreq_frequency_table_get_attr(powernv_freqs, policy->cpu);
I think you have Srivatsa there who has seen lots of cpufreq code and
could have helped you a lot :)
:-)
I have followed the locking and synchronization aspects of cpufreq
closely, but unfortunately, I haven't been able to keep up with some of
the other details that well :-( Besides, its hard to keep up with the
rate of your changes, you are way too fast! ;-)
Regards,
Srivatsa S. Bhat
On 21 March 2014 16:34, Gautham R Shenoy [off-list ref] wrote:
Heh! Well, that wasn't the reason why this was sent out as a separate
patch, but never mind. Though I don't understand why it would be
difficult to review the patch though.
Because the initial driver wasn't complete earlier. There were 2-3 patches
after the first one which are changing what the first patch has added.
Nothing else :)
quoted
quoted
+static void powernv_read_cpu_freq(void *ret_freq)+{+ unsigned long pmspr_val;+ s8 local_pstate_id;+ int *cur_freq, freq, pstate_id;++ cur_freq = (int *)ret_freq;
You don't need cur_freq variable at all..
I don't like it either. But the compiler complains without this hack
:-(
Why would the compiler warn for doing this?:
*(int *)ret_freq = freq;
quoted
quoted
+ pmspr_val = get_pmspr(SPRN_PMSR);++ /* The local pstate id corresponds bits 48..55 in the PMSR.+ * Note: Watch out for the sign! */+ local_pstate_id = (pmspr_val >> 48) & 0xFF;+ pstate_id = local_pstate_id;
similarly local_pstate_id
well, I am interested in the bits 48..55 of pmspr_val. That's the
pstate_id which can be negative. So I'll like to keep
local_pstate_id.
Can you please explain at bit level how getting the value in a s8
first and then into a s32 will help you here? Instead of getting it
directly into s32.
On 21 March 2014 17:15, Srivatsa S. Bhat
[off-list ref] wrote:
quoted
I think you have Srivatsa there who has seen lots of cpufreq code and
could have helped you a lot :)
:-)
I was waiting for your reply here :)
I have followed the locking and synchronization aspects of cpufreq
closely, but unfortunately, I haven't been able to keep up with some of
the other details that well :-( Besides, its hard to keep up with the
rate of your changes, you are way too fast! ;-)
From: Gautham R Shenoy <hidden> Date: 2014-03-21 12:31:16
On Fri, Mar 21, 2014 at 12:01:07PM +0000, David Laight wrote:
From: Viresh Kumar
quoted
On 21 March 2014 16:34, Gautham R Shenoy [off-list ref] wrote:
quoted
Heh! Well, that wasn't the reason why this was sent out as a separate
patch, but never mind. Though I don't understand why it would be
difficult to review the patch though.
Because the initial driver wasn't complete earlier. There were 2-3 patches
after the first one which are changing what the first patch has added.
Nothing else :)
quoted
quoted
quoted
+static void powernv_read_cpu_freq(void *ret_freq)+{+ unsigned long pmspr_val;+ s8 local_pstate_id;+ int *cur_freq, freq, pstate_id;++ cur_freq = (int *)ret_freq;
You don't need cur_freq variable at all..
I don't like it either. But the compiler complains without this hack
:-(
Why would the compiler warn for doing this?:
*(int *)ret_freq = freq;
Because it is very likely to be wrong.
In general casts of pointers to integer types are dangerous.
In this case why not make the function return the value?
Because this function is called via an smp_call_function(). And we
need a way of returning the value to the caller.
From: Gautham R Shenoy <hidden> Date: 2014-03-21 13:05:00
On Fri, Mar 21, 2014 at 05:15:34PM +0530, Viresh Kumar wrote:
On 21 March 2014 16:34, Gautham R Shenoy [off-list ref] wrote:
quoted
Heh! Well, that wasn't the reason why this was sent out as a separate
patch, but never mind. Though I don't understand why it would be
difficult to review the patch though.
Because the initial driver wasn't complete earlier. There were 2-3 patches
after the first one which are changing what the first patch has added.
Nothing else :)
quoted
quoted
quoted
+static void powernv_read_cpu_freq(void *ret_freq)+{+ unsigned long pmspr_val;+ s8 local_pstate_id;+ int *cur_freq, freq, pstate_id;++ cur_freq = (int *)ret_freq;
You don't need cur_freq variable at all..
I don't like it either. But the compiler complains without this hack
:-(
Why would the compiler warn for doing this?:
*(int *)ret_freq = freq;
The compiler doesn't complain if I do this.
quoted
quoted
quoted
+ pmspr_val = get_pmspr(SPRN_PMSR);++ /* The local pstate id corresponds bits 48..55 in the PMSR.+ * Note: Watch out for the sign! */+ local_pstate_id = (pmspr_val >> 48) & 0xFF;+ pstate_id = local_pstate_id;
similarly local_pstate_id
well, I am interested in the bits 48..55 of pmspr_val. That's the
pstate_id which can be negative. So I'll like to keep
local_pstate_id.
Can you please explain at bit level how getting the value in a s8
first and then into a s32 will help you here? Instead of getting it
directly into s32.
Consider the case when pmspr = 0x00feffffffffffff;
We are interested in extracting the value 'fe'. And ensure that when
we store this value into an int, we get the sign extension right.
So the following doesn't work:
pstate_id = (pmspr_val >> 48) & 0xFFFFFFFF;
Since we get pstate_id = 0x000000fe, which is not the same as
0xfffffffe.
Of course, we could do the following, but I wasn't sure if
two levels of type casting helped on the readability front.
pstate_id = (int) ((s8)((pmspr_val >> 48) & 0xFF));
--
Thanks and Regards
gautham.
On 21 March 2014 18:34, Gautham R Shenoy [off-list ref] wrote:
Consider the case when pmspr = 0x00feffffffffffff;
We are interested in extracting the value 'fe'. And ensure that when
we store this value into an int, we get the sign extension right.
So the following doesn't work:
pstate_id = (pmspr_val >> 48) & 0xFFFFFFFF;
What about pstate_id = (pmspr_val >> 48) & 0xFF; ??
I don't think you are using this field at all and this is the field you can
use for driver_data and so you can get rid of powernv_pstate_ids[ ].
Using driver_data to record powernv_pstate_ids won't work since
powernv_pstate_ids can be negative. So a pstate_id -3 can be confused
with CPUFREQ_BOOST_FREQ thereby not displaying the frequency
corresponding to pstate id -3. So for now I think we will be retaining
powernv_pstate_ids.
As I said earlier, this field is only used by cpufreq drivers and cpufreq core
isn't supposed to touch it. CPUFREQ_BOOST_FREQ and other macros
are there for .frequency field and not this one.
Ok, I had based my code on linus's git tree. I checked the 'pm-cpufreq'
branch of Rafael's 'linux-pm' tree and freq_table.c contains the
following code snippet in show_available_frequencies:
if (show_boost ^ (table[i].driver_data == CPUFREQ_BOOST_FREQ))
continue;
I suspect we're talking about different code bases. So could you
please tell me which one should I be looking at ?
quoted
quoted
quoted
+static int powernv_cpufreq_cpu_init(struct cpufreq_policy *policy)+{+ int base, i;++#ifdef CONFIG_SMP
What will break if you don't have this ifdef here? Without that as well
below code should work?
Missed this one?
quoted
quoted
quoted
+ base = cpu_first_thread_sibling(policy->cpu);++ for (i = 0; i < threads_per_core; i++)+ cpumask_set_cpu(base + i, policy->cpus);+#endif+ policy->cpuinfo.transition_latency = 25000;++ policy->cur = powernv_freqs[0].frequency;+ cpufreq_frequency_table_get_attr(powernv_freqs, policy->cpu);
Place these right after the routines without any blank lines in
between.
Is this the new convention ?
Don't know I have been following this since long time, probably from the
time I started with Mainline stuff.. I have seen many maintainers advising this
as it make code more readable, specially if these routines are quite big..
Probably it isn't mentioned in coding guidelines but people follow it most of
the times.
On 21 March 2014 18:53, Gautham R Shenoy [off-list ref] wrote:
Ok, I had based my code on linus's git tree. I checked the 'pm-cpufreq'
Always check his bleeding-edge or linux-next branch.
branch of Rafael's 'linux-pm' tree and freq_table.c contains the
following code snippet in show_available_frequencies:
if (show_boost ^ (table[i].driver_data == CPUFREQ_BOOST_FREQ))
continue;
I suspect we're talking about different code bases. So could you
please tell me which one should I be looking at ?
Okay, there is some problem here. I will check how can I simplify this..
And yes, you were correct.
quoted
Because cpufreq_frequency_table_get_attr() and
cpufreq_frequency_table_put_attr() don't exist anymore :)
Well, it does in the codebases that I was looking at. May be I've been
looking at the wrong place.
From: Gautham R Shenoy <hidden> Date: 2014-03-21 14:26:04
On Fri, Mar 21, 2014 at 06:42:50PM +0530, Viresh Kumar wrote:
On 21 March 2014 18:34, Gautham R Shenoy [off-list ref] wrote:
quoted
Consider the case when pmspr = 0x00feffffffffffff;
We are interested in extracting the value 'fe'. And ensure that when
we store this value into an int, we get the sign extension right.
So the following doesn't work:
pstate_id = (pmspr_val >> 48) & 0xFFFFFFFF;
What about pstate_id = (pmspr_val >> 48) & 0xFF; ??
Nope.
Suppose the pmspr_val is contained in the register
%rax, and pstate_id corresponds to the address -20(%rbp) then:
pstate_id = (pmspr_val >> 48) & 0xFF;
would corrspond to
shrq $48, %rax // Left shift by 48 bits
andl $255, %eax // Mask the lower 32 bits of %rax with 0x000000FF
movl %eax, -20(%rbp) // Store the lower 32 bits of %rax
into pstate_id
On the other hand,
pstate_id = (int)((s8)((pmspr_val >> 48) & 0xFF));
would correspond to:
shrq $48, %rax // Left shift by 48 bits.
movsbl %al, %eax // Move the lower 8 bits of %rax to %eax
with sign-extension.
movl %eax, -20(%rbp) // store the result in pstate_id;
So with this, we are getting the sign extension due to the use of movsbl.
And if local_pstate_id corresponds to the address -1(%rbp) then:
local_pstate_id = (pmspr_val >> 48) & 0xFF;
pstate_id = local_pstate_id;
would correspond to:
shrq $48, %rax // Left shift by 48 bits
movb %al, -1(%rbp) //copy the lower 8 bits to local_pstate_id
movsbl -1(%rbp), %eax //move the contents of
local_pstate_id to %eax with sign extension.
movl %eax, -20(%rbp) // Store the result in pstate_id
Hope this helps :-)
--
Thanks and Regards
gautham.
Probably we should remove SA1100's entry as well from here. This is
not the right way of doing it. Imagine 100 platforms having entries here.
If you want it, then select it from your platforms Kconfig.
Sure. Will move these bits and the other governor related bits to the
Powernv Kconfig.
Good point. We might be better off exiting at this point.
Yes, we could return here. We do not generally come till this point
if the platform has a problem discovering PStates from device tree.
But there is no useful debug info after this point if nr_pstates is 0.
quoted
quoted
+ pr_debug("NR PStates %d\n", nr_pstates);+ for (i = 0; i < nr_pstates; i++) {+ u32 id = be32_to_cpu(pstate_ids[i]);+ u32 freq = be32_to_cpu(pstate_freqs[i]);++ pr_debug("PState id %d freq %d MHz\n", id, freq);+ powernv_freqs[i].driver_data = i;
I don't think you are using this field at all and this is the field you can
use for driver_data and so you can get rid of powernv_pstate_ids[ ].
Using driver_data to record powernv_pstate_ids won't work since
powernv_pstate_ids can be negative. So a pstate_id -3 can be confused
with CPUFREQ_BOOST_FREQ thereby not displaying the frequency
corresponding to pstate id -3. So for now I think we will be retaining
powernv_pstate_ids.
Yeah, I had the driver written using driver_data to store pstates.
Gautham found the bug that we are missing one PState when we match the
ID with CPUFREQ_BOOST_FREQ!
We did not know that you have taken care of those issues. Ideally
I did expect that driver_data should not be touched by the framework.
Thanks for fixing that and allowing the back-end driver to use
driver_data.
quoted
quoted
+ powernv_freqs[i].frequency = freq * 1000; /* kHz */+ powernv_pstate_ids[i] = id;+ }+ /* End of list marker entry */+ powernv_freqs[i].driver_data = 0;
Not required.
Ok.
quoted
quoted
+ powernv_freqs[i].frequency = CPUFREQ_TABLE_END;++ /* Print frequency table */+ for (i = 0; powernv_freqs[i].frequency != CPUFREQ_TABLE_END; i++)+ pr_debug("%d: %d\n", i, powernv_freqs[i].frequency);
In this patch yes. But later patch introduces an additional attribute
for displaying the nominal frequency. Will handle that part in a clean
way in the next version.
quoted
quoted
+/* Helper routines */++/* Access helpers to power mgt SPR */++static inline unsigned long get_pmspr(unsigned long sprn)
Looks big enough not be inlined?
It is called from one function. It has been defined separately for
readability.
Let the compiler decide. The code is straight forward :)
I wanted to keep this SPR operations in a separate function to
facilitate debug and also introduce any timing/sequence change here if
required. Keeping this separate is helpful, if inlining is
successful, we get a bonus :)
quoted
quoted
+{+ switch (sprn) {+ case SPRN_PMCR:+ return mfspr(SPRN_PMCR);++ case SPRN_PMICR:+ return mfspr(SPRN_PMICR);++ case SPRN_PMSR:+ return mfspr(SPRN_PMSR);+ }+ BUG();+}++static inline void set_pmspr(unsigned long sprn, unsigned long val)+{
Same here..
Same reason as above.
quoted
quoted
+ switch (sprn) {+ case SPRN_PMCR:+ mtspr(SPRN_PMCR, val);+ return;++ case SPRN_PMICR:+ mtspr(SPRN_PMICR, val);+ return;++ case SPRN_PMSR:+ mtspr(SPRN_PMSR, val);+ return;+ }+ BUG();+}++static void set_pstate(void *pstate)+{+ unsigned long val;+ unsigned long pstate_ul = *(unsigned long *) pstate;
Why not sending value only to this routine instead of pointer?
Well this function is called via an smp_call_function. so, cannot send
a value :(
quoted
quoted
++ val = get_pmspr(SPRN_PMCR);+ val = val & 0x0000ffffffffffffULL;
Maybe a blank line here?
Ok.
quoted
quoted
+ /* Set both global(bits 56..63) and local(bits 48..55) PStates */
+ val = val | (pstate_ul << 56) | (pstate_ul << 48);
here as well?
Ok.
quotedquoted
quoted
+ pr_debug("Setting cpu %d pmcr to %016lX\n", smp_processor_id(), val);+ set_pmspr(SPRN_PMCR, val);+}++static int powernv_set_freq(cpumask_var_t cpus, unsigned int new_index)+{+ unsigned long val = (unsigned long) powernv_pstate_ids[new_index];
I think automatic type conversion will happen here.
Ok. Will fix this.
Most of the conversions are verbose mainly to help readability of the
required sign-extensions. There is scope to make these concise.
quoted
quoted
++ /*+ * Use smp_call_function to send IPI and execute the+ * mtspr on target cpu. We could do that without IPI+ * if current CPU is within policy->cpus (core)+ */
Hmm, interesting I also feel there are cases where this routine can
get called from other CPUs. Can you list those use cases where it can
happen? Governors will mostly call this from one of the CPUs present
in policy->cpus.
Consider the case when the governor is userspace and we are executing
# echo freqvalue >
/sys/devices/system/cpu/cpu<i>/cpufreq/scaling_setspeed
from a cpu <j> which is not in policy->cpus of cpu i.
quoted
quoted
+static int powernv_cpufreq_cpu_init(struct cpufreq_policy *policy)+{+ int base, i;++#ifdef CONFIG_SMP
What will break if you don't have this ifdef here? Without that as well
below code should work?
quoted
+ base = cpu_first_thread_sibling(policy->cpu);++ for (i = 0; i < threads_per_core; i++)+ cpumask_set_cpu(base + i, policy->cpus);+#endif+ policy->cpuinfo.transition_latency = 25000;++ policy->cur = powernv_freqs[0].frequency;+ cpufreq_frequency_table_get_attr(powernv_freqs, policy->cpu);
Have you written this driver long time back? CPUFreq core has been
cleaned up heavily since last few kernel releases and I think there are
better helper routines available now.
Yup it was written quite a while ago. And yeah, CPUFreq has changed
quite a bit since the last time I saw it :-)
Yes, the driver is more than a year old and based on even older
implementation that I had written. I kept up until I got a compiler
warning or functional issue. Definitely could not catch-up with your
cleanups :)
quoted
quoted
+}++static int powernv_cpufreq_cpu_exit(struct cpufreq_policy *policy)+{+ cpufreq_frequency_table_put_attr(policy->cpu);+ return 0;+}
You don't need this..
Why not ?
quoted
quoted
+static int powernv_cpufreq_verify(struct cpufreq_policy *policy)+{+ return cpufreq_frequency_table_verify(policy, powernv_freqs);+}
use generic verify function pointer instead..
quoted
+static int powernv_cpufreq_target(struct cpufreq_policy *policy,+ unsigned int target_freq,+ unsigned int relation)
I guess it was to serialize accesses to PMCR. But Srivatsa's patch
converts this to a per-core lock which probably is no longer required
after your cpufreq_freq_transition_begin/end() patch series.
Right. Frequency transitions are per-core, the h/w SPRs are per-core.
We need to prevent threads from colliding on h/w SPR access. We do
make the lock per-core later in the series as mentioned above.
Gautham has addressed most comments.
Thanks,
Vaidy
From: Gautham R Shenoy <hidden> Date: 2014-03-21 14:55:07
On Fri, Mar 21, 2014 at 04:24:27PM +0530, Viresh Kumar wrote:
quoted
quoted
quoted
+static int powernv_cpufreq_cpu_init(struct cpufreq_policy *policy)+{+ int base, i;++ base = cpu_first_thread_sibling(policy->cpu);++ for (i = 0; i < threads_per_core; i++)+ cpumask_set_cpu(base + i, policy->cpus);+ policy->cpuinfo.transition_latency = 25000;++ policy->cur = powernv_freqs[0].frequency;+ cpufreq_frequency_table_get_attr(powernv_freqs, policy->cpu);
This doesn't exist anymore.
Ok, I guess the right thing to do at this point is call
cpufreq_table_validate_and_show(policy, powernv_freqs);
Will fix the code to take care of this.
--
Thanks and Regards
gautham.
On 21 March 2014 17:31, David Laight [off-list ref] wrote:
quoted
quoted
*(int *)ret_freq =3D freq;
Because it is very likely to be wrong.
In general casts of pointers to integer types are dangerous.
=20
Where are we converting pointers to integers? We are doing a
cast from 'void * ' to 'int *' and then using indirection operator
to set its value.
You mis-parsed what I wrote, try:
In general casts of 'pointer to integer' types are dangerous.
Somewhere, much higher up the call stack, the address of an integer
variable is being taken and then passed as the 'void *' parameter.
The 'problem' is that it is quite easily to pass the address of
a 'long' instead. On 32bit and LE systems this won't always
be a problem. On 64bit BE it all goes wrong.
David
From: Benjamin Herrenschmidt <benh@kernel.crashing.org> Date: 2014-03-21 22:57:17
On Fri, 2014-03-21 at 16:34 +0530, Gautham R Shenoy wrote:
quoted
quoted
+/*+ * Computes the current frequency on this cpu+ * and stores the result in *ret_freq.+ */+static void powernv_read_cpu_freq(void *ret_freq)+{+ unsigned long pmspr_val;+ s8 local_pstate_id;+ int *cur_freq, freq, pstate_id;++ cur_freq = (int *)ret_freq;
You don't need cur_freq variable at all..
I don't like it either. But the compiler complains without this hack
:-(
Casting integers into void * is a recipe for disaster... what is that
supposed to be about ? We lose all type checking and get exposed
to endian issues etc... the day somebody uses a different type on both
sides.
Also is "freq" a frequency ? In this case an int isn't big enough.
Cheers,
Ben.
On 21 March 2014 20:18, Vaidyanathan Srinivasan
[off-list ref] wrote:
Yeah, I had the driver written using driver_data to store pstates.
Gautham found the bug that we are missing one PState when we match the
ID with CPUFREQ_BOOST_FREQ!
I see..
We did not know that you have taken care of those issues. Ideally
I did expect that driver_data should not be touched by the framework.
Thanks for fixing that and allowing the back-end driver to use
driver_data.
No, I haven't fixed anything yet. And this piece of code still exists.
I will see if I can get this fixed, by that time you can continue the
way your code is there in this version.
On 21 March 2014 20:24, Gautham R Shenoy [off-list ref] wrote:
Ok, I guess the right thing to do at this point is call
cpufreq_table_validate_and_show(policy, powernv_freqs);
Will fix the code to take care of this.
From: Gautham R Shenoy <hidden> Date: 2014-03-22 07:54:07
Hi Ben,
On Sat, Mar 22, 2014 at 09:56:30AM +1100, Benjamin Herrenschmidt wrote:
On Fri, 2014-03-21 at 16:34 +0530, Gautham R Shenoy wrote:
quoted
quoted
quoted
+/*+ * Computes the current frequency on this cpu+ * and stores the result in *ret_freq.+ */+static void powernv_read_cpu_freq(void *ret_freq)+{+ unsigned long pmspr_val;+ s8 local_pstate_id;+ int *cur_freq, freq, pstate_id;++ cur_freq = (int *)ret_freq;
You don't need cur_freq variable at all..
I don't like it either. But the compiler complains without this hack
:-(
Casting integers into void * is a recipe for disaster... what is that
supposed to be about ?
Like I mentioned elsewhere on this thread, we're calling
powernv_read_cpu_freq via an smp_call_function(). We use this to
obtain the frequency on the cpu where powernv_read_cpu_freq
executes and return it to the caller of smp_call_function.
We lose all type checking and get exposed
to endian issues etc... the day somebody uses a different type on both
sides.
Yes, I understand the problem now. I'll think of a safer way to pass
the return value.
Also is "freq" a frequency ? In this case an int isn't big enough.
freq is the frequency stored in the cpufreq_table. The value is in
kHz. So, int should be big enough.