Intel Hardware P-States (HWP) support
v3 cover Intel Hardware P-States (HWP) support
Hi,
Resending since I messed up the To: line. Sorry about that.
This patch series adds Hardware-Controlled Performance States (HWP) for Intel processors to Xen.
v2 was only partially reviewed, so v3 is mostly a reposting of v2. In v2 & v3, I think I addressed all comments for v1. I kept patch 11 "xenpm:
Factor out a non-fatal cpuid_parse variant", with a v2 comment explaining why I keep it.
v3 adds "xen/x86: Tweak PDC bits when using HWP". Qubes testing revealed an issue where enabling HWP can crash firwmare code (maybe SMM). This requires a Linux change to get the PDC bits from Xen and pass them to ACPI. Roger has a patch [0] to set the PDC bits. Roger's 3 patch series was tested with "xen/x86: Tweak PDC bits when using HWP" on affected hardware and allowed proper operation.
Previous cover letter:
With HWP, the processor makes its own determinations for frequency selection, though users can set some parameters and preferences. There is also Turbo Boost which dynamically pushes the max frequency if possible.
The existing governors don't work with HWP since they select frequencies and HWP doesn't expose those. Therefore a dummy hwp-interal governor is used that doesn't do anything.
xenpm get-cpufreq-para is extended to show HWP parameters, and set-cpufreq-hwp is added to set them.
A lightly loaded OpenXT laptop showed ~1W power savings according to powertop. A mostly idle Fedora system (dom0 only) showed a more modest power savings.
This for for a 10th gen 6-core 1600 MHz base 4900 MHZ max cpu. In the default balance mode, Turbo Boost doesn't exceed 4GHz. Tweaking the energy_perf preference with xenpm set-cpufreq-hwp balance ene:64, I've seen the CPU hit 4.7GHz before throttling down and bouncing around between 4.3 and 4.5 GHz. Curiously the other cores read ~4GHz when turbo boost takes affect. This was done after pinning all dom0 cores, and using taskset to pin to vCPU/pCPU 11 and running a bash tightloop.
HWP defaults to disabled and running with the existing HWP configuration
- it doesn't reconfigure by default. It can be enabled with cpufreq=xen:hwp.
Hardware Duty Cycling (HDC) is another feature to autonomously powerdown things. It defaults to enabled when HWP is enabled, but HDC can be disabled on the command line. cpufreq=xen:hwp,no-hdc
I've only tested on 8th gen and 10th gen systems with activity window and energy_perf support. So the pathes for CPUs lacking those features are untested.
Fast MSR support was removed in v2. The model specific checking was not done properly, and I don't have hardware to test with. Since writes are expected to be infrequent, I just removed the code.
This changes the systcl_pm_op hypercall, so that wants review.
Regards,
Jason
[0] https://lore.kernel.org/xen-devel/[email protected]/
Jason Andryuk (14):
cpufreq: Allow restricting to internal governors only
cpufreq: Add perf_freq to cpuinfo
cpufreq: Export intel_feature_detect
cpufreq: Add Hardware P-State (HWP) driver
xenpm: Change get-cpufreq-para output for internal xen/x86: Tweak PDC bits when using HWP
cpufreq: Export HWP parameters to userspace
libxc: Include hwp_para in definitions
xenpm: Print HWP parameters
xen: Add SET_CPUFREQ_HWP xen_sysctl_pm_op
libxc: Add xc_set_cpufreq_hwp
xenpm: Factor out a non-fatal cpuid_parse variant
xenpm: Add set-cpufreq-hwp subcommand
CHANGELOG: Add Intel HWP entry
CHANGELOG.md | 1 + docs/misc/xen-command-line.pandoc | 8 +- tools/include/xenctrl.h | 6 + tools/libs/ctrl/xc_pm.c | 18 + tools/misc/xenpm.c | 355 +++++++++++- xen/arch/x86/acpi/cpufreq/Makefile | 1 + xen/arch/x86/acpi/cpufreq/cpufreq.c | 15 +- xen/arch/x86/acpi/cpufreq/hwp.c | 633 ++++++++++++++++++++++ xen/arch/x86/acpi/lib.c | 5 + xen/arch/x86/cpu/mcheck/mce_intel.c | 6 + xen/arch/x86/include/asm/cpufeature.h | 13 +- xen/arch/x86/include/asm/msr-index.h | 14 + xen/drivers/acpi/pmstat.c | 23 + xen/drivers/cpufreq/cpufreq.c | 40 ++ xen/drivers/cpufreq/utility.c | 1 + xen/include/acpi/cpufreq/cpufreq.h | 14 + xen/include/acpi/cpufreq/processor_perf.h | 4 + xen/include/acpi/pdc_intel.h | 1 + xen/include/public/sysctl.h | 57 ++ 19 files changed, 1187 insertions(+), 28 deletions(-) create mode 100644 xen/arch/x86/acpi/cpufreq/hwp.c
Signature · 1 line
2.40.0
PATCH RESEND v3 1/14 cpufreq: Allow restricting to internal governors only
For hwp, the standard governors are not usable, and only the internal one is applicable. Add the cpufreq_governor_internal boolean to indicate when an internal governor, like hwp-internal, will be used. This is set during presmp_initcall, so that it can suppress governor registration during initcall. Only a governor with a name containing "-internal" will be allowed in that case.
This way, the unuseable governors are not registered, so the internal one is the only one returned to userspace. This means incompatible governors won't be advertised to userspace.
---
v3:
Switch to initdata
Add Jan Acked-by
Commit message s/they/the/ typo
Don't register hwp-internal when running non-hwp - Marek
v2:
Switch to "-internal"
Add blank line in header
--- xen/drivers/cpufreq/cpufreq.c | 8 ++++++++ xen/include/acpi/cpufreq/cpufreq.h | 2 ++ 2 files changed, 10 insertions(+)
xen/drivers/cpufreq/cpufreq.c +8 -0
@@ -56,6 +56,7 @@ struct cpufreq_dom { };static LIST_HEAD_READ_MOSTLY (cpufreq_dom_list_head); +bool __initdata cpufreq_governor_internal;struct cpufreq_governor *__read_mostly cpufreq_opt_governor;LIST_HEAD_READ_MOSTLY (cpufreq_governor_list);
@@ -121,6 +122,13 @@ int __init cpufreq_register_governor(struct cpufreq_governor *governor)if (!governor)return -EINVAL ; +if (cpufreq_governor_internal && +strstr (governor->name,"-internal" ) ==NULL ) +return -EINVAL ; + +if (!cpufreq_governor_internal &&strstr (governor->name,"-internal" )) +return -EINVAL ; +if (__find_governor (governor->name) !=NULL )return -EEXIST ;
xen/include/acpi/cpufreq/cpufreq.h +2 -0
@@ -114,6 +114,8 @@ extern struct cpufreq_governor cpufreq_gov_userspace;extern struct cpufreq_governor cpufreq_gov_performance;extern struct cpufreq_governor cpufreq_gov_powersave; +extern bool cpufreq_governor_internal; +extern struct list_head cpufreq_governor_list;extern int cpufreq_register_governor (struct cpufreq_governor *governor);
Signature · 1 line
2.40.0
PATCH RESEND v3 2/14 cpufreq: Add perf_freq to cpuinfo
In reply to Jason Andryukacpi-cpufreq scales the aperf/mperf measurements by max_freq, but HWP needs to scale by base frequency. Settings max_freq to base_freq "works" but the code is not obvious, and returning values to userspace is tricky. Add an additonal perf_freq member which is used for scaling aperf/mperf measurements.
---
v3:
Add Jan's Ack
I don't like this, but it seems the best way to re-use the common aperf/mperf code. The other option would be to add wrappers that then do the acpi vs. hwp scaling.
--- xen/arch/x86/acpi/cpufreq/cpufreq.c | 2 +- xen/drivers/cpufreq/utility.c | 1 + xen/include/acpi/cpufreq/cpufreq.h | 3 +++ 3 files changed, 5 insertions(+), 1 deletion(-)
xen/arch/x86/acpi/cpufreq/cpufreq.c +1 -1
@@ -316,7 +316,7 @@ unsigned int get_measured_perf(unsigned int cpu, unsigned int flag)else perf_percent =0 ; -return policy->cpuinfo.max_freq * perf_percent /100 ; +return policy->cpuinfo.perf_freq * perf_percent /100 ; } static unsigned int cf_check get_cur_freq_on_cpu(unsigned int cpu)
xen/drivers/cpufreq/utility.c +1 -0
@@ -236,6 +236,7 @@ int cpufreq_frequency_table_cpuinfo(struct cpufreq_policy *policy, policy->min = policy->cpuinfo.min_freq = min_freq; policy->max = policy->cpuinfo.max_freq = max_freq; + policy->cpuinfo.perf_freq = max_freq; policy->cpuinfo.second_max_freq = second_max_freq;if (policy->min == ~0 )
xen/include/acpi/cpufreq/cpufreq.h +3 -0
@@ -37,6 +37,9 @@ extern struct acpi_cpufreq_data *cpufreq_drv_data[NR_CPUS];struct cpufreq_cpuinfo {unsigned int max_freq;unsigned int second_max_freq;/* P1 if Turbo Mode is on */ +unsigned int perf_freq;/* Scaling freq for aperf/mpref. +acpi-cpufreq uses max_freq, but HWP uses +base_freq.*/ unsigned int min_freq;unsigned int transition_latency;/* in 10^(-9) s = nanoseconds */ };
Signature · 1 line
2.40.0
PATCH RESEND v3 3/14 cpufreq: Export intel_feature_detect
In reply to Jason AndryukExport feature_detect as intel_feature_detect so it can be re-used by HWP.
---
v3:
Remove void * cast when calling intel_feature_detect
v2:
export intel_feature_detect with typed pointer
Move intel_feature_detect to acpi/cpufreq/cpufreq.h since the declaration now contains struct cpufreq_policy *.
--- xen/arch/x86/acpi/cpufreq/cpufreq.c | 8 ++++++-- xen/include/acpi/cpufreq/cpufreq.h | 2 ++ 2 files changed, 8 insertions(+), 2 deletions(-)
xen/arch/x86/acpi/cpufreq/cpufreq.c +6 -2
@@ -339,9 +339,8 @@ static unsigned int cf_check get_cur_freq_on_cpu(unsigned int cpu)return extract_freq (get_cur_val (cpumask_of (cpu)), data); } -static void cf_check feature_detect(void *info) +void intel_feature_detect (struct cpufreq_policy *policy) { -struct cpufreq_policy *policy = info;unsigned int eax; eax =cpuid_eax (6 );
@@ -353,6 +352,11 @@ static void cf_check feature_detect(void *info) } } +static void cf_check feature_detect(void *info) +{ +intel_feature_detect (info); +} +static unsigned int check_freqs (const cpumask_t *mask,unsigned int freq,struct acpi_cpufreq_data *data) {
xen/include/acpi/cpufreq/cpufreq.h +2 -0
@@ -243,4 +243,6 @@ int write_userspace_scaling_setspeed(unsigned int cpu, unsigned int freq);void cpufreq_dbs_timer_suspend (void );void cpufreq_dbs_timer_resume (void ); +void intel_feature_detect (struct cpufreq_policy *policy); +#endif /* __XEN_CPUFREQ_PM_H__ */
Signature · 1 line
2.40.0
Re: [PATCH v3 03/14 RESEND] cpufreq: Export intel_feature_detect
Quoted 4 lines · Jason Andryuk
Export
feature_detectasintel_feature_detectso it can be re-used by HWP.Signed-off-by Jason Andryuk <[email protected]>
PATCH RESEND v3 4/14 cpufreq: Add Hardware P-State (HWP) driver
In reply to Jason AndryukFrom the Intel SDM: "Hardware-Controlled Performance States (HWP), which autonomously selects performance states while utilizing OS supplied performance guidance hints."
Enable HWP to run in autonomous mode by poking the correct MSRs. cpufreq=xen:hwp enables and cpufreq=xen:hwp=0 disables. The same for hdc.
There is no interface to configure - xen_sysctl_pm_op/xenpm will be to be extended to configure in subsequent patches. It will run with the default values, which should be the default 0x80 (out
of 0x0-0xff) energy/performance preference.
Unscientific powertop measurement of an mostly idle, customized OpenXT install:
A 10th gen 6-core laptop showed battery discharge drop from ~9.x to ~7.x watts.
A 8th gen 4-core laptop dropped from ~10 to ~9
Power usage depends on many factors, especially display brightness, but this does show an power saving in balanced mode when CPU utilization is low.
HWP isn't compatible with an external governor - it doesn't take explicit frequency requests. Therefore a minimal internal governor, hwp-internal, is also added as a placeholder.
While adding to the xen-command-line.pandoc entry, un-nest verbose from minfreq. They are independent.
---
We disable on cpuid_level < 0x16. cpuid(0x16) is used to get the cpu frequencies for calculating the APERF/MPERF. Without it, things would still work, but the averge cpufrequency output would be wrong.
My 8th & 10th gen test systems both report:
(XEN) HWP: 1 notify: 1 act_window: 1 energy_perf: 1 pkg_level: 0 peci: 0 (XEN) HWP: Hardware Duty Cycling (HDC) supported
(XEN) HWP: HW_FEEDBACK not supported
IA32_ENERGY_PERF_BIAS has not been tested.
For cpufreq=xen:hwp, placing the option inside the governor wouldn't work. Users would have to select the hwp-internal governor to turn off hwp support. hwp-internal isn't usable without hwp, and users wouldn't be able to select a different governor. That doesn't matter while hwp defaults off, but it would if or when hwp defaults to enabled.
We can't use parse_boolean() since it requires a single name=val string and cpufreq_handle_common_option is provided two strings. Use parse_bool() and manual handle no-hwp.
Write to disable the interrupt - the linux pstate driver does this. We don't use the interrupts, so we can just turn them off. We aren't ready to handle them, so we don't want any. Unclear if this is necessary. SDM says it's default disabled.
FAST_IA32_HWP_REQUEST was removed in v2. The check in v1 was wrong, it's a model specific feature and the CPUID bit is only available after enabling via the MSR. Support was untested since I don't have hardware with the feature. Writes are expected to be infrequent, so just leave it out.
---
v2:
Alphabetize headers
Re-work driver registration
name hwp_drv_data anonymous union "hw"
Drop hwp_verbose_cont
style cleanups
Condense hwp_governor switchhwp_cpufreq_target remove .raw from hwp_req assignment Use typed-pointer in a few functions
Pass type to xzalloc
Add HWP_ENERGY_PERF_BALANCE/IA32_ENERGY_BIAS_BALANCE defines Add XEN_HWP_GOVERNOR define for "hwp-internal" Capitalize CPUID and MSR defines
Change '_' to '-' for energy-perf & act-window Read-modify-write MSRs updates
Use FAST_IA32_HWP_REQUEST_MSR_ENABLE define
constify pointer in hwp_set_misc_turbo
Add space after non-fallthrough break in governor switch Add IA32_ENERGY_BIAS_MASK define
Check CPUID_PM_LEAK for energy bias when needed
Fail initialization with curr_req = -1
Fold hwp_read_capabilities into hwp_init_msrs
Add command line cpufreq=xen:hwp
Add command line cpufreq=xen:hdc
Use per_cpu for hwp_drv_data pointers
Move hwp_energy_perf_bias call into hwp_write_request energy_perf 0 is valid, so hwp_energy_perf_bias cannot be skipped Ensure we don't generate interrupts
Remove Fast Write of Uncore MSR
Initialize hwp_drv_data from curr_req
Use SPDX line instead of license text in hwp.c
v3:
Add cf_check to cpufreq_gov_hwp_init() - Marek
Print cpuid_level with %#x - Marek
--- docs/misc/xen-command-line.pandoc | 8 +- xen/arch/x86/acpi/cpufreq/Makefile | 1 + xen/arch/x86/acpi/cpufreq/cpufreq.c | 5 +- xen/arch/x86/acpi/cpufreq/hwp.c | 506 ++++++++++++++++++++++ xen/arch/x86/include/asm/cpufeature.h | 13 +- xen/arch/x86/include/asm/msr-index.h | 13 + xen/drivers/cpufreq/cpufreq.c | 32 ++ xen/include/acpi/cpufreq/cpufreq.h | 3 + xen/include/acpi/cpufreq/processor_perf.h | 3 + xen/include/public/sysctl.h | 1 + 10 files changed, 581 insertions(+), 4 deletions(-) create mode 100644 xen/arch/x86/acpi/cpufreq/hwp.c
docs/misc/xen-command-line.pandoc +7 -1
@@ -499,7 +499,7 @@ If set, force use of the performance counters for oprofile, rather than detectin available support. ### cpufreq -> `= none | {{ <boolean> | xen } [:[powersave|performance|ondemand|userspace][,<maxfreq>][,[<minfreq>][,[verbose]]]]} | dom0-kernel` +> `= none | {{ <boolean> | xen } [:[powersave|performance|ondemand|userspace][,<hdc>][,[<hwp>]][,[<maxfreq>]][,[<minfreq>]][,[verbose]]]} | dom0-kernel` > Default: `xen`
@@ -510,6 +510,12 @@ choice of `dom0-kernel` is deprecated and not supported by all Dom0 kernels. * `<maxfreq>` and `<minfreq>` are integers which represent max and min processor frequencies respectively. * `verbose` option can be included as a string or also as `verbose=<integer>` +* `<hwp>` is a boolean to enable Hardware-Controlled Performance States (HWP) + on supported Intel hardware. HWP is a Skylake+ feature which provides better + CPU power management. The default is disabled. +* `<hdc>` is a boolean to enable Hardware Duty Cycling (HDC). HDC enables the + processor to autonomously force physical package components into idle state. + The default is enabled, but the option only applies when `<hwp>` is enabled. ### cpuid (x86) > `= List of comma separated booleans`
xen/arch/x86/acpi/cpufreq/Makefile +1 -0
@@ -1,2 +1,3 @@ obj-y += cpufreq.o +obj-y += hwp.o obj-y += powernow.o
xen/arch/x86/acpi/cpufreq/cpufreq.c +4 -1
@@ -642,7 +642,10 @@ static int __init cf_check cpufreq_driver_init(void)switch ( boot_cpu_data.x86_vendor ) {case X86_VENDOR_INTEL : - ret =cpufreq_register_driver (&acpi_cpufreq_driver); +if (hwp_available () ) + ret =hwp_register_driver (); +else + ret =cpufreq_register_driver (&acpi_cpufreq_driver);break ;case X86_VENDOR_AMD :
xen/arch/x86/acpi/cpufreq/hwp.c new file +506 -0
506 lines not on this page · raw message
xen/arch/x86/include/asm/cpufeature.h +11 -2
@@ -46,8 +46,17 @@ extern struct cpuinfo_x86 boot_cpu_data;#define cpu_has (c, bit) test_bit(bit, (c)->x86_capability)#define boot_cpu_has (bit) test_bit(bit, boot_cpu_data.x86_capability) -#define CPUID_PM_LEAF 6 -#define CPUID6_ECX_APERFMPERF_CAPABILITY 0x1 +#define CPUID_PM_LEAF 6 +#define CPUID6_EAX_HWP (_AC(1, U) << 7) +#define CPUID6_EAX_HWP_NOTIFICATION (_AC(1, U) << 8) +#define CPUID6_EAX_HWP_ACTIVITY_WINDOW (_AC(1, U) << 9) +#define CPUID6_EAX_HWP_ENERGY_PERFORMANCE_PREFERENCE (_AC(1, U) << 10) +#define CPUID6_EAX_HWP_PACKAGE_LEVEL_REQUEST (_AC(1, U) << 11) +#define CPUID6_EAX_HDC (_AC(1, U) << 13) +#define CPUID6_EAX_HWP_PECI (_AC(1, U) << 16) +#define CPUID6_EAX_HW_FEEDBACK (_AC(1, U) << 19) +#define CPUID6_ECX_APERFMPERF_CAPABILITY 0x1 +#define CPUID6_ECX_IA32_ENERGY_PERF_BIAS 0x8/* CPUID level 0x00000001.edx */ #define cpu_has_fpu 1
xen/arch/x86/include/asm/msr-index.h +13 -0
@@ -151,6 +151,13 @@#define MSR_PKRS 0x000006e1 +#define MSR_IA32_PM_ENABLE 0x00000770 +#define IA32_PM_ENABLE_HWP_ENABLE (_AC(1, ULL) << 0) + +#define MSR_IA32_HWP_CAPABILITIES 0x00000771 +#define MSR_IA32_HWP_INTERRUPT 0x00000773 +#define MSR_IA32_HWP_REQUEST 0x00000774 +#define MSR_X2APIC_FIRST 0x00000800#define MSR_X2APIC_LAST 0x000008ff
@@ -165,6 +172,11 @@#define PASID_PASID_MASK 0x000fffff#define PASID_VALID (_AC(1, ULL) << 31) +#define MSR_IA32_PKG_HDC_CTL 0x00000db0 +#define IA32_PKG_HDC_CTL_HDC_PKG_ENABLE (_AC(1, ULL) << 0) +#define MSR_IA32_PM_CTL1 0x00000db1 +#define IA32_PM_CTL1_HDC_ALLOW_BLOCK (_AC(1, ULL) << 0) +#define MSR_UARCH_MISC_CTRL 0x00001b01#define UARCH_CTRL_DOITM (_AC(1, ULL) << 0)
@@ -500,6 +512,7 @@#define MSR_IA32_MISC_ENABLE_LIMIT_CPUID (1<<22)#define MSR_IA32_MISC_ENABLE_XTPR_DISABLE (1<<23)#define MSR_IA32_MISC_ENABLE_XD_DISABLE (1ULL << 34) +#define MSR_IA32_MISC_ENABLE_TURBO_DISENGAGE (1ULL << 38)#define MSR_IA32_TSC_DEADLINE 0x000006E0#define MSR_IA32_ENERGY_PERF_BIAS 0x000001b0
xen/drivers/cpufreq/cpufreq.c +32 -0
@@ -565,6 +565,38 @@ static void cpufreq_cmdline_common_para(struct cpufreq_policy *new_policy)static int __init cpufreq_handle_common_option (const char *name,const char *val) { +if (!strcmp (name,"hdc" )) { +if (val) { +int ret =parse_bool (val,NULL ); +if (ret !=-1 ) { + opt_cpufreq_hdc = ret; +return 1 ; + } + }else { + opt_cpufreq_hdc = true; +return 1 ; + } + }else if (!strcmp (name,"no-hdc" )) { + opt_cpufreq_hdc = false; +return 1 ; + } + +if (!strcmp (name,"hwp" )) { +if (val) { +int ret =parse_bool (val,NULL ); +if (ret !=-1 ) { + opt_cpufreq_hwp = ret; +return 1 ; + } + }else { + opt_cpufreq_hwp = true; +return 1 ; + } + }else if (!strcmp (name,"no-hwp" )) { + opt_cpufreq_hwp = false; +return 1 ; + } +if (!strcmp (name,"maxfreq" ) && val) { usr_max_freq =simple_strtoul (val,NULL ,0 );return 1 ;
xen/include/acpi/cpufreq/cpufreq.h +3 -0
@@ -245,4 +245,7 @@ void cpufreq_dbs_timer_resume(void);void intel_feature_detect (struct cpufreq_policy *policy); +extern bool opt_cpufreq_hwp; +extern bool opt_cpufreq_hdc; +#endif /* __XEN_CPUFREQ_PM_H__ */
xen/include/acpi/cpufreq/processor_perf.h +3 -0
@@ -7,6 +7,9 @@#define XEN_PX_INIT 0x80000000 +bool hwp_available (void ); +int hwp_register_driver (void ); +int powernow_cpufreq_init (void );unsigned int powernow_register_driver (void );unsigned int get_measured_perf (unsigned int cpu,unsigned int flag);
xen/include/public/sysctl.h +1 -0
@@ -292,6 +292,7 @@ struct xen_ondemand {uint32_t up_threshold; }; +#define XEN_HWP_GOVERNOR "hwp-internal"/* * cpufreq para name of this structure named * same as sysfs file name of native linux
Signature · 1 line
2.40.0
Re: [PATCH v3 04/14 RESEND] cpufreq: Add Hardware P-State (HWP) driver
Quoted 3 lines · Jason Andryuk
For cpufreq=xen:hwp, placing the option inside the governor wouldn't work. Users would have to select the hwp-internal governor to turn off hwp support.
I'm afraid I don't understand this, and you'll find a comment towards this further down. Even when ...
Quoted 3 lines
hwp-internal isn't usable without hwp, and users wouldn't
be able to select a different governor. That doesn't matter while hwp defaults off, but it would if or when hwp defaults to enabled.
... it starts defaulting to enabled, selecting another governor can simply have the side effect of turning off hwp.
Quoted 4 lines
Write to disable the interrupt - the linux pstate driver does this. We don't use the interrupts, so we can just turn them off. We aren't ready to handle them, so we don't want any. Unclear if this is necessary. SDM says it's default disabled.
Definitely better to be on the safe side.
docs/misc/xen-command-line.pandoc If set, force use of the performance counters for oprofile, rather than detectin · line 502
Quoted 8 lines
docs/misc/xen-command-line.pandoc +1
-1@@ -499,7 +499,7 @@ If set, force use of the performance counters for oprofile, rather than detectin available support. ### cpufreq -> `= none | {{ <boolean> | xen } [:[powersave|performance|ondemand|userspace][,<maxfreq>][,[<minfreq>][,[verbose]]]]} | dom0-kernel` +> `= none | {{ <boolean> | xen } [:[powersave|performance|ondemand|userspace][,<hdc>][,[<hwp>]][,[<maxfreq>]][,[<minfreq>]][,[verbose]]]} | dom0-kernel`
Considering you use a special internal governor, the 4 governor alternatives are meaningless for hwp. Hence at the command line level recognizing "hwp" as if it was another governor name would seem better to me. This would then also get rid of one of the two special "no-" prefix parsing cases (which I'm not overly happy about).
Even if not done that way I'm puzzled by the way you spell out the interaction of "hwp" and "hdc": As you say in the description, "hdc" is meaningful only when "hwp" was specified, so even if not merged with the governors group "hwp" should come first, and "hdc" ought to be rejected if "hwp" wasn't first specified. (The way you've spelled it out it actually looks to be kind of the other way around.)
Strictly speaking "maxfreq" and "minfreq" also should be objected to when "hwp" was specified.
Overall I'm getting the impression that beyond your "verbose" related adjustment more is needed, if you're meaning to get things closer to how we parse the option (splitting across multiple lines to help see what I mean):
`= none
| {{ <boolean> | xen } [:{powersave|performance|ondemand|userspace}
[{,hwp[,hdc]|[,maxfreq=<maxfreq>[,minfreq=<minfreq>]}]
[,verbose]]}| dom0-kernel`
(We're still parsing in a more relaxed way, e.g. minfreq may come ahead of maxfreq, but better be more tight in the doc than too relaxed.)
Furthermore while max/min freq don't apply directly, there are still two MSRs controlling bounds at the package and logical processor levels.
Quoted 16 lines
xen/arch/x86/acpi/cpufreq/hwp.c new file +13
-0@@ -0,0 +1,506 @@ +/* SPDX-License-Identifier: GPL-2.0 */ +/* +* hwp.c cpufreq driver to run Intel Hardware P-States (HWP) +* +* Copyright (C) 2021 Jason Andryuk <[email protected]> +*/ + +#include <xen/cpumask.h> +#include <xen/init.h> +#include <xen/param.h> +#include <xen/xmalloc.h> +#include <asm/io.h> +#include <asm/msr.h>
xen/arch/x86/acpi/cpufreq/hwp.c line 23
Quoted 10 lines
xen/arch/x86/acpi/cpufreq/hwp.c new file +10
-0+#include <acpi/cpufreq/cpufreq.h> + +static bool feature_hwp; +static bool feature_hwp_notification; +static bool feature_hwp_activity_window; +static bool feature_hwp_energy_perf; +static bool feature_hwp_pkg_level_ctl; +static bool feature_hwp_peci; + +static bool feature_hdc;
Most (all?) of these want to be __ro_after_init, I expect.
xen/arch/x86/acpi/cpufreq/hwp.c line 26
Quoted 2 lines
xen/arch/x86/acpi/cpufreq/hwp.c new file +2
-0+__initdata bool opt_cpufreq_hwp = false; +__initdata bool opt_cpufreq_hdc = true;
Nit (style): Please put annotations after the type.
Quoted 11 lines
xen/arch/x86/acpi/cpufreq/hwp.c new file +11
-0+#define HWP_ENERGY_PERF_BALANCE 0x80 +#define IA32_ENERGY_BIAS_BALANCE 0x7 +#define IA32_ENERGY_BIAS_MAX_POWERSAVE 0xf +#define IA32_ENERGY_BIAS_MASK 0xf + +union hwp_request +{ +struct + { +uint64_t min_perf:8 ; +uint64_t max_perf:8 ;
xen/arch/x86/acpi/cpufreq/hwp.c line 48
Quoted 10 lines
xen/arch/x86/acpi/cpufreq/hwp.c new file +10
-0+ uint64_t desired:8; + uint64_t energy_perf:8; + uint64_t activity_window:10; + uint64_t package_control:1; + uint64_t reserved:16; + uint64_t activity_window_valid:1; + uint64_t energy_perf_valid:1; + uint64_t desired_valid:1; + uint64_t max_perf_valid:1; + uint64_t min_perf_valid:1;
The boolean fields here would probably better be of type "bool". I also don't see the need for using uint64_t for any of the other fields - unsigned int will be quite fine, I think. Only ...
xen/arch/x86/acpi/cpufreq/hwp.c line 50
Quoted 2 lines
xen/arch/x86/acpi/cpufreq/hwp.c new file +2
-0+ }; +uint64_t raw;
... this wants to keep this type. (Same again below then.)
Quoted 45 lines
xen/arch/x86/acpi/cpufreq/hwp.c new file +45
-0+bool __init hwp_available (void ) +{ +unsigned int eax, ecx, unused; +bool use_hwp; + +if ( boot_cpu_data.cpuid_level <CPUID_PM_LEAF ) + { +hwp_verbose ("cpuid_level (%#x) lacks HWP support\n" , + boot_cpu_data.cpuid_level); +return false; + } + +if ( boot_cpu_data.cpuid_level <0x16 ) + { +hwp_info ("HWP disabled: cpuid_level %#x < 0x16 lacks CPU freq info\n" , + boot_cpu_data.cpuid_level); +return false; + } + +cpuid (CPUID_PM_LEAF , &eax, &unused, &ecx, &unused); + +if ( !(eax &CPUID6_EAX_HWP_ENERGY_PERFORMANCE_PREFERENCE ) && + !(ecx &CPUID6_ECX_IA32_ENERGY_PERF_BIAS ) ) + { +hwp_verbose ("HWP disabled: No energy/performance preference available" ); +return false; + } + + feature_hwp = eax &CPUID6_EAX_HWP ; + feature_hwp_notification = eax &CPUID6_EAX_HWP_NOTIFICATION ; + feature_hwp_activity_window = eax &CPUID6_EAX_HWP_ACTIVITY_WINDOW ; + feature_hwp_energy_perf = + eax &CPUID6_EAX_HWP_ENERGY_PERFORMANCE_PREFERENCE ; + feature_hwp_pkg_level_ctl = eax &CPUID6_EAX_HWP_PACKAGE_LEVEL_REQUEST ; + feature_hwp_peci = eax &CPUID6_EAX_HWP_PECI ; + +hwp_verbose ("HWP: %d notify: %d act-window: %d energy-perf: %d pkg-level: %d peci: %d\n" , + feature_hwp, feature_hwp_notification, + feature_hwp_activity_window, feature_hwp_energy_perf, + feature_hwp_pkg_level_ctl, feature_hwp_peci); + +if ( !feature_hwp ) +return false; + + feature_hdc = eax &CPUID6_EAX_HDC ;
xen/arch/x86/acpi/cpufreq/hwp.c line 174
Quoted 10 lines
xen/arch/x86/acpi/cpufreq/hwp.c new file +10
-0+ +hwp_verbose ("HWP: Hardware Duty Cycling (HDC) %ssupported%s\n" , + feature_hdc ?"" :"not " , + feature_hdc ? opt_cpufreq_hdc ?", enabled" :", disabled" + :"" ); + + feature_hdc = feature_hdc && opt_cpufreq_hdc; + +hwp_verbose ("HWP: HW_FEEDBACK %ssupported\n" , + (eax &CPUID6_EAX_HW_FEEDBACK ) ?"" :"not " );
You report this, but you don't really use it?
xen/arch/x86/acpi/cpufreq/hwp.c line 176
Quoted 1 line
xen/arch/x86/acpi/cpufreq/hwp.c new file +1
-0+ use_hwp = feature_hwp && opt_cpufreq_hwp;
There's a lot of output you may produce until you make it here, which is largely meaningless when opt_cpufreq_hwp == false. Is there a reason you don't check that flag first thing in the function?
Quoted 29 lines
xen/arch/x86/acpi/cpufreq/hwp.c new file +29
-0+static void hdc_set_pkg_hdc_ctl (bool val) +{ +uint64_t msr; + +if (rdmsr_safe (MSR_IA32_PKG_HDC_CTL , msr) ) + { +hwp_err ("error rdmsr_safe(MSR_IA32_PKG_HDC_CTL)\n" ); + +return ; + } + +if ( val ) + msr |=IA32_PKG_HDC_CTL_HDC_PKG_ENABLE ; +else + msr &= ~IA32_PKG_HDC_CTL_HDC_PKG_ENABLE ; + +if (wrmsr_safe (MSR_IA32_PKG_HDC_CTL , msr) ) +hwp_err ("error wrmsr_safe(MSR_IA32_PKG_HDC_CTL): %016lx\n" , msr); +} + +static void hdc_set_pm_ctl1 (bool val) +{ +uint64_t msr; + +if (rdmsr_safe (MSR_IA32_PM_CTL1 , msr) ) + { +hwp_err ("error rdmsr_safe(MSR_IA32_PM_CTL1)\n" ); + +return ;
xen/arch/x86/acpi/cpufreq/hwp.c line 223
Quoted 10 lines
xen/arch/x86/acpi/cpufreq/hwp.c new file +10
-0+ } + +if ( val ) + msr |=IA32_PM_CTL1_HDC_ALLOW_BLOCK ; +else + msr &= ~IA32_PM_CTL1_HDC_ALLOW_BLOCK ; + +if (wrmsr_safe (MSR_IA32_PM_CTL1 , msr) ) +hwp_err ("error wrmsr_safe(MSR_IA32_PM_CTL1): %016lx\n" , msr); +}
For both functions: Elsewhere you also log the affected CPU in hwp_err(). Without this I'm not convinced the logging here is very useful. In fact I wonder whether hwp_err() shouldn't take care of this and/or the "error" part of the string literal. A HWP: prefix might also not be bad ...
xen/arch/x86/acpi/cpufreq/hwp.c line 237
Quoted 13 lines
xen/arch/x86/acpi/cpufreq/hwp.c new file +13
-0+static void hwp_get_cpu_speeds (struct cpufreq_policy *policy) +{ +uint32_t base_khz, max_khz, bus_khz, edx; + +cpuid (0x16 , &base_khz, &max_khz, &bus_khz, &edx); + +/* aperf/mperf scales base. */ + policy->cpuinfo.perf_freq = base_khz *1000 ; + policy->cpuinfo.min_freq = base_khz *1000 ; + policy->cpuinfo.max_freq = max_khz *1000 ; + policy->min = base_khz *1000 ; + policy->max = max_khz *1000 ; + policy->cur =0 ;
What is the comment intended to be telling me here?
Quoted 40 lines
xen/arch/x86/acpi/cpufreq/hwp.c new file +40
-0+static void cf_check hwp_init_msrs(void *info) +{ +struct cpufreq_policy *policy = info; +struct hwp_drv_data *data =this_cpu (hwp_drv_data); +uint64_t val; + +/* +* Package level MSR, but we don't have a good idea of packages here, so +* just do it everytime. +*/ +if (rdmsr_safe (MSR_IA32_PM_ENABLE , val) ) + { +hwp_err ("CPU%u: error rdmsr_safe(MSR_IA32_PM_ENABLE)\n" , policy->cpu); + data->curr_req.raw =-1 ; +return ; + } + +/* Ensure we don't generate interrupts */ +if ( feature_hwp_notification ) +wrmsr_safe (MSR_IA32_HWP_INTERRUPT ,0 ); + +hwp_verbose ("CPU%u: MSR_IA32_PM_ENABLE: %016lx\n" , policy->cpu, val); +if ( !(val &IA32_PM_ENABLE_HWP_ENABLE ) ) + { + val |=IA32_PM_ENABLE_HWP_ENABLE ; +if (wrmsr_safe (MSR_IA32_PM_ENABLE , val) ) + { +hwp_err ("CPU%u: error wrmsr_safe(MSR_IA32_PM_ENABLE, %lx)\n" , + policy->cpu, val); + data->curr_req.raw =-1 ; +return ; + } + } + +if (rdmsr_safe (MSR_IA32_HWP_CAPABILITIES , data->hwp_caps) ) + { +hwp_err ("CPU%u: error rdmsr_safe(MSR_IA32_HWP_CAPABILITIES)\n" , + policy->cpu); + data->curr_req.raw =-1 ; +return ;
xen/arch/x86/acpi/cpufreq/hwp.c line 289
Quoted 10 lines
xen/arch/x86/acpi/cpufreq/hwp.c new file +10
-0+ } + +if (rdmsr_safe (MSR_IA32_HWP_REQUEST , data->curr_req.raw) ) + { +hwp_err ("CPU%u: error rdmsr_safe(MSR_IA32_HWP_REQUEST)\n" , policy->cpu); + data->curr_req.raw =-1 ; +return ; + } + +if ( !feature_hwp_energy_perf ) {
Nit: Brace placement.
xen/arch/x86/acpi/cpufreq/hwp.c line 299
Quoted 10 lines
xen/arch/x86/acpi/cpufreq/hwp.c new file +10
-0+if (rdmsr_safe (MSR_IA32_ENERGY_PERF_BIAS , val) ) + { +hwp_err ("error rdmsr_safe(MSR_IA32_ENERGY_PERF_BIAS)\n" ); + data->curr_req.raw =-1 ; + +return ; + } + + data->energy_perf = val &IA32_ENERGY_BIAS_MASK ; + }
In order to not need to undo the "enable" you've already done, maybe that should move down here? With all the sanity checking you do here, maybe you should also check that the write of the enable bit actually took effect?
Quoted 59 lines
xen/arch/x86/acpi/cpufreq/hwp.c new file +59
-0+/* val 0 - highest performance, 15 - maximum energy savings */ +static void hwp_energy_perf_bias (const struct hwp_drv_data *data) +{ +uint64_t msr; +uint8_t val = data->energy_perf; + +ASSERT (val <=IA32_ENERGY_BIAS_MAX_POWERSAVE ); + +if (rdmsr_safe (MSR_IA32_ENERGY_PERF_BIAS , msr) ) + { +hwp_err ("error rdmsr_safe(MSR_IA32_ENERGY_PERF_BIAS)\n" ); + +return ; + } + + msr &= ~IA32_ENERGY_BIAS_MASK ; + msr |= val; + +if (wrmsr_safe (MSR_IA32_ENERGY_PERF_BIAS , msr) ) +hwp_err ("error wrmsr_safe(MSR_IA32_ENERGY_PERF_BIAS): %016lx\n" , msr); +} + +static void cf_check hwp_write_request(void *info) +{ +struct cpufreq_policy *policy = info; +struct hwp_drv_data *data =this_cpu (hwp_drv_data); +union hwp_request hwp_req = data->curr_req; + +BUILD_BUG_ON (sizeof (union hwp_request ) !=sizeof (uint64_t )); +if (wrmsr_safe (MSR_IA32_HWP_REQUEST , hwp_req.raw) ) + { +hwp_err ("CPU%u: error wrmsr_safe(MSR_IA32_HWP_REQUEST, %lx)\n" , + policy->cpu, hwp_req.raw); +rdmsr_safe (MSR_IA32_HWP_REQUEST , data->curr_req.raw); + } + +if ( !feature_hwp_energy_perf ) +hwp_energy_perf_bias (data); + +} + +static int cf_check hwp_cpufreq_target(struct cpufreq_policy *policy, +unsigned int target_freq, +unsigned int relation) +{ +unsigned int cpu = policy->cpu; +struct hwp_drv_data *data =per_cpu (hwp_drv_data, cpu); +/* Zero everything to ensure reserved bits are zero... */ +union hwp_request hwp_req = { .raw =0 }; + +/* .. and update from there */ + hwp_req.min_perf = data->minimum; + hwp_req.max_perf = data->maximum; + hwp_req.desired = data->desired; +if ( feature_hwp_energy_perf ) + hwp_req.energy_perf = data->energy_perf; +if ( feature_hwp_activity_window ) + hwp_req.activity_window = data->activity_window; +
xen/arch/x86/acpi/cpufreq/hwp.c line 409
Quoted 10 lines
xen/arch/x86/acpi/cpufreq/hwp.c new file +10
-0+if ( hwp_req.raw == data->curr_req.raw ) +return 0 ; + + data->curr_req = hwp_req; + +hwp_verbose ("CPU%u: wrmsr HWP_REQUEST %016lx\n" , cpu, hwp_req.raw); +on_selected_cpus (cpumask_of (cpu), hwp_write_request, policy,1 ); + +return 0 ; +}
If I'm not mistaken these 3 functions can only be reached from the user space tool (via set_cpufreq_para()). On that path I don't think there should be any hwp_err(); definitely not in non-verbose mode. Instead it would be good if a sensible error code could be reported back. (Same then for hwp_cpufreq_update() and its helper.)
Quoted 7 lines
xen/arch/x86/include/asm/cpufeature.h +0
-1@@ -46,8 +46,17 @@ extern struct cpuinfo_x86 boot_cpu_data;#define cpu_has (c, bit) test_bit(bit, (c)->x86_capability)#define boot_cpu_has (bit) test_bit(bit, boot_cpu_data.x86_capability) -#define CPUID_PM_LEAF 6
xen/arch/x86/include/asm/cpufeature.h extern struct cpuinfo_x86 boot_cpu_data; · line 57
Quoted 10 lines
xen/arch/x86/include/asm/cpufeature.h +9
-1-#define CPUID6_ECX_APERFMPERF_CAPABILITY 0x1 +#define CPUID_PM_LEAF 6 +#define CPUID6_EAX_HWP (_AC(1, U) << 7) +#define CPUID6_EAX_HWP_NOTIFICATION (_AC(1, U) << 8) +#define CPUID6_EAX_HWP_ACTIVITY_WINDOW (_AC(1, U) << 9) +#define CPUID6_EAX_HWP_ENERGY_PERFORMANCE_PREFERENCE (_AC(1, U) << 10) +#define CPUID6_EAX_HWP_PACKAGE_LEVEL_REQUEST (_AC(1, U) << 11) +#define CPUID6_EAX_HDC (_AC(1, U) << 13) +#define CPUID6_EAX_HWP_PECI (_AC(1, U) << 16) +#define CPUID6_EAX_HW_FEEDBACK (_AC(1, U) << 19)
Perhaps better without open-coding BIT()?
I also find it a little odd that e.g. bit 17 is left out here despite you declaring the 5 "valid" bits in union hwp_request (which are qualified by this CPUID bit afaict).
xen/arch/x86/include/asm/cpufeature.h extern struct cpuinfo_x86 boot_cpu_data; · line 59
Quoted 2 lines
xen/arch/x86/include/asm/cpufeature.h +2
-0+#define CPUID6_ECX_APERFMPERF_CAPABILITY 0x1 +#define CPUID6_ECX_IA32_ENERGY_PERF_BIAS 0x8
Why not the same form here?
xen/arch/x86/include/asm/msr-index.h line 159
Quoted 12 lines
xen/arch/x86/include/asm/msr-index.h +6
-0@@ -151,6 +151,13 @@#define MSR_PKRS 0x000006e1 +#define MSR_IA32_PM_ENABLE 0x00000770 +#define IA32_PM_ENABLE_HWP_ENABLE (_AC(1, ULL) << 0) + +#define MSR_IA32_HWP_CAPABILITIES 0x00000771 +#define MSR_IA32_HWP_INTERRUPT 0x00000773 +#define MSR_IA32_HWP_REQUEST 0x00000774
I think for new MSRs being added here in particular Andrew would like to see the IA32 infixes omitted. (I'd extend this then to CPUID6_ECX_IA32_ENERGY_PERF_BIAS as well.)
xen/arch/x86/include/asm/msr-index.h line 176
Quoted 6 lines
xen/arch/x86/include/asm/msr-index.h +2
-0@@ -165,6 +172,11 @@#define PASID_PASID_MASK 0x000fffff#define PASID_VALID (_AC(1, ULL) << 31) +#define MSR_IA32_PKG_HDC_CTL 0x00000db0 +#define IA32_PKG_HDC_CTL_HDC_PKG_ENABLE (_AC(1, ULL) << 0)
The name has two redundant infixes, which looks odd, but then I can't suggest any better without going too much out of sync with the SDM.
Quoted 11 lines
xen/drivers/cpufreq/cpufreq.c +5
-0@@ -565,6 +565,38 @@ static void cpufreq_cmdline_common_para(struct cpufreq_policy *new_policy)static int __init cpufreq_handle_common_option (const char *name,const char *val) { +if (!strcmp (name,"hdc" )) { +if (val) { +int ret =parse_bool (val,NULL ); +if (ret !=-1 ) { + opt_cpufreq_hdc = ret;
xen/drivers/cpufreq/cpufreq.c static void cpufreq_cmdline_common_para(struct cpufreq_policy *new_policy) · line 582
Quoted 10 lines
xen/drivers/cpufreq/cpufreq.c +10
-0+return 1 ; + } + }else { + opt_cpufreq_hdc = true; +return 1 ; + } + }else if (!strcmp (name,"no-hdc" )) { + opt_cpufreq_hdc = false; +return 1 ; + }
I think recognizing a "no-" prefix would want to be separated out, and be restricted to val being NULL. It would result in val being pointed at the string "no" (or "off" or anything else parse_bool() recognizes as negative indicator).
Yet if, as suggested above, "hwp" became a "fake" governor also when parsing the command line, "hdc" could actually be handled in its handle_option() hook.
Jan
Re: [PATCH v3 04/14 RESEND] cpufreq: Add Hardware P-State (HWP) driver
Quoted 9 lines · Jan Beulich
Quoted 3 lines · Jason Andryuk
For cpufreq=xen:hwp, placing the option inside the governor wouldn't work. Users would have to select the hwp-internal governor to turn off hwp support.
I'm afraid I don't understand this, and you'll find a comment towards this further down. Even when ...
Quoted 6 lines
Quoted 3 lines
hwp-internal isn't usable without hwp, and users wouldn't
be able to select a different governor. That doesn't matter while hwp defaults off, but it would if or when hwp defaults to enabled.... it starts defaulting to enabled, selecting another governor can simply have the side effect of turning off hwp.
I didn't think of that - makes sense.
Quoted 22 lines
Quoted 4 lines
Write to disable the interrupt - the linux pstate driver does this. We don't use the interrupts, so we can just turn them off. We aren't ready to handle them, so we don't want any. Unclear if this is necessary. SDM says it's default disabled.
Definitely better to be on the safe side.
docs/misc/xen-command-line.pandoc If set, force use of the performance counters for oprofile, rather than detectin · line 502
Quoted 8 lines
docs/misc/xen-command-line.pandoc +1
-1@@ -499,7 +499,7 @@ If set, force use of the performance counters for oprofile, rather than detectin available support. ### cpufreq -> `= none | {{ <boolean> | xen } [:[powersave|performance|ondemand|userspace][,<maxfreq>][,[<minfreq>][,[verbose]]]]} | dom0-kernel` +> `= none | {{ <boolean> | xen } [:[powersave|performance|ondemand|userspace][,<hdc>][,[<hwp>]][,[<maxfreq>]][,[<minfreq>]][,[verbose]]]} | dom0-kernel`Considering you use a special internal governor, the 4 governor alternatives are meaningless for hwp. Hence at the command line level recognizing "hwp" as if it was another governor name would seem better to me. This would then also get rid of one of the two special "no-" prefix parsing cases (which I'm not overly happy about).
Quoted 5 lines
Even if not done that way I'm puzzled by the way you spell out the interaction of "hwp" and "hdc": As you say in the description, "hdc" is meaningful only when "hwp" was specified, so even if not merged with the governors group "hwp" should come first, and "hdc" ought to be rejected if "hwp" wasn't first specified. (The way you've spelled it out it actually looks to be kind of the other way around.)
I placed them in alphabetical order, but, yes, it doesn't make sense.
Quoted 11 lines
Strictly speaking "maxfreq" and "minfreq" also should be objected to when "hwp" was specified.
Overall I'm getting the impression that beyond your "verbose" related adjustment more is needed, if you're meaning to get things closer to how we parse the option (splitting across multiple lines to help see what I mean):
`= none
| {{ <boolean> | xen } [:{powersave|performance|ondemand|userspace} [{,hwp[,hdc]|[,maxfreq=<maxfreq>[,minfreq=<minfreq>]}] [,verbose]]}
Quoted 7 lines
| dom0-kernel`
(We're still parsing in a more relaxed way, e.g. minfreq may come ahead of maxfreq, but better be more tight in the doc than too relaxed.)
Furthermore while max/min freq don't apply directly, there are still two MSRs controlling bounds at the package and logical processor levels.
Well, we only program the logical processor level MSRs because we don't have a good idea of the packages to know when we can skip writing an MSR.
How about this:
`= none
| {{ <boolean> | xen } {
[:{powersave|performance|ondemand|userspace}[,maxfreq=<maxfreq>[,minfreq=<minfreq>]]
| [:hwp[,hdc]] }
[,verbose]]}| dom0-kernel`
i.e:
xen:hwp,hdc
Quoted 20 lines
Quoted 20 lines
xen/arch/x86/acpi/cpufreq/hwp.c new file +17
-0@@ -0,0 +1,506 @@ +/* SPDX-License-Identifier: GPL-2.0 */ +/* +* hwp.c cpufreq driver to run Intel Hardware P-States (HWP) +* +* Copyright (C) 2021 Jason Andryuk <[email protected]> +*/ + +#include <xen/cpumask.h> +#include <xen/init.h> +#include <xen/param.h> +#include <xen/xmalloc.h> +#include <asm/io.h> +#include <asm/msr.h> +#include <acpi/cpufreq/cpufreq.h> + +static bool feature_hwp; +static bool feature_hwp_notification;
Quoted 8 lines
xen/arch/x86/acpi/cpufreq/hwp.c line 23
Quoted 6 lines
xen/arch/x86/acpi/cpufreq/hwp.c new file +6
-0+static bool feature_hwp_activity_window; +static bool feature_hwp_energy_perf; +static bool feature_hwp_pkg_level_ctl; +static bool feature_hwp_peci; + +static bool feature_hdc;Most (all?) of these want to be
__ro_after_init, I expect.
I think you are correct. (This pre-dates __ro_after_init and I didn't update it.)
Quoted 22 lines
xen/arch/x86/acpi/cpufreq/hwp.c line 26
Quoted 2 lines
xen/arch/x86/acpi/cpufreq/hwp.c new file +2
-0+__initdata bool opt_cpufreq_hwp = false; +__initdata bool opt_cpufreq_hdc = true;Nit (style): Please put annotations after the type.
Quoted 17 lines
xen/arch/x86/acpi/cpufreq/hwp.c new file +17
-0+#define HWP_ENERGY_PERF_BALANCE 0x80 +#define IA32_ENERGY_BIAS_BALANCE 0x7 +#define IA32_ENERGY_BIAS_MAX_POWERSAVE 0xf +#define IA32_ENERGY_BIAS_MASK 0xf + +union hwp_request +{ +struct + { +uint64_t min_perf:8 ; +uint64_t max_perf:8 ; +uint64_t desired:8 ; +uint64_t energy_perf:8 ; +uint64_t activity_window:10 ; +uint64_t package_control:1 ; +uint64_t reserved:16 ; +uint64_t activity_window_valid:1 ;
Quoted 8 lines
xen/arch/x86/acpi/cpufreq/hwp.c line 48
Quoted 4 lines
xen/arch/x86/acpi/cpufreq/hwp.c new file +4
-0+ uint64_t energy_perf_valid:1; + uint64_t desired_valid:1; + uint64_t max_perf_valid:1; + uint64_t min_perf_valid:1;The boolean fields here would probably better be of type "bool". I also don't see the need for using
uint64_tfor any of the other fields - unsigned int will be quite fine, I think. Only ...
This is the hardware MSR format, so it seemed natural to use uint64_t and the bit fields. To me, uint64_t foo:$bits; better shows that we are dividing up a single hardware register using bit fields. Honestly, I'm unfamiliar with the finer points of laying out bitfields with bool. And the 10 bits of activity window throws off aligning to standard types.
This seems to have the correct layout:
struct
{
unsigned char min_perf;
unsigned char max_perf;
unsigned char desired;
unsigned char energy_perf;
unsigned int activity_window:10;
bool package_control:1;
unsigned int reserved:16;
bool activity_window_valid:1;
bool energy_perf_valid:1;
bool desired_valid:1;
bool max_perf_valid:1;
bool min_perf_valid:1;
} ;Or would you prefer the first 8 bit ones to be unsigned int min_perf:8? The bools seem to need :1, which doesn't seem to be gaining us much, IMO. I'd strongly prefer just keeping it as I have it, but I will change it however you like.
Quoted 4 lines
xen/arch/x86/acpi/cpufreq/hwp.c line 50
Quoted 2 lines
xen/arch/x86/acpi/cpufreq/hwp.c new file +2
-0+ }; +uint64_t raw;... this wants to keep this type. (Same again below then.)
For "below", do you want:
struct
{
unsigned char highest;
unsigned char guaranteed;
unsigned char most_efficient;
unsigned char lowest;
unsigned int reserved;
} hw;?
Quoted 49 lines
Quoted 49 lines
xen/arch/x86/acpi/cpufreq/hwp.c new file +49
-0+bool __init hwp_available (void ) +{ +unsigned int eax, ecx, unused; +bool use_hwp; + +if ( boot_cpu_data.cpuid_level <CPUID_PM_LEAF ) + { +hwp_verbose ("cpuid_level (%#x) lacks HWP support\n" , + boot_cpu_data.cpuid_level); +return false; + } + +if ( boot_cpu_data.cpuid_level <0x16 ) + { +hwp_info ("HWP disabled: cpuid_level %#x < 0x16 lacks CPU freq info\n" , + boot_cpu_data.cpuid_level); +return false; + } + +cpuid (CPUID_PM_LEAF , &eax, &unused, &ecx, &unused); + +if ( !(eax &CPUID6_EAX_HWP_ENERGY_PERFORMANCE_PREFERENCE ) && + !(ecx &CPUID6_ECX_IA32_ENERGY_PERF_BIAS ) ) + { +hwp_verbose ("HWP disabled: No energy/performance preference available" ); +return false; + } + + feature_hwp = eax &CPUID6_EAX_HWP ; + feature_hwp_notification = eax &CPUID6_EAX_HWP_NOTIFICATION ; + feature_hwp_activity_window = eax &CPUID6_EAX_HWP_ACTIVITY_WINDOW ; + feature_hwp_energy_perf = + eax &CPUID6_EAX_HWP_ENERGY_PERFORMANCE_PREFERENCE ; + feature_hwp_pkg_level_ctl = eax &CPUID6_EAX_HWP_PACKAGE_LEVEL_REQUEST ; + feature_hwp_peci = eax &CPUID6_EAX_HWP_PECI ; + +hwp_verbose ("HWP: %d notify: %d act-window: %d energy-perf: %d pkg-level: %d peci: %d\n" , + feature_hwp, feature_hwp_notification, + feature_hwp_activity_window, feature_hwp_energy_perf, + feature_hwp_pkg_level_ctl, feature_hwp_peci); + +if ( !feature_hwp ) +return false; + + feature_hdc = eax &CPUID6_EAX_HDC ; + + hwp_verbose("HWP: Hardware Duty Cycling (HDC) %ssupported%s\n", + feature_hdc ? "" : "not ", + feature_hdc ? opt_cpufreq_hdc ? ", enabled" : ", disabled"
Quoted 8 lines
xen/arch/x86/acpi/cpufreq/hwp.c line 174
Quoted 6 lines
xen/arch/x86/acpi/cpufreq/hwp.c new file +6
-0+ : ""); + + feature_hdc = feature_hdc && opt_cpufreq_hdc; + +hwp_verbose ("HWP: HW_FEEDBACK %ssupported\n" , + (eax &CPUID6_EAX_HW_FEEDBACK ) ?"" :"not " );You report this, but you don't really use it?
Correct. I needed to know what capabilities my processors have.
feature_hwp_pkg_level_ctl and feature_hwp_peci can also be dropped since they aren't used beyond printing their values. I'd still lean toward keeping their printing under verbose since otherwise there isn't a convenient way to know if they are available without recompiling.
Quoted 5 lines
xen/arch/x86/acpi/cpufreq/hwp.c line 176
Quoted 1 line
xen/arch/x86/acpi/cpufreq/hwp.c new file +1
-0+ use_hwp = feature_hwp && opt_cpufreq_hwp;There's a lot of output you may produce until you make it here, which is largely meaningless when
opt_cpufreq_hwp== false. Is there a reason you don't check that flag first thing in the function?
opt_cpufreq_hwp can be checked earlier for an early exit, yes. The code came about during development to print all the HWP capabilities even if it wasn't enabled. But eliminating it now makes sense.
Quoted 36 lines
Quoted 36 lines
xen/arch/x86/acpi/cpufreq/hwp.c new file +36
-0+static void hdc_set_pkg_hdc_ctl (bool val) +{ +uint64_t msr; + +if (rdmsr_safe (MSR_IA32_PKG_HDC_CTL , msr) ) + { +hwp_err ("error rdmsr_safe(MSR_IA32_PKG_HDC_CTL)\n" ); + +return ; + } + +if ( val ) + msr |=IA32_PKG_HDC_CTL_HDC_PKG_ENABLE ; +else + msr &= ~IA32_PKG_HDC_CTL_HDC_PKG_ENABLE ; + +if (wrmsr_safe (MSR_IA32_PKG_HDC_CTL , msr) ) +hwp_err ("error wrmsr_safe(MSR_IA32_PKG_HDC_CTL): %016lx\n" , msr); +} + +static void hdc_set_pm_ctl1 (bool val) +{ +uint64_t msr; + +if (rdmsr_safe (MSR_IA32_PM_CTL1 , msr) ) + { +hwp_err ("error rdmsr_safe(MSR_IA32_PM_CTL1)\n" ); + +return ; + } + +if ( val ) + msr |=IA32_PM_CTL1_HDC_ALLOW_BLOCK ; +else + msr &= ~IA32_PM_CTL1_HDC_ALLOW_BLOCK ; +
Quoted 8 lines
xen/arch/x86/acpi/cpufreq/hwp.c line 223
Quoted 3 lines
xen/arch/x86/acpi/cpufreq/hwp.c new file +3
-0+if (wrmsr_safe (MSR_IA32_PM_CTL1 , msr) ) +hwp_err ("error wrmsr_safe(MSR_IA32_PM_CTL1): %016lx\n" , msr); +}For both functions: Elsewhere you also log the affected CPU in
hwp_err(). Without this I'm not convinced the logging here is very useful. In fact I wonder whetherhwp_err()shouldn't take care of this and/or the "error" part of the string literal. A HWP: prefix might also not be bad ...
Sounds good. I'll investigate.
Quoted 7 lines
Quoted 7 lines
xen/arch/x86/acpi/cpufreq/hwp.c new file +7
-0+static void hwp_get_cpu_speeds (struct cpufreq_policy *policy) +{ +uint32_t base_khz, max_khz, bus_khz, edx; + +cpuid (0x16 , &base_khz, &max_khz, &bus_khz, &edx); + +/* aperf/mperf scales base. */
Quoted 8 lines
xen/arch/x86/acpi/cpufreq/hwp.c line 237
Quoted 6 lines
xen/arch/x86/acpi/cpufreq/hwp.c new file +6
-0+ policy->cpuinfo.perf_freq = base_khz *1000 ; + policy->cpuinfo.min_freq = base_khz *1000 ; + policy->cpuinfo.max_freq = max_khz *1000 ; + policy->min = base_khz *1000 ; + policy->max = max_khz *1000 ; + policy->cur =0 ;What is the comment intended to be telling me here?
When I was surprised to discover that I needed to pass in the base frequency for proper aperf/mperf scaling, it seemed relevant at the time as it's the opposite of ACPI cpufreq. It can be dropped now.
Quoted 53 lines
Quoted 40 lines
xen/arch/x86/acpi/cpufreq/hwp.c new file +40
-0+static void cf_check hwp_init_msrs(void *info) +{ +struct cpufreq_policy *policy = info; +struct hwp_drv_data *data =this_cpu (hwp_drv_data); +uint64_t val; + +/* +* Package level MSR, but we don't have a good idea of packages here, so +* just do it everytime. +*/ +if (rdmsr_safe (MSR_IA32_PM_ENABLE , val) ) + { +hwp_err ("CPU%u: error rdmsr_safe(MSR_IA32_PM_ENABLE)\n" , policy->cpu); + data->curr_req.raw =-1 ; +return ; + } + +/* Ensure we don't generate interrupts */ +if ( feature_hwp_notification ) +wrmsr_safe (MSR_IA32_HWP_INTERRUPT ,0 ); + +hwp_verbose ("CPU%u: MSR_IA32_PM_ENABLE: %016lx\n" , policy->cpu, val); +if ( !(val &IA32_PM_ENABLE_HWP_ENABLE ) ) + { + val |=IA32_PM_ENABLE_HWP_ENABLE ; +if (wrmsr_safe (MSR_IA32_PM_ENABLE , val) ) + { +hwp_err ("CPU%u: error wrmsr_safe(MSR_IA32_PM_ENABLE, %lx)\n" , + policy->cpu, val); + data->curr_req.raw =-1 ; +return ; + } + } + +if (rdmsr_safe (MSR_IA32_HWP_CAPABILITIES , data->hwp_caps) ) + { +hwp_err ("CPU%u: error rdmsr_safe(MSR_IA32_HWP_CAPABILITIES)\n" , + policy->cpu); + data->curr_req.raw =-1 ; +return ;xen/arch/x86/acpi/cpufreq/hwp.c line 289
Quoted 10 lines
xen/arch/x86/acpi/cpufreq/hwp.c new file +10
-0+ } + +if (rdmsr_safe (MSR_IA32_HWP_REQUEST , data->curr_req.raw) ) + { +hwp_err ("CPU%u: error rdmsr_safe(MSR_IA32_HWP_REQUEST)\n" , policy->cpu); + data->curr_req.raw =-1 ; +return ; + } + +if ( !feature_hwp_energy_perf ) {Nit: Brace placement.
Quoted 13 lines
xen/arch/x86/acpi/cpufreq/hwp.c line 299
Quoted 10 lines
xen/arch/x86/acpi/cpufreq/hwp.c new file +10
-0+if (rdmsr_safe (MSR_IA32_ENERGY_PERF_BIAS , val) ) + { +hwp_err ("error rdmsr_safe(MSR_IA32_ENERGY_PERF_BIAS)\n" ); + data->curr_req.raw =-1 ; + +return ; + } + + data->energy_perf = val &IA32_ENERGY_BIAS_MASK ; + }In order to not need to undo the "enable" you've already done, maybe that should move down here?
HWP needs to be enabled before the Capabilities and Request MSRs can be read. Reading them shouldn't fail, but it seems safer to use rdmsr_safe in case something goes wrong.
I think I will rip out ENERGY_PERF_BIAS. The Linux driver doesn't support it. I thought it might be necessary, but my test machines don't need it. The Qubes report with SkyLake wasn't using ENERGY_PERF_BIAS, and SkyLake introduced HWP. So the set of machines needing it is probably small and older, so it probably isn't worth supporting.
Quoted 3 lines
With all the sanity checking you do here, maybe
you should also check that the write of the enable bit actually took effect?
I can add that.
Quoted 67 lines
Quoted 67 lines
xen/arch/x86/acpi/cpufreq/hwp.c new file +67
-0+/* val 0 - highest performance, 15 - maximum energy savings */ +static void hwp_energy_perf_bias (const struct hwp_drv_data *data) +{ +uint64_t msr; +uint8_t val = data->energy_perf; + +ASSERT (val <=IA32_ENERGY_BIAS_MAX_POWERSAVE ); + +if (rdmsr_safe (MSR_IA32_ENERGY_PERF_BIAS , msr) ) + { +hwp_err ("error rdmsr_safe(MSR_IA32_ENERGY_PERF_BIAS)\n" ); + +return ; + } + + msr &= ~IA32_ENERGY_BIAS_MASK ; + msr |= val; + +if (wrmsr_safe (MSR_IA32_ENERGY_PERF_BIAS , msr) ) +hwp_err ("error wrmsr_safe(MSR_IA32_ENERGY_PERF_BIAS): %016lx\n" , msr); +} + +static void cf_check hwp_write_request(void *info) +{ +struct cpufreq_policy *policy = info; +struct hwp_drv_data *data =this_cpu (hwp_drv_data); +union hwp_request hwp_req = data->curr_req; + +BUILD_BUG_ON (sizeof (union hwp_request ) !=sizeof (uint64_t )); +if (wrmsr_safe (MSR_IA32_HWP_REQUEST , hwp_req.raw) ) + { +hwp_err ("CPU%u: error wrmsr_safe(MSR_IA32_HWP_REQUEST, %lx)\n" , + policy->cpu, hwp_req.raw); +rdmsr_safe (MSR_IA32_HWP_REQUEST , data->curr_req.raw); + } + +if ( !feature_hwp_energy_perf ) +hwp_energy_perf_bias (data); + +} + +static int cf_check hwp_cpufreq_target(struct cpufreq_policy *policy, +unsigned int target_freq, +unsigned int relation) +{ +unsigned int cpu = policy->cpu; +struct hwp_drv_data *data =per_cpu (hwp_drv_data, cpu); +/* Zero everything to ensure reserved bits are zero... */ +union hwp_request hwp_req = { .raw =0 }; + +/* .. and update from there */ + hwp_req.min_perf = data->minimum; + hwp_req.max_perf = data->maximum; + hwp_req.desired = data->desired; +if ( feature_hwp_energy_perf ) + hwp_req.energy_perf = data->energy_perf; +if ( feature_hwp_activity_window ) + hwp_req.activity_window = data->activity_window; + +if ( hwp_req.raw == data->curr_req.raw ) +return 0 ; + + data->curr_req = hwp_req; + +hwp_verbose ("CPU%u: wrmsr HWP_REQUEST %016lx\n" , cpu, hwp_req.raw); +on_selected_cpus (cpumask_of (cpu), hwp_write_request, policy,1 ); +
Quoted 8 lines
xen/arch/x86/acpi/cpufreq/hwp.c line 285
Quoted 2 lines
xen/arch/x86/acpi/cpufreq/hwp.c new file +2
-0+return 0 ; +}If I'm not mistaken these 3 functions can only be reached from the user space tool (via
set_cpufreq_para()). On that path I don't think there should be anyhwp_err(); definitely not in non-verbose mode. Instead it would be good if a sensible error code could be reported back. (Same then forhwp_cpufreq_update()and its helper.)
I'll investigate this. I guess I'll have to stash a result in struct hwp_drv_data.
Quoted 6 lines
Quoted 6 lines
xen/arch/x86/include/asm/cpufeature.h +0
-0@@ -46,8 +46,17 @@ extern struct cpuinfo_x86 boot_cpu_data;#define cpu_has (c, bit) test_bit(bit, (c)->x86_capability)#define boot_cpu_has (bit) test_bit(bit, boot_cpu_data.x86_capability)
Quoted 13 lines
xen/arch/x86/include/asm/cpufeature.h extern struct cpuinfo_x86 boot_cpu_data; · line 57
Quoted 11 lines
xen/arch/x86/include/asm/cpufeature.h +9
-2-#define CPUID_PM_LEAF 6 -#define CPUID6_ECX_APERFMPERF_CAPABILITY 0x1 +#define CPUID_PM_LEAF 6 +#define CPUID6_EAX_HWP (_AC(1, U) << 7) +#define CPUID6_EAX_HWP_NOTIFICATION (_AC(1, U) << 8) +#define CPUID6_EAX_HWP_ACTIVITY_WINDOW (_AC(1, U) << 9) +#define CPUID6_EAX_HWP_ENERGY_PERFORMANCE_PREFERENCE (_AC(1, U) << 10) +#define CPUID6_EAX_HWP_PACKAGE_LEVEL_REQUEST (_AC(1, U) << 11) +#define CPUID6_EAX_HDC (_AC(1, U) << 13) +#define CPUID6_EAX_HWP_PECI (_AC(1, U) << 16) +#define CPUID6_EAX_HW_FEEDBACK (_AC(1, U) << 19)Perhaps better without open-coding
BIT()?
Ok.
Quoted 3 lines
I also find it a little odd that e.g. bit 17 is left out here despite you declaring the 5 "valid" bits in union
hwp_request(which are qualified by this CPUID bit afaict).
Well, I thought I wasn't supposed to introduce unused defines, so I didn't add one for 17. For union hwp_request, the "valid" bits are part of the register structure, so it makes sense to include them instead of an incomplete definition. IIRC, at some point I set the "valid" bits when I wasn't supposed to, and they caused the wrmsr calls to fail. That might have been because my test machines don't have package-level HWP.
(I was confused when the CPUID section stated "Bit 17: Flexible HWP is supported if set.", but there are no further references to "Flexible HWP" in the SDM.)
Quoted 4 lines
xen/arch/x86/include/asm/cpufeature.h extern struct cpuinfo_x86 boot_cpu_data; · line 59
Quoted 2 lines
xen/arch/x86/include/asm/cpufeature.h +2
-0+#define CPUID6_ECX_APERFMPERF_CAPABILITY 0x1 +#define CPUID6_ECX_IA32_ENERGY_PERF_BIAS 0x8Why not the same form here?
I was re-indenting APERFMPERF, and added ENERGY_PERF_BIAS in a consistent style. I will update with BIT().
Quoted 6 lines
Quoted 6 lines
xen/arch/x86/include/asm/msr-index.h +0
-0@@ -151,6 +151,13 @@#define MSR_PKRS 0x000006e1
Quoted 10 lines
xen/arch/x86/include/asm/msr-index.h line 159
Quoted 6 lines
xen/arch/x86/include/asm/msr-index.h +6
-0+#define MSR_IA32_PM_ENABLE 0x00000770 +#define IA32_PM_ENABLE_HWP_ENABLE (_AC(1, ULL) << 0) + +#define MSR_IA32_HWP_CAPABILITIES 0x00000771 +#define MSR_IA32_HWP_INTERRUPT 0x00000773 +#define MSR_IA32_HWP_REQUEST 0x00000774I think for new MSRs being added here in particular Andrew would like to see the IA32 infixes omitted. (I'd extend this then to
CPUID6_ECX_IA32_ENERGY_PERF_BIASas well.)
Ok.
Quoted 9 lines
xen/arch/x86/include/asm/msr-index.h line 176
Quoted 6 lines
xen/arch/x86/include/asm/msr-index.h +2
-0@@ -165,6 +172,11 @@#define PASID_PASID_MASK 0x000fffff#define PASID_VALID (_AC(1, ULL) << 31) +#define MSR_IA32_PKG_HDC_CTL 0x00000db0 +#define IA32_PKG_HDC_CTL_HDC_PKG_ENABLE (_AC(1, ULL) << 0)The name has two redundant infixes, which looks odd, but then I can't suggest any better without going too much out of sync with the SDM.
Yes, it's not a good name, but I was trying to keep close to the SDM. FAOD, these should drop IA32_ to become:MSR_PKG_HDC_CTLPKG_HDC_CTL_HDC_PKG_ENABLE
?
Quoted 27 lines
Quoted 11 lines
xen/drivers/cpufreq/cpufreq.c +5
-0@@ -565,6 +565,38 @@ static void cpufreq_cmdline_common_para(struct cpufreq_policy *new_policy)static int __init cpufreq_handle_common_option (const char *name,const char *val) { +if (!strcmp (name,"hdc" )) { +if (val) { +int ret =parse_bool (val,NULL ); +if (ret !=-1 ) { + opt_cpufreq_hdc = ret;xen/drivers/cpufreq/cpufreq.c static void cpufreq_cmdline_common_para(struct cpufreq_policy *new_policy) · line 582
Quoted 10 lines
xen/drivers/cpufreq/cpufreq.c +10
-0+return 1 ; + } + }else { + opt_cpufreq_hdc = true; +return 1 ; + } + }else if (!strcmp (name,"no-hdc" )) { + opt_cpufreq_hdc = false; +return 1 ; + }I think recognizing a "no-" prefix would want to be separated out, and be restricted to val being NULL. It would result in val being pointed at the string "no" (or "off" or anything else
parse_bool()recognizes as negative indicator).
Quoted 3 lines
Yet if, as suggested above, "hwp" became a "fake" governor also when parsing the command line, "hdc" could actually be handled in its
handle_option()hook.
Makes sense.
Thank you for taking the time to review this.
Regards,
Jason
Re: [PATCH v3 04/14 RESEND] cpufreq: Add Hardware P-State (HWP) driver
Quoted 48 lines · Jason Andryuk
Quoted 16 lines · Jan Beulich
docs/misc/xen-command-line.pandoc If set, force use of the performance counters for oprofile, rather than detectin · line 502
Quoted 8 lines · Jason Andryuk
docs/misc/xen-command-line.pandoc +1
-1@@ -499,7 +499,7 @@ If set, force use of the performance counters for oprofile, rather than detectin available support. ### cpufreq -> `= none | {{ <boolean> | xen } [:[powersave|performance|ondemand|userspace][,<maxfreq>][,[<minfreq>][,[verbose]]]]} | dom0-kernel` +> `= none | {{ <boolean> | xen } [:[powersave|performance|ondemand|userspace][,<hdc>][,[<hwp>]][,[<maxfreq>]][,[<minfreq>]][,[verbose]]]} | dom0-kernel`Considering you use a special internal governor, the 4 governor alternatives are meaningless for hwp. Hence at the command line level recognizing "hwp" as if it was another governor name would seem better to me. This would then also get rid of one of the two special "no-" prefix parsing cases (which I'm not overly happy about).
Quoted 5 lines
Even if not done that way I'm puzzled by the way you spell out the interaction of "hwp" and "hdc": As you say in the description, "hdc" is meaningful only when "hwp" was specified, so even if not merged with the governors group "hwp" should come first, and "hdc" ought to be rejected if "hwp" wasn't first specified. (The way you've spelled it out it actually looks to be kind of the other way around.)
I placed them in alphabetical order, but, yes, it doesn't make sense.
Quoted 11 lines
Strictly speaking "maxfreq" and "minfreq" also should be objected to when "hwp" was specified.
Overall I'm getting the impression that beyond your "verbose" related adjustment more is needed, if you're meaning to get things closer to how we parse the option (splitting across multiple lines to help see what I mean):
`= none
| {{ <boolean> | xen } [:{powersave|performance|ondemand|userspace} [{,hwp[,hdc]|[,maxfreq=<maxfreq>[,minfreq=<minfreq>]}] [,verbose]]}Quoted 7 lines
| dom0-kernel`
(We're still parsing in a more relaxed way, e.g. minfreq may come ahead of maxfreq, but better be more tight in the doc than too relaxed.)
Furthermore while max/min freq don't apply directly, there are still two MSRs controlling bounds at the package and logical processor levels.
Well, we only program the logical processor level MSRs because we don't have a good idea of the packages to know when we can skip writing an MSR.
Quoted 7 lines
How about this:
`= none| {{ <boolean> | xen } { [:{powersave|performance|ondemand|userspace}[,maxfreq=<maxfreq>[,minfreq=<minfreq>]] | [:hwp[,hdc]] } [,verbose]]}| dom0-kernel`
Looks right, yes.
Quoted 29 lines
Quoted 20 lines
Quoted 20 lines
xen/arch/x86/acpi/cpufreq/hwp.c new file +17
-0@@ -0,0 +1,506 @@ +/* SPDX-License-Identifier: GPL-2.0 */ +/* +* hwp.c cpufreq driver to run Intel Hardware P-States (HWP) +* +* Copyright (C) 2021 Jason Andryuk <[email protected]> +*/ + +#include <xen/cpumask.h> +#include <xen/init.h> +#include <xen/param.h> +#include <xen/xmalloc.h> +#include <asm/io.h> +#include <asm/msr.h> +#include <acpi/cpufreq/cpufreq.h> + +static bool feature_hwp; +static bool feature_hwp_notification;Quoted 8 lines
xen/arch/x86/acpi/cpufreq/hwp.c line 23
Quoted 6 lines
xen/arch/x86/acpi/cpufreq/hwp.c new file +6
-0+static bool feature_hwp_activity_window; +static bool feature_hwp_energy_perf; +static bool feature_hwp_pkg_level_ctl; +static bool feature_hwp_peci; + +static bool feature_hdc;Most (all?) of these want to be
__ro_after_init, I expect.
Quoted 2 lines
I think you are correct. (This pre-dates
__ro_after_initand I didn't update it.)
Yet even then they should have used __read_mostly.
Quoted 45 lines
Quoted 12 lines
Quoted 12 lines
xen/arch/x86/acpi/cpufreq/hwp.c new file +12
-0+union hwp_request +{ +struct + { +uint64_t min_perf:8 ; +uint64_t max_perf:8 ; +uint64_t desired:8 ; +uint64_t energy_perf:8 ; +uint64_t activity_window:10 ; +uint64_t package_control:1 ; +uint64_t reserved:16 ; +uint64_t activity_window_valid:1 ;Quoted 8 lines
xen/arch/x86/acpi/cpufreq/hwp.c line 48
Quoted 4 lines
xen/arch/x86/acpi/cpufreq/hwp.c new file +4
-0+ uint64_t energy_perf_valid:1; + uint64_t desired_valid:1; + uint64_t max_perf_valid:1; + uint64_t min_perf_valid:1;The boolean fields here would probably better be of type "bool". I also don't see the need for using
uint64_tfor any of the other fields - unsigned int will be quite fine, I think. Only ...This is the hardware MSR format, so it seemed natural to use
uint64_tand the bit fields. To me,uint64_tfoo:$bits; better shows that we are dividing up a single hardware register using bit fields. Honestly, I'm unfamiliar with the finer points of laying out bitfields with bool. And the 10 bits of activity window throws off aligning to standard types.This seems to have the correct layout:
struct{ unsigned char min_perf; unsigned char max_perf; unsigned char desired; unsigned char energy_perf; unsigned int activity_window:10; bool package_control:1; unsigned int reserved:16; bool activity_window_valid:1; bool energy_perf_valid:1; bool desired_valid:1; bool max_perf_valid:1; bool min_perf_valid:1; } ;
Quoted 2 lines
Or would you prefer the first 8 bit ones to be unsigned int min_perf:8?
Personally I think using bitfields uniformly would be better. What you definitely cannot use if not using a bitfield is "unsigned char", it ought to by uint8_t then. If using a bitfield, as said, I think it's best to stick to unsigned int and bool, unless field width goes beyond 32 bits or fields cross a 32-bit boundary.
Quoted 3 lines
The bools seem to need :1, which doesn't seem to be
gaining us much, IMO. I'd strongly prefer just keeping it as I have it, but I will change it however you like.
It's not so much how I like it, but to follow (a) existing practice (for the boolean fields) and (b) ./CODING_STYLE (for the selection of types).
Quoted 15 lines
Quoted 4 lines
xen/arch/x86/acpi/cpufreq/hwp.c line 50
Quoted 2 lines
xen/arch/x86/acpi/cpufreq/hwp.c new file +2
-0+ }; +uint64_t raw;... this wants to keep this type. (Same again below then.)
For "below", do you want:
struct { unsigned char highest; unsigned char guaranteed; unsigned char most_efficient; unsigned char lowest; unsigned int reserved; } hw;
Quoted 1 line
?
No - it can only be bitfields or fixed-width types here.
Quoted 58 lines
Quoted 49 lines
Quoted 49 lines
xen/arch/x86/acpi/cpufreq/hwp.c new file +49
-0+bool __init hwp_available (void ) +{ +unsigned int eax, ecx, unused; +bool use_hwp; + +if ( boot_cpu_data.cpuid_level <CPUID_PM_LEAF ) + { +hwp_verbose ("cpuid_level (%#x) lacks HWP support\n" , + boot_cpu_data.cpuid_level); +return false; + } + +if ( boot_cpu_data.cpuid_level <0x16 ) + { +hwp_info ("HWP disabled: cpuid_level %#x < 0x16 lacks CPU freq info\n" , + boot_cpu_data.cpuid_level); +return false; + } + +cpuid (CPUID_PM_LEAF , &eax, &unused, &ecx, &unused); + +if ( !(eax &CPUID6_EAX_HWP_ENERGY_PERFORMANCE_PREFERENCE ) && + !(ecx &CPUID6_ECX_IA32_ENERGY_PERF_BIAS ) ) + { +hwp_verbose ("HWP disabled: No energy/performance preference available" ); +return false; + } + + feature_hwp = eax &CPUID6_EAX_HWP ; + feature_hwp_notification = eax &CPUID6_EAX_HWP_NOTIFICATION ; + feature_hwp_activity_window = eax &CPUID6_EAX_HWP_ACTIVITY_WINDOW ; + feature_hwp_energy_perf = + eax &CPUID6_EAX_HWP_ENERGY_PERFORMANCE_PREFERENCE ; + feature_hwp_pkg_level_ctl = eax &CPUID6_EAX_HWP_PACKAGE_LEVEL_REQUEST ; + feature_hwp_peci = eax &CPUID6_EAX_HWP_PECI ; + +hwp_verbose ("HWP: %d notify: %d act-window: %d energy-perf: %d pkg-level: %d peci: %d\n" , + feature_hwp, feature_hwp_notification, + feature_hwp_activity_window, feature_hwp_energy_perf, + feature_hwp_pkg_level_ctl, feature_hwp_peci); + +if ( !feature_hwp ) +return false; + + feature_hdc = eax &CPUID6_EAX_HDC ; + + hwp_verbose("HWP: Hardware Duty Cycling (HDC) %ssupported%s\n", + feature_hdc ? "" : "not ", + feature_hdc ? opt_cpufreq_hdc ? ", enabled" : ", disabled"Quoted 8 lines
xen/arch/x86/acpi/cpufreq/hwp.c line 174
Quoted 6 lines
xen/arch/x86/acpi/cpufreq/hwp.c new file +6
-0+ : ""); + + feature_hdc = feature_hdc && opt_cpufreq_hdc; + +hwp_verbose ("HWP: HW_FEEDBACK %ssupported\n" , + (eax &CPUID6_EAX_HW_FEEDBACK ) ?"" :"not " );You report this, but you don't really use it?
Quoted 7 lines
Correct. I needed to know what capabilities my processors have.
feature_hwp_pkg_level_ctlandfeature_hwp_pecican also be dropped since they aren't used beyond printing their values. I'd still lean toward keeping their printing under verbose since otherwise there isn't a convenient way to know if they are available without recompiling.
That's fine, but wants mentioning in the description. Also respective variables would want to be __initdata then, be local to the function, or be dropped altogether. Plus you'd want to be consistent - either you use a helper variable for all print-only features, or you don't.
Quoted 16 lines
Quoted 7 lines
Quoted 7 lines
xen/arch/x86/acpi/cpufreq/hwp.c new file +7
-0+static void hwp_get_cpu_speeds (struct cpufreq_policy *policy) +{ +uint32_t base_khz, max_khz, bus_khz, edx; + +cpuid (0x16 , &base_khz, &max_khz, &bus_khz, &edx); + +/* aperf/mperf scales base. */ Quoted 8 lines
xen/arch/x86/acpi/cpufreq/hwp.c line 237
Quoted 6 lines
xen/arch/x86/acpi/cpufreq/hwp.c new file +6
-0+ policy->cpuinfo.perf_freq = base_khz *1000 ; + policy->cpuinfo.min_freq = base_khz *1000 ; + policy->cpuinfo.max_freq = max_khz *1000 ; + policy->min = base_khz *1000 ; + policy->max = max_khz *1000 ; + policy->cur =0 ;What is the comment intended to be telling me here?
Quoted 3 lines
When I was surprised to discover that I needed to pass in the base frequency for proper aperf/mperf scaling, it seemed relevant at the time as it's the opposite of ACPI cpufreq. It can be dropped now.
Well, I'm not insisting on dropping the comment. It could also be left, but then extended so it can be understood what is meant.
Quoted 67 lines
Quoted 53 lines
Quoted 40 lines
xen/arch/x86/acpi/cpufreq/hwp.c new file +40
-0+static void cf_check hwp_init_msrs(void *info) +{ +struct cpufreq_policy *policy = info; +struct hwp_drv_data *data =this_cpu (hwp_drv_data); +uint64_t val; + +/* +* Package level MSR, but we don't have a good idea of packages here, so +* just do it everytime. +*/ +if (rdmsr_safe (MSR_IA32_PM_ENABLE , val) ) + { +hwp_err ("CPU%u: error rdmsr_safe(MSR_IA32_PM_ENABLE)\n" , policy->cpu); + data->curr_req.raw =-1 ; +return ; + } + +/* Ensure we don't generate interrupts */ +if ( feature_hwp_notification ) +wrmsr_safe (MSR_IA32_HWP_INTERRUPT ,0 ); + +hwp_verbose ("CPU%u: MSR_IA32_PM_ENABLE: %016lx\n" , policy->cpu, val); +if ( !(val &IA32_PM_ENABLE_HWP_ENABLE ) ) + { + val |=IA32_PM_ENABLE_HWP_ENABLE ; +if (wrmsr_safe (MSR_IA32_PM_ENABLE , val) ) + { +hwp_err ("CPU%u: error wrmsr_safe(MSR_IA32_PM_ENABLE, %lx)\n" , + policy->cpu, val); + data->curr_req.raw =-1 ; +return ; + } + } + +if (rdmsr_safe (MSR_IA32_HWP_CAPABILITIES , data->hwp_caps) ) + { +hwp_err ("CPU%u: error rdmsr_safe(MSR_IA32_HWP_CAPABILITIES)\n" , + policy->cpu); + data->curr_req.raw =-1 ; +return ;xen/arch/x86/acpi/cpufreq/hwp.c line 289
Quoted 10 lines
xen/arch/x86/acpi/cpufreq/hwp.c new file +10
-0+ } + +if (rdmsr_safe (MSR_IA32_HWP_REQUEST , data->curr_req.raw) ) + { +hwp_err ("CPU%u: error rdmsr_safe(MSR_IA32_HWP_REQUEST)\n" , policy->cpu); + data->curr_req.raw =-1 ; +return ; + } + +if ( !feature_hwp_energy_perf ) {Nit: Brace placement.
Quoted 13 lines
xen/arch/x86/acpi/cpufreq/hwp.c line 299
Quoted 10 lines
xen/arch/x86/acpi/cpufreq/hwp.c new file +10
-0+if (rdmsr_safe (MSR_IA32_ENERGY_PERF_BIAS , val) ) + { +hwp_err ("error rdmsr_safe(MSR_IA32_ENERGY_PERF_BIAS)\n" ); + data->curr_req.raw =-1 ; + +return ; + } + + data->energy_perf = val &IA32_ENERGY_BIAS_MASK ; + }In order to not need to undo the "enable" you've already done, maybe that should move down here?
Quoted 2 lines
HWP needs to be enabled before the Capabilities and Request MSRs can be read.
I must have missed this aspect in the SDM. Do you have a pointer?
Quoted 2 lines
Reading them shouldn't fail, but it seems safer to use
rdmsr_safein case something goes wrong.
Sure. But then the "enable" will need undoing in the unlikely event of failure.
Quoted 34 lines
Quoted 6 lines
Quoted 6 lines
xen/arch/x86/include/asm/cpufeature.h +0
-0@@ -46,8 +46,17 @@ extern struct cpuinfo_x86 boot_cpu_data;#define cpu_has (c, bit) test_bit(bit, (c)->x86_capability)#define boot_cpu_has (bit) test_bit(bit, boot_cpu_data.x86_capability)Quoted 13 lines
xen/arch/x86/include/asm/cpufeature.h extern struct cpuinfo_x86 boot_cpu_data; · line 57
Quoted 11 lines
xen/arch/x86/include/asm/cpufeature.h +9
-2-#define CPUID_PM_LEAF 6 -#define CPUID6_ECX_APERFMPERF_CAPABILITY 0x1 +#define CPUID_PM_LEAF 6 +#define CPUID6_EAX_HWP (_AC(1, U) << 7) +#define CPUID6_EAX_HWP_NOTIFICATION (_AC(1, U) << 8) +#define CPUID6_EAX_HWP_ACTIVITY_WINDOW (_AC(1, U) << 9) +#define CPUID6_EAX_HWP_ENERGY_PERFORMANCE_PREFERENCE (_AC(1, U) << 10) +#define CPUID6_EAX_HWP_PACKAGE_LEVEL_REQUEST (_AC(1, U) << 11) +#define CPUID6_EAX_HDC (_AC(1, U) << 13) +#define CPUID6_EAX_HWP_PECI (_AC(1, U) << 16) +#define CPUID6_EAX_HW_FEEDBACK (_AC(1, U) << 19)Perhaps better without open-coding
BIT()?Ok.
Quoted 3 lines
I also find it a little odd that e.g. bit 17 is left out here despite you declaring the 5 "valid" bits in union
hwp_request(which are qualified by this CPUID bit afaict).Well, I thought I wasn't supposed to introduce unused defines, so I didn't add one for 17. For union
hwp_request, the "valid" bits are part of the register structure, so it makes sense to include them instead of an incomplete definition. IIRC, at some point I set the "valid" bits when I wasn't supposed to, and they caused the wrmsr calls to fail. That might have been because my test machines don't have package-level HWP.
Quoted 3 lines
(I was confused when the CPUID section stated "Bit 17: Flexible HWP is supported if set.", but there are no further references to "Flexible HWP" in the SDM.)
A not uncommon issue with the SDM. At least there is a place where bit 17's purpose is described in the HWP section.
Quoted 10 lines
Quoted 9 lines
xen/arch/x86/include/asm/cpufeature.h line 176
Quoted 6 lines
xen/arch/x86/include/asm/cpufeature.h +2
-0@@ -165,6 +172,11 @@#define PASID_PASID_MASK 0x000fffff#define PASID_VALID (_AC(1, ULL) << 31) +#define MSR_IA32_PKG_HDC_CTL 0x00000db0 +#define IA32_PKG_HDC_CTL_HDC_PKG_ENABLE (_AC(1, ULL) << 0)The name has two redundant infixes, which looks odd, but then I can't suggest any better without going too much out of sync with the SDM.
Quoted 5 lines
Yes, it's not a good name, but I was trying to keep close to the SDM. FAOD, these should drop
IA32_to become:MSR_PKG_HDC_CTLPKG_HDC_CTL_HDC_PKG_ENABLE
?
Right.
Quoted 1 line
Thank you for taking the time to review this.
Well, it has taken me awfully long to get back to this.
Jan
Re: [PATCH v3 04/14 RESEND] cpufreq: Add Hardware P-State (HWP) driver
Quoted 58 lines · Jan Beulich
Quoted 48 lines · Jason Andryuk
Quoted 16 lines · Jan Beulich
docs/misc/xen-command-line.pandoc If set, force use of the performance counters for oprofile, rather than detectin · line 502
Quoted 8 lines · Jason Andryuk
docs/misc/xen-command-line.pandoc +1
-1@@ -499,7 +499,7 @@ If set, force use of the performance counters for oprofile, rather than detectin available support. ### cpufreq -> `= none | {{ <boolean> | xen } [:[powersave|performance|ondemand|userspace][,<maxfreq>][,[<minfreq>][,[verbose]]]]} | dom0-kernel` +> `= none | {{ <boolean> | xen } [:[powersave|performance|ondemand|userspace][,<hdc>][,[<hwp>]][,[<maxfreq>]][,[<minfreq>]][,[verbose]]]} | dom0-kernel`Considering you use a special internal governor, the 4 governor alternatives are meaningless for hwp. Hence at the command line level recognizing "hwp" as if it was another governor name would seem better to me. This would then also get rid of one of the two special "no-" prefix parsing cases (which I'm not overly happy about).
Quoted 5 lines
Even if not done that way I'm puzzled by the way you spell out the interaction of "hwp" and "hdc": As you say in the description, "hdc" is meaningful only when "hwp" was specified, so even if not merged with the governors group "hwp" should come first, and "hdc" ought to be rejected if "hwp" wasn't first specified. (The way you've spelled it out it actually looks to be kind of the other way around.)
I placed them in alphabetical order, but, yes, it doesn't make sense.
Quoted 11 lines
Strictly speaking "maxfreq" and "minfreq" also should be objected to when "hwp" was specified.
Overall I'm getting the impression that beyond your "verbose" related adjustment more is needed, if you're meaning to get things closer to how we parse the option (splitting across multiple lines to help see what I mean):
`= none
| {{ <boolean> | xen } [:{powersave|performance|ondemand|userspace} [{,hwp[,hdc]|[,maxfreq=<maxfreq>[,minfreq=<minfreq>]}] [,verbose]]}Quoted 7 lines
| dom0-kernel`
(We're still parsing in a more relaxed way, e.g. minfreq may come ahead of maxfreq, but better be more tight in the doc than too relaxed.)
Furthermore while max/min freq don't apply directly, there are still two MSRs controlling bounds at the package and logical processor levels.
Well, we only program the logical processor level MSRs because we don't have a good idea of the packages to know when we can skip writing an MSR.
Quoted 7 lines
How about this:
`= none| {{ <boolean> | xen } { [:{powersave|performance|ondemand|userspace}[,maxfreq=<maxfreq>[,minfreq=<minfreq>]] | [:hwp[,hdc]] } [,verbose]]}| dom0-kernel`
Quoted 1 line
Looks right, yes.
There is a wrinkle to using the hwp governor. The hwp governor was named "hwp-internal", so it needs to be renamed to "hwp" for use with command line parsing. That means the checking for "-internal" needs to change to just "hwp" which removes the generality of the original implementation.
The other issue is that if you select "hwp" as the governor, but HWP hardware support is not available, then hwp_available() needs to reset the governor back to the default. This feels like a layering violation.
I'm still investigating, but promoting hwp to a top level option - cpufreq=hwp - might be a better arrangement.
Quoted 45 lines
Quoted 45 lines
Quoted 12 lines
Quoted 12 lines
docs/misc/xen-command-line.pandoc +12
-0+union hwp_request +{ + struct + { + uint64_t min_perf:8; + uint64_t max_perf:8; + uint64_t desired:8; + uint64_t energy_perf:8; + uint64_t activity_window:10; + uint64_t package_control:1; + uint64_t reserved:16; + uint64_t activity_window_valid:1;Quoted 8 lines
docs/misc/xen-command-line.pandoc
Quoted 4 lines
docs/misc/xen-command-line.pandoc +4
-0+ uint64_t energy_perf_valid:1; + uint64_t desired_valid:1; + uint64_t max_perf_valid:1; + uint64_t min_perf_valid:1;The boolean fields here would probably better be of type "bool". I also don't see the need for using
uint64_tfor any of the other fields - unsigned int will be quite fine, I think. Only ...This is the hardware MSR format, so it seemed natural to use
uint64_tand the bit fields. To me,uint64_tfoo:$bits; better shows that we are dividing up a single hardware register using bit fields. Honestly, I'm unfamiliar with the finer points of laying out bitfields with bool. And the 10 bits of activity window throws off aligning to standard types.This seems to have the correct layout:
struct{ unsigned char min_perf; unsigned char max_perf; unsigned char desired; unsigned char energy_perf; unsigned int activity_window:10; bool package_control:1; unsigned int reserved:16; bool activity_window_valid:1; bool energy_perf_valid:1; bool desired_valid:1; bool max_perf_valid:1; bool min_perf_valid:1; } ;
Quoted 8 lines
Quoted 2 lines
Or would you prefer the first 8 bit ones to be unsigned int min_perf:8?
Personally I think using bitfields uniformly would be better. What you definitely cannot use if not using a bitfield is "unsigned char", it ought to by
uint8_tthen. If using a bitfield, as said, I think it's best to stick to unsigned int and bool, unless field width goes beyond 32 bits or fields cross a 32-bit boundary.
Ok, thanks.
Quoted 66 lines
Quoted 58 lines
Quoted 49 lines
Quoted 49 lines
docs/misc/xen-command-line.pandoc +49
-0+bool __init hwp_available(void) +{ + unsigned int eax, ecx, unused; + bool use_hwp; + + if ( boot_cpu_data.cpuid_level < CPUID_PM_LEAF ) + { + hwp_verbose("cpuid_level (%#x) lacks HWP support\n", + boot_cpu_data.cpuid_level); + return false; + } + + if ( boot_cpu_data.cpuid_level < 0x16 ) + { + hwp_info("HWP disabled: cpuid_level %#x < 0x16 lacks CPU freq info\n", + boot_cpu_data.cpuid_level); + return false; + } + + cpuid(CPUID_PM_LEAF, &eax, &unused, &ecx, &unused); + + if ( !(eax & CPUID6_EAX_HWP_ENERGY_PERFORMANCE_PREFERENCE) && + !(ecx & CPUID6_ECX_IA32_ENERGY_PERF_BIAS) ) + { + hwp_verbose("HWP disabled: No energy/performance preference available"); + return false; + } + + feature_hwp = eax & CPUID6_EAX_HWP; + feature_hwp_notification = eax & CPUID6_EAX_HWP_NOTIFICATION; + feature_hwp_activity_window = eax & CPUID6_EAX_HWP_ACTIVITY_WINDOW; + feature_hwp_energy_perf = + eax & CPUID6_EAX_HWP_ENERGY_PERFORMANCE_PREFERENCE; + feature_hwp_pkg_level_ctl = eax & CPUID6_EAX_HWP_PACKAGE_LEVEL_REQUEST; + feature_hwp_peci = eax & CPUID6_EAX_HWP_PECI; + + hwp_verbose("HWP: %d notify: %d act-window: %d energy-perf: %d pkg-level: %d peci: %d\n", + feature_hwp, feature_hwp_notification, + feature_hwp_activity_window, feature_hwp_energy_perf, + feature_hwp_pkg_level_ctl, feature_hwp_peci); + + if ( !feature_hwp ) + return false; + + feature_hdc = eax & CPUID6_EAX_HDC; + + hwp_verbose("HWP: Hardware Duty Cycling (HDC) %ssupported%s\n", + feature_hdc ? "" : "not ", + feature_hdc ? opt_cpufreq_hdc ? ", enabled" : ", disabled"Quoted 8 lines
docs/misc/xen-command-line.pandoc
Quoted 6 lines
docs/misc/xen-command-line.pandoc +6
-0+ : ""); + + feature_hdc = feature_hdc && opt_cpufreq_hdc; + + hwp_verbose("HWP: HW_FEEDBACK %ssupported\n", + (eax & CPUID6_EAX_HW_FEEDBACK) ? "" : "not ");You report this, but you don't really use it?
Quoted 7 lines
Correct. I needed to know what capabilities my processors have.
feature_hwp_pkg_level_ctlandfeature_hwp_pecican also be dropped since they aren't used beyond printing their values. I'd still lean toward keeping their printing under verbose since otherwise there isn't a convenient way to know if they are available without recompiling.
Quoted 4 lines
That's fine, but wants mentioning in the description. Also respective variables would want to be
__initdatathen, be local to the function, or be dropped altogether. Plus you'd want to be consistent - either you use a helper variable for all print-only features, or you don't.
Got it, thanks.
Quoted 14 lines
Quoted 14 lines
Quoted 13 lines
docs/misc/xen-command-line.pandoc
Quoted 10 lines
docs/misc/xen-command-line.pandoc +10
-0+ if ( rdmsr_safe(MSR_IA32_ENERGY_PERF_BIAS, val) ) + { + hwp_err("error rdmsr_safe(MSR_IA32_ENERGY_PERF_BIAS)\n"); + data->curr_req.raw = -1; + + return; + } + + data->energy_perf = val & IA32_ENERGY_BIAS_MASK; + }In order to not need to undo the "enable" you've already done, maybe that should move down here?
Quoted 4 lines
Quoted 2 lines
HWP needs to be enabled before the Capabilities and Request MSRs can be read.
I must have missed this aspect in the SDM. Do you have a pointer?
In 15.4.2 Enabling HWP
Additional MSRs associated with HWP may only be accessed after HWP is enabled, with the exception of IA32_HWP_INTERRUPT and MSR_PPERF. Accessing the IA32_HWP_INTERRUPT MSR requires only HWP is present as enumerated by CPUID but does not require enabling HWP.
Quoted 5 lines
Quoted 2 lines
Reading them shouldn't fail, but it seems safer to use
rdmsr_safein case something goes wrong.Sure. But then the "enable" will need undoing in the unlikely event of failure.
Yes.
Regards,
Jason
Re: [PATCH v3 04/14 RESEND] cpufreq: Add Hardware P-State (HWP) driver
Quoted 59 lines · Jason Andryuk
Quoted 58 lines · Jan Beulich
Quoted 55 lines · Jason Andryuk
Quoted 16 lines · Jan Beulich
docs/misc/xen-command-line.pandoc If set, force use of the performance counters for oprofile, rather than detectin · line 502
Quoted 8 lines · Jason Andryuk
docs/misc/xen-command-line.pandoc +1
-1@@ -499,7 +499,7 @@ If set, force use of the performance counters for oprofile, rather than detectin available support. ### cpufreq -> `= none | {{ <boolean> | xen } [:[powersave|performance|ondemand|userspace][,<maxfreq>][,[<minfreq>][,[verbose]]]]} | dom0-kernel` +> `= none | {{ <boolean> | xen } [:[powersave|performance|ondemand|userspace][,<hdc>][,[<hwp>]][,[<maxfreq>]][,[<minfreq>]][,[verbose]]]} | dom0-kernel`Considering you use a special internal governor, the 4 governor alternatives are meaningless for hwp. Hence at the command line level recognizing "hwp" as if it was another governor name would seem better to me. This would then also get rid of one of the two special "no-" prefix parsing cases (which I'm not overly happy about).
Quoted 5 lines
Even if not done that way I'm puzzled by the way you spell out the interaction of "hwp" and "hdc": As you say in the description, "hdc" is meaningful only when "hwp" was specified, so even if not merged with the governors group "hwp" should come first, and "hdc" ought to be rejected if "hwp" wasn't first specified. (The way you've spelled it out it actually looks to be kind of the other way around.)
I placed them in alphabetical order, but, yes, it doesn't make sense.
Quoted 11 lines
Strictly speaking "maxfreq" and "minfreq" also should be objected to when "hwp" was specified.
Overall I'm getting the impression that beyond your "verbose" related adjustment more is needed, if you're meaning to get things closer to how we parse the option (splitting across multiple lines to help see what I mean):
`= none
| {{ <boolean> | xen } [:{powersave|performance|ondemand|userspace} [{,hwp[,hdc]|[,maxfreq=<maxfreq>[,minfreq=<minfreq>]}] [,verbose]]}Quoted 7 lines
| dom0-kernel`
(We're still parsing in a more relaxed way, e.g. minfreq may come ahead of maxfreq, but better be more tight in the doc than too relaxed.)
Furthermore while max/min freq don't apply directly, there are still two MSRs controlling bounds at the package and logical processor levels.
Well, we only program the logical processor level MSRs because we don't have a good idea of the packages to know when we can skip writing an MSR.
How about this:
`= none| {{ <boolean> | xen } { [:{powersave|performance|ondemand|userspace}[,maxfreq=<maxfreq>[,minfreq=<minfreq>]] | [:hwp[,hdc]] } [,verbose]]}| dom0-kernel`
Quoted 7 lines
Quoted 1 line
Looks right, yes.
There is a wrinkle to using the hwp governor. The hwp governor was named "hwp-internal", so it needs to be renamed to "hwp" for use with command line parsing. That means the checking for "-internal" needs to change to just "hwp" which removes the generality of the original implementation.
I'm afraid I don't see why this would strictly be necessary or a consequence.
Quoted 4 lines
The other issue is that if you select "hwp" as the governor, but HWP hardware support is not available, then
hwp_available()needs to reset the governor back to the default. This feels like a layering violation.
Layering violation - yes. But why would the governor need resetting in this case? If HWP was asked for but isn't available, I don't think any other cpufreq handling (and hence governor) should be put in place. And turning off cpufreq altogether (if necessary in the first place) wouldn't, to me, feel as much like a layering violation.
Quoted 2 lines
I'm still investigating, but promoting hwp to a top level option - cpufreq=hwp - might be a better arrangement.
Might be an alternative, yes.
Jan
Re: [PATCH v3 04/14 RESEND] cpufreq: Add Hardware P-State (HWP) driver
Quoted 63 lines · Jan Beulich
Quoted 61 lines · Jason Andryuk
Quoted 59 lines · Jan Beulich
Quoted 48 lines · Jason Andryuk
Quoted 16 lines · Jan Beulich
docs/misc/xen-command-line.pandoc If set, force use of the performance counters for oprofile, rather than detectin · line 502
Quoted 8 lines · Jason Andryuk
docs/misc/xen-command-line.pandoc +1
-1@@ -499,7 +499,7 @@ If set, force use of the performance counters for oprofile, rather than detectin available support. ### cpufreq -> `= none | {{ <boolean> | xen } [:[powersave|performance|ondemand|userspace][,<maxfreq>][,[<minfreq>][,[verbose]]]]} | dom0-kernel` +> `= none | {{ <boolean> | xen } [:[powersave|performance|ondemand|userspace][,<hdc>][,[<hwp>]][,[<maxfreq>]][,[<minfreq>]][,[verbose]]]} | dom0-kernel`Considering you use a special internal governor, the 4 governor alternatives are meaningless for hwp. Hence at the command line level recognizing "hwp" as if it was another governor name would seem better to me. This would then also get rid of one of the two special "no-" prefix parsing cases (which I'm not overly happy about).
Quoted 5 lines
Even if not done that way I'm puzzled by the way you spell out the interaction of "hwp" and "hdc": As you say in the description, "hdc" is meaningful only when "hwp" was specified, so even if not merged with the governors group "hwp" should come first, and "hdc" ought to be rejected if "hwp" wasn't first specified. (The way you've spelled it out it actually looks to be kind of the other way around.)
I placed them in alphabetical order, but, yes, it doesn't make sense.
Quoted 11 lines
Strictly speaking "maxfreq" and "minfreq" also should be objected to when "hwp" was specified.
Overall I'm getting the impression that beyond your "verbose" related adjustment more is needed, if you're meaning to get things closer to how we parse the option (splitting across multiple lines to help see what I mean):
`= none
| {{ <boolean> | xen } [:{powersave|performance|ondemand|userspace} [{,hwp[,hdc]|[,maxfreq=<maxfreq>[,minfreq=<minfreq>]}] [,verbose]]}Quoted 7 lines
| dom0-kernel`
(We're still parsing in a more relaxed way, e.g. minfreq may come ahead of maxfreq, but better be more tight in the doc than too relaxed.)
Furthermore while max/min freq don't apply directly, there are still two MSRs controlling bounds at the package and logical processor levels.
Well, we only program the logical processor level MSRs because we don't have a good idea of the packages to know when we can skip writing an MSR.
Quoted 7 lines
How about this:
`= none| {{ <boolean> | xen } { [:{powersave|performance|ondemand|userspace}[,maxfreq=<maxfreq>[,minfreq=<minfreq>]] | [:hwp[,hdc]] } [,verbose]]}| dom0-kernel`
Looks right, yes.
Quoted 8 lines
Quoted 5 lines
There is a wrinkle to using the hwp governor. The hwp governor was named "hwp-internal", so it needs to be renamed to "hwp" for use with command line parsing. That means the checking for "-internal" needs to change to just "hwp" which removes the generality of the original implementation.
I'm afraid I don't see why this would strictly be necessary or a consequence.
Maybe I took your comment too far when you mentioned using hwp as a fake governor. I used the actual HWP struct cpufreq_governor to hook into cpufreq_cmdline_parse(). cpufreq_cmdline_parse() uses the that name for comparison. But the naming stops being an issue if struct cpufreq_governor gains a bool .internal flag. That flag also makes the registration checks clearer.
Quoted 10 lines
Quoted 4 lines
The other issue is that if you select "hwp" as the governor, but HWP hardware support is not available, then
hwp_available()needs to reset the governor back to the default. This feels like a layering violation.Layering violation - yes. But why would the governor need resetting in this case? If HWP was asked for but isn't available, I don't think any other cpufreq handling (and hence governor) should be put in place. And turning off cpufreq altogether (if necessary in the first place) wouldn't, to me, feel as much like a layering violation.
My goal was for Xen to use HWP if available and fallback to the acpi cpufreq driver if not. That to me seems more user-friendly than disabling cpufreq.
if ( hwp_available() )
ret = hwp_register_driver();
else
ret = cpufreq_register_driver(&acpi_cpufreq_driver);If we are setting cpufreq_opt_governor to enter hwp_available(), but then HWP isn't available, it seems to me that we need to reset cpufreq_opt_governor when exiting hwp_available() false.
Regards,
Jason
Re: [PATCH v3 04/14 RESEND] cpufreq: Add Hardware P-State (HWP) driver
Quoted 14 lines · Jason Andryuk
Quoted 7 lines · Jan Beulich
Quoted 5 lines · Jason Andryuk
On Fri, May 5, 2023 at 3:01 AM Jan Beulich <[email protected]> wrote:
The other issue is that if you select "hwp" as the governor, but HWP hardware support is not available, thenhwp_available()needs to reset the governor back to the default. This feels like a layering violation.Quoted 5 lines
Layering violation - yes. But why would the governor need resetting in this case? If HWP was asked for but isn't available, I don't think any other cpufreq handling (and hence governor) should be put in place. And turning off cpufreq altogether (if necessary in the first place) wouldn't, to me, feel as much like a layering violation.
Quoted 8 lines
My goal was for Xen to use HWP if available and fallback to the acpi cpufreq driver if not. That to me seems more user-friendly than disabling cpufreq.
if ( hwp_available() ) ret = hwp_register_driver(); else ret = cpufreq_register_driver(&acpi_cpufreq_driver);
That's fine as a (future) default, but for now using hwp requires a command line option, and if that option says "hwp" then it ought to be hwp imo.
Quoted 3 lines
If we are setting
cpufreq_opt_governorto enterhwp_available(), but then HWP isn't available, it seems to me that we need to resetcpufreq_opt_governorwhen exitinghwp_available()false.
This may be necessary in the future, but shouldn't be necessary right now. It's not entirely clear to me how that future is going to look like, command line option wise.
Jan
Re: [PATCH v3 04/14 RESEND] cpufreq: Add Hardware P-State (HWP) driver
Quoted 19 lines · Jan Beulich
Quoted 18 lines · Jason Andryuk
Quoted 7 lines · Jan Beulich
Quoted 5 lines · Jason Andryuk
On Fri, May 5, 2023 at 3:01 AM Jan Beulich <[email protected]> wrote:
The other issue is that if you select "hwp" as the governor, but HWP hardware support is not available, thenhwp_available()needs to reset the governor back to the default. This feels like a layering violation.Quoted 5 lines
Layering violation - yes. But why would the governor need resetting in this case? If HWP was asked for but isn't available, I don't think any other cpufreq handling (and hence governor) should be put in place. And turning off cpufreq altogether (if necessary in the first place) wouldn't, to me, feel as much like a layering violation.
My goal was for Xen to use HWP if available and fallback to the acpi cpufreq driver if not. That to me seems more user-friendly than disabling cpufreq.
Quoted 8 lines
Quoted 4 lines
if ( hwp_available() ) ret = hwp_register_driver(); else ret = cpufreq_register_driver(&acpi_cpufreq_driver);That's fine as a (future) default, but for now using hwp requires a command line option, and if that option says "hwp" then it ought to be hwp imo.
As a downstrem distribution, I'd strongly prefer to have an option that would enable HWP when present and fallback to other driver otherwise, even if that isn't the default upstream. I can't possibly require large group of users (either HWP-having or HWP-not-having) to edit the Xen cmdline to get power management working well.
If the meaning for cpufreq=hwp absolutely must include "nothing if HWP is not available", then maybe it should be named cpufreq=try-hwp instead, or cpufreq=prefer-hwp or something else like this?
Quoted 10 lines
Quoted 3 lines
If we are setting
cpufreq_opt_governorto enterhwp_available(), but then HWP isn't available, it seems to me that we need to resetcpufreq_opt_governorwhen exitinghwp_available()false.This may be necessary in the future, but shouldn't be necessary right now. It's not entirely clear to me how that future is going to look like, command line option wise.
Jan
Signature · 3 lines
Best Regards, Marek Marczykowski-Górecki Invisible Things Lab
Re: [PATCH v3 04/14 RESEND] cpufreq: Add Hardware P-State (HWP) driver
Quoted 35 lines · Marek Marczykowski-Górecki
Quoted 19 lines · Jan Beulich
Quoted 18 lines · Jason Andryuk
Quoted 7 lines · Jan Beulich
Quoted 5 lines · Jason Andryuk
On Fri, May 5, 2023 at 3:01 AM Jan Beulich <[email protected]> wrote:
The other issue is that if you select "hwp" as the governor, but HWP hardware support is not available, thenhwp_available()needs to reset the governor back to the default. This feels like a layering violation.Quoted 5 lines
Layering violation - yes. But why would the governor need resetting in this case? If HWP was asked for but isn't available, I don't think any other cpufreq handling (and hence governor) should be put in place. And turning off cpufreq altogether (if necessary in the first place) wouldn't, to me, feel as much like a layering violation.
My goal was for Xen to use HWP if available and fallback to the acpi cpufreq driver if not. That to me seems more user-friendly than disabling cpufreq.
Quoted 8 lines
Quoted 4 lines
if ( hwp_available() ) ret = hwp_register_driver(); else ret = cpufreq_register_driver(&acpi_cpufreq_driver);That's fine as a (future) default, but for now using hwp requires a command line option, and if that option says "hwp" then it ought to be hwp imo.
As a downstrem distribution, I'd strongly prefer to have an option that would enable HWP when present and fallback to other driver otherwise, even if that isn't the default upstream. I can't possibly require large group of users (either HWP-having or HWP-not-having) to edit the Xen cmdline to get power management working well.
Quoted 3 lines
If the meaning for cpufreq=hwp absolutely must include "nothing if HWP is not available", then maybe it should be named cpufreq=try-hwp instead, or cpufreq=prefer-hwp or something else like this?
Any new sub-option needs to fit the existing ones in its meaning. I could see e.g. "cpufreq=xen" alone to effect what you want (once hwp becomes available for use by default). But (for now at least) I continue to think that a request for "hwp" ought to mean HWP.
Jan
PATCH RESEND v3 5/14 xenpm: Change get-cpufreq-para output for internal
In reply to Jason AndryukWhen using HWP, some of the returned data is not applicable. In that case, we should just omit it to avoid confusing the user. So switch to printing the base and turbo frequencies since those are relevant to HWP. Similarly, stop printing the CPU frequencies since those do not apply.
---
v2:
Use full governor name XEN_HWP_GOVERNOR to change output Style fixes
--- tools/misc/xenpm.c | 41 +++++++++++++++++++++++++---------------- 1 file changed, 25 insertions(+), 16 deletions(-)
tools/misc/xenpm.c +25 -16
@@ -711,6 +711,7 @@ void start_gather_func(int argc, char *argv[])/* print out parameters about cpu frequency */ static void print_cpufreq_para (int cpuid,struct xc_get_cpufreq_para *p_cpufreq) { +bool internal =strstr (p_cpufreq->scaling_governor,XEN_HWP_GOVERNOR );int i;printf ("cpu id : %d\n" , cpuid);
@@ -720,10 +721,15 @@ static void print_cpufreq_para(int cpuid, struct xc_get_cpufreq_para *p_cpufreq)printf (" %d" , p_cpufreq->affected_cpus[i]);printf ("\n" ); -printf ("cpuinfo frequency : max [%u] min [%u] cur [%u]\n" , - p_cpufreq->cpuinfo_max_freq, - p_cpufreq->cpuinfo_min_freq, - p_cpufreq->cpuinfo_cur_freq); +if ( internal ) +printf ("cpuinfo frequency : base [%u] turbo [%u]\n" , + p_cpufreq->cpuinfo_min_freq, + p_cpufreq->cpuinfo_max_freq); +else +printf ("cpuinfo frequency : max [%u] min [%u] cur [%u]\n" , + p_cpufreq->cpuinfo_max_freq, + p_cpufreq->cpuinfo_min_freq, + p_cpufreq->cpuinfo_cur_freq);printf ("scaling_driver : %s\n" , p_cpufreq->scaling_driver);
@@ -750,19 +756,22 @@ static void print_cpufreq_para(int cpuid, struct xc_get_cpufreq_para *p_cpufreq) p_cpufreq->u.ondemand.up_threshold); } -printf ("scaling_avail_freq :" ); -for ( i =0 ; i < p_cpufreq->freq_num; i++ ) -if ( p_cpufreq->scaling_available_frequencies[i] == - p_cpufreq->scaling_cur_freq ) -printf (" *%d" , p_cpufreq->scaling_available_frequencies[i]); -else -printf (" %d" , p_cpufreq->scaling_available_frequencies[i]); -printf ("\n" ); +if ( !internal ) + { +printf ("scaling_avail_freq :" ); +for ( i =0 ; i < p_cpufreq->freq_num; i++ ) +if ( p_cpufreq->scaling_available_frequencies[i] == + p_cpufreq->scaling_cur_freq ) +printf (" *%d" , p_cpufreq->scaling_available_frequencies[i]); +else +printf (" %d" , p_cpufreq->scaling_available_frequencies[i]); +printf ("\n" ); -printf ("scaling frequency : max [%u] min [%u] cur [%u]\n" , - p_cpufreq->scaling_max_freq, - p_cpufreq->scaling_min_freq, - p_cpufreq->scaling_cur_freq); +printf ("scaling frequency : max [%u] min [%u] cur [%u]\n" , + p_cpufreq->scaling_max_freq, + p_cpufreq->scaling_min_freq, + p_cpufreq->scaling_cur_freq); + }printf ("turbo mode : %s\n" , p_cpufreq->turbo_enabled ?"enabled" :"disabled or n/a" );
Signature · 1 line
2.40.0
Re: [PATCH v3 05/14 RESEND] xenpm: Change get-cpufreq-para output for internal
Quoted 4 lines · Jason Andryuk
When using HWP, some of the returned data is not applicable. In that case, we should just omit it to avoid confusing the user. So switch to printing the base and turbo frequencies since those are relevant to HWP. Similarly, stop printing the CPU frequencies since those do not apply.
It vaguely feels like I have asked this before: Can you point me at a place in the SDM where it is said that CPUID 0x16's "Maximum Frequency" is the turbo frequency? Without such a reference I feel a little uneasy with ...
tools/misc/xenpm.c static void print_cpufreq_para(int cpuid, struct xc_get_cpufreq_para *p_cpufreq) · line 727
Quoted 12 lines
tools/misc/xenpm.c +4
-4@@ -720,10 +721,15 @@ static void print_cpufreq_para(int cpuid, struct xc_get_cpufreq_para *p_cpufreq)printf (" %d" , p_cpufreq->affected_cpus[i]);printf ("\n" ); -printf ("cpuinfo frequency : max [%u] min [%u] cur [%u]\n" , - p_cpufreq->cpuinfo_max_freq, - p_cpufreq->cpuinfo_min_freq, - p_cpufreq->cpuinfo_cur_freq); +if ( internal ) +printf ("cpuinfo frequency : base [%u] turbo [%u]\n" , + p_cpufreq->cpuinfo_min_freq, + p_cpufreq->cpuinfo_max_freq);
... calling it "turbo" (and not "max") here.
Jan
Quoted 8 lines
tools/misc/xenpm.c +5
-0+else +printf ("cpuinfo frequency : max [%u] min [%u] cur [%u]\n" , + p_cpufreq->cpuinfo_max_freq, + p_cpufreq->cpuinfo_min_freq, + p_cpufreq->cpuinfo_cur_freq);printf ("scaling_driver : %s\n" , p_cpufreq->scaling_driver);
Re: [PATCH v3 05/14 RESEND] xenpm: Change get-cpufreq-para output for internal
Quoted 11 lines · Jan Beulich
Quoted 4 lines · Jason Andryuk
When using HWP, some of the returned data is not applicable. In that case, we should just omit it to avoid confusing the user. So switch to printing the base and turbo frequencies since those are relevant to HWP. Similarly, stop printing the CPU frequencies since those do not apply.
It vaguely feels like I have asked this before: Can you point me at a place in the SDM where it is said that CPUID 0x16's "Maximum Frequency" is the turbo frequency? Without such a reference I feel a little uneasy with ...
I don't have a reference, but I found it empirically to match the "turbo" frequency.
For an Intel® Core™ i7-10810U,
https://ark.intel.com/content/www/us/en/ark/products/201888/intel-core-i710810u-processor-12m-cache-up-to-4-90-ghz.html
Max Turbo Frequency 4.90 GHz
# xenpm get-cpufreq-para cpu id : 0 affected_cpus : 0 cpuinfo frequency : base [1600000] turbo [4900000]
Turbo has to be enabled to reach (close to) that frequency.
From my cover letter:
This is for a 10th gen 6-core 1600 MHz base 4900 MHZ max cpu. In the default balance mode, Turbo Boost doesn't exceed 4GHz. Tweaking the energy_perf preference with xenpm set-cpufreq-hwp balance ene:64, I've seen the CPU hit 4.7GHz before throttling down and bouncing around between 4.3 and 4.5 GHz. Curiously the other cores read ~4GHz when turbo boost takes affect. This was done after pinning all dom0 cores, and using taskset to pin to vCPU/pCPU 11 and running a bash tightloop.
Quoted 4 lines
Quoted 4 lines
tools/misc/xenpm.c +0
-0@@ -720,10 +721,15 @@ static void print_cpufreq_para(int cpuid, struct xc_get_cpufreq_para *p_cpufreq)printf (" %d" , p_cpufreq->affected_cpus[i]);printf ("\n" );
Quoted 10 lines
tools/misc/xenpm.c static void print_cpufreq_para(int cpuid, struct xc_get_cpufreq_para *p_cpufreq) · line 727
Quoted 8 lines
tools/misc/xenpm.c +4
-4-printf ("cpuinfo frequency : max [%u] min [%u] cur [%u]\n" , - p_cpufreq->cpuinfo_max_freq, - p_cpufreq->cpuinfo_min_freq, - p_cpufreq->cpuinfo_cur_freq); +if ( internal ) +printf ("cpuinfo frequency : base [%u] turbo [%u]\n" , + p_cpufreq->cpuinfo_min_freq, + p_cpufreq->cpuinfo_max_freq);... calling it "turbo" (and not "max") here.
I'm fine with "max". I think I went with turbo since it's a value you cannot sustain but can only hit in short bursts.
Regards,
Jason
Re: [PATCH v3 05/14 RESEND] xenpm: Change get-cpufreq-para output for internal
Quoted 28 lines · Jason Andryuk
Quoted 11 lines · Jan Beulich
Quoted 4 lines · Jason Andryuk
When using HWP, some of the returned data is not applicable. In that case, we should just omit it to avoid confusing the user. So switch to printing the base and turbo frequencies since those are relevant to HWP. Similarly, stop printing the CPU frequencies since those do not apply.
It vaguely feels like I have asked this before: Can you point me at a place in the SDM where it is said that CPUID 0x16's "Maximum Frequency" is the turbo frequency? Without such a reference I feel a little uneasy with ...
I don't have a reference, but I found it empirically to match the "turbo" frequency.
For an Intel® Core™ i7-10810U,
https://ark.intel.com/content/www/us/en/ark/products/201888/intel-core-i710810u-processor-12m-cache-up-to-4-90-ghz.htmlMax Turbo Frequency 4.90 GHz
# xenpm get-cpufreq-para cpu id : 0 affected_cpus : 0 cpuinfo frequency : base [1600000] turbo [4900000]Turbo has to be enabled to reach (close to) that frequency.
Quoted 8 lines
From my cover letter:
This is for a 10th gen 6-core 1600 MHz base 4900 MHZ max cpu. In the default balance mode, Turbo Boost doesn't exceed 4GHz. Tweaking theenergy_perfpreference withxenpm set-cpufreq-hwp balance ene:64, I've seen the CPU hit 4.7GHz before throttling down and bouncing around between 4.3 and 4.5 GHz. Curiously the other cores read ~4GHz when turbo boost takes affect. This was done after pinning all dom0 cores, and using taskset to pin to vCPU/pCPU 11 and running a bash tightloop.
Right, but what matters for the longer term future is what gets committed (and the cover letter won't be). IOW ...
Quoted 15 lines
Quoted 4 lines
Quoted 4 lines
tools/misc/xenpm.c +0
-0@@ -720,10 +721,15 @@ static void print_cpufreq_para(int cpuid, struct xc_get_cpufreq_para *p_cpufreq)printf (" %d" , p_cpufreq->affected_cpus[i]);printf ("\n" );Quoted 10 lines
tools/misc/xenpm.c static void print_cpufreq_para(int cpuid, struct xc_get_cpufreq_para *p_cpufreq) · line 727
Quoted 8 lines
tools/misc/xenpm.c +4
-4-printf ("cpuinfo frequency : max [%u] min [%u] cur [%u]\n" , - p_cpufreq->cpuinfo_max_freq, - p_cpufreq->cpuinfo_min_freq, - p_cpufreq->cpuinfo_cur_freq); +if ( internal ) +printf ("cpuinfo frequency : base [%u] turbo [%u]\n" , + p_cpufreq->cpuinfo_min_freq, + p_cpufreq->cpuinfo_max_freq);... calling it "turbo" (and not "max") here.
Quoted 2 lines
I'm fine with "max". I think I went with turbo since it's a value you cannot sustain but can only hit in short bursts.
... I don't mind you sticking to "turbo" as long as the description makes clear why that was chosen despite the SDM not naming it this way.
Jan
Re: [PATCH v3 05/14 RESEND] xenpm: Change get-cpufreq-para output for internal
Quoted 15 lines · Jan Beulich
Quoted 15 lines
Quoted 14 lines
tools/misc/xenpm.c static void print_cpufreq_para(int cpuid, struct xc_get_cpufreq_para *p_cpufreq) · line 727
Quoted 12 lines
tools/misc/xenpm.c +4
-4@@ -720,10 +721,15 @@ static void print_cpufreq_para(int cpuid, struct xc_get_cpufreq_para *p_cpufreq)printf (" %d" , p_cpufreq->affected_cpus[i]);printf ("\n" ); -printf ("cpuinfo frequency : max [%u] min [%u] cur [%u]\n" , - p_cpufreq->cpuinfo_max_freq, - p_cpufreq->cpuinfo_min_freq, - p_cpufreq->cpuinfo_cur_freq); +if ( internal ) +printf ("cpuinfo frequency : base [%u] turbo [%u]\n" , + p_cpufreq->cpuinfo_min_freq, + p_cpufreq->cpuinfo_max_freq);... calling it "turbo" (and not "max") here.
Quoted 5 lines
Quoted 2 lines
I'm fine with "max". I think I went with turbo since it's a value you cannot sustain but can only hit in short bursts.
... I don't mind you sticking to "turbo" as long as the description makes clear why that was chosen despite the SDM not naming it this way.
I switched to "max" since as you point out that matches the SDM naming.
Regards,
Jason
PATCH RESEND v3 6/14 xen/x86: Tweak PDC bits when using HWP
In reply to Jason AndryukQubes testing of HWP support had a report of a laptop, Thinkpad X1 Carbon Gen 4 with a Skylake processor, locking up during boot when HWP is enabled. A user found a kernel bug that seems to be the same issue:
https://bugzilla.kernel.org/show_bug.cgi?id=110941.
That bug was fixed by Linux commit a21211672c9a ("ACPI / processor:
Request native thermal interrupt handling via _OSC"). The tl;dr is SMM crashes when it receives thermal interrupts, so Linux calls the ACPI _OSC method to take over interrupt handling.
The Linux fix looks at the CPU features to decide whether or not to call _OSC with bit 12 set to take over native interrupt handling. Xen needs some way to communicate HWP to Dom0 for making an equivalent call.
Xen exposes modified PDC bits via the platform_op set_pminfo hypercall. Expand that to set bit 12 when HWP is present and in use.
Any generated interrupt would be handled by Xen's thermal drive, which clears the status.
Bit 12 isn't named in the linux header and is open coded in Linux's usage.
This will need a corresponding linux patch to pick up and apply the PDC bits.
---
New in v3
xen/arch/x86/acpi/cpufreq/hwp.c | 16 +++++++++++----- xen/arch/x86/acpi/lib.c | 5 +++++ xen/arch/x86/cpu/mcheck/mce_intel.c | 6 ++++++ xen/arch/x86/include/asm/msr-index.h | 1 + xen/include/acpi/cpufreq/processor_perf.h | 1 + xen/include/acpi/pdc_intel.h | 1 + 6 files changed, 25 insertions(+), 5 deletions(-)
xen/arch/x86/acpi/cpufreq/hwp.c +11 -5
@@ -13,6 +13,8 @@#include <asm/msr.h> #include <acpi/cpufreq/cpufreq.h> +static bool hwp_in_use; +static bool feature_hwp;static bool feature_hwp_notification;static bool feature_hwp_activity_window;
@@ -117,10 +119,14 @@ static int __init cf_check cpufreq_gov_hwp_init(void) }__initcall (cpufreq_gov_hwp_init); +bool hwp_active (void ) +{ +return hwp_in_use; +} +bool __init hwp_available (void ) {unsigned int eax, ecx, unused; -bool use_hwp;if ( boot_cpu_data.cpuid_level <CPUID_PM_LEAF ) {
@@ -173,13 +179,13 @@ bool __init hwp_available(void)hwp_verbose ("HWP: HW_FEEDBACK %ssupported\n" , (eax &CPUID6_EAX_HW_FEEDBACK ) ?"" :"not " ); - use_hwp = feature_hwp && opt_cpufreq_hwp; - cpufreq_governor_internal = use_hwp; + hwp_in_use = feature_hwp && opt_cpufreq_hwp; + cpufreq_governor_internal = hwp_in_use; -if ( use_hwp ) +if ( hwp_in_use )hwp_info ("Using HWP for cpufreq\n" ); -return use_hwp; +return hwp_in_use; }static void hdc_set_pkg_hdc_ctl (bool val)
xen/arch/x86/acpi/lib.c +5 -0
@@ -26,6 +26,8 @@#include <asm/fixmap.h> #include <asm/mwait.h> +#include <acpi/cpufreq/processor_perf.h> +u32 __read_mostly acpi_smi_cmd;u8 __read_mostly acpi_enable_value;u8 __read_mostly acpi_disable_value;
@@ -140,5 +142,8 @@ int arch_acpi_set_pdc_bits(u32 acpi_id, u32 *pdc, u32 mask) !(ecx & CPUID5_ECX_INTERRUPT_BREAK)) pdc[2 ] &= ~(ACPI_PDC_C_C1_FFH |ACPI_PDC_C_C2C3_FFH ); +if (hwp_active ()) + pdc[2 ] |=ACPI_PDC_CPPC_NTV_INT ; +return 0 ; }
xen/arch/x86/cpu/mcheck/mce_intel.c +6 -0
@@ -15,6 +15,9 @@#include <asm/p2m.h> #include <asm/mce.h> #include <asm/apic.h> + +#include <acpi/cpufreq/processor_perf.h> +#include "mce.h" #include "x86_mca.h" #include "barrier.h"
@@ -64,6 +67,9 @@ static void cf_check intel_thermal_interrupt(struct cpu_user_regs *regs)ack_APIC_irq (); +if (hwp_active () ) +wrmsr_safe (MSR_IA32_HWP_STATUS ,0 ); +if (NOW () <per_cpu (next, cpu) )return ;
xen/arch/x86/include/asm/msr-index.h +1 -0
@@ -157,6 +157,7 @@#define MSR_IA32_HWP_CAPABILITIES 0x00000771#define MSR_IA32_HWP_INTERRUPT 0x00000773#define MSR_IA32_HWP_REQUEST 0x00000774 +#define MSR_IA32_HWP_STATUS 0x00000777#define MSR_X2APIC_FIRST 0x00000800#define MSR_X2APIC_LAST 0x000008ff
xen/include/acpi/cpufreq/processor_perf.h +1 -0
@@ -8,6 +8,7 @@#define XEN_PX_INIT 0x80000000bool hwp_available (void ); +bool hwp_active (void );int hwp_register_driver (void );int powernow_cpufreq_init (void );
xen/include/acpi/pdc_intel.h +1 -0
@@ -17,6 +17,7 @@#define ACPI_PDC_C_C1_FFH (0x0100)#define ACPI_PDC_C_C2C3_FFH (0x0200)#define ACPI_PDC_SMP_P_HWCOORD (0x0800) +#define ACPI_PDC_CPPC_NTV_INT (0x1000)#define ACPI_PDC_EST_CAPABILITY_SMP (ACPI_PDC_SMP_C1PT | \ ACPI_PDC_C_C1_HALT | \
Signature · 1 line
2.40.0
Re: [PATCH v3 06/14 RESEND] xen/x86: Tweak PDC bits when using HWP
xen/arch/x86/acpi/cpufreq/hwp.c line 16
Quoted 7 lines · Jason Andryuk
xen/arch/x86/acpi/cpufreq/hwp.c +1
-0@@ -13,6 +13,8 @@#include <asm/msr.h> #include <acpi/cpufreq/cpufreq.h> +static bool hwp_in_use;
__ro_after_init again, please.
xen/include/acpi/pdc_intel.h line 20
Quoted 7 lines
xen/include/acpi/pdc_intel.h +1
-0@@ -17,6 +17,7 @@#define ACPI_PDC_C_C1_FFH (0x0100)#define ACPI_PDC_C_C2C3_FFH (0x0200)#define ACPI_PDC_SMP_P_HWCOORD (0x0800) +#define ACPI_PDC_CPPC_NTV_INT (0x1000)
I can probably live with NTV (albeit I'd prefer NATIVE), but INT is too ambiguous for my taste: Can at least that become INTR, please?
With at least the minimal adjustments
Jan
Re: [PATCH v3 06/14 RESEND] xen/x86: Tweak PDC bits when using HWP
Quoted 11 lines · Jan Beulich
xen/arch/x86/acpi/cpufreq/hwp.c line 16
Quoted 7 lines · Jason Andryuk
xen/arch/x86/acpi/cpufreq/hwp.c +1
-0@@ -13,6 +13,8 @@#include <asm/msr.h> #include <acpi/cpufreq/cpufreq.h> +static bool hwp_in_use;
__ro_after_initagain, please.
Of course. (I'd already made the change locally after the earlier ones.)
Quoted 10 lines
xen/include/acpi/pdc_intel.h line 20
Quoted 7 lines
xen/include/acpi/pdc_intel.h +1
-0@@ -17,6 +17,7 @@#define ACPI_PDC_C_C1_FFH (0x0100)#define ACPI_PDC_C_C2C3_FFH (0x0200)#define ACPI_PDC_SMP_P_HWCOORD (0x0800) +#define ACPI_PDC_CPPC_NTV_INT (0x1000)I can probably live with NTV (albeit I'd prefer NATIVE), but INT is too ambiguous for my taste: Can at least that become INTR, please?
Sounds good. I'm switching to ACPI_PDC_CPPC_NATIVE_INTR.
Quoted 2 lines
With at least the minimal adjustments
Reviewed-by Jan Beulich <[email protected]>
Thank you.
Regards,
Jason
PATCH RESEND v3 7/14 cpufreq: Export HWP parameters to userspace
In reply to Jason AndryukExtend xen_get_cpufreq_para to return hwp parameters. These match the hardware rather closely.
We need the features bitmask to indicated fields supported by the actual hardware.
The use of uint8_t parameters matches the hardware size. uint32_t entries grows the sysctl_t past the build assertion in setup.c. The uint8_t ranges are supported across multiple generations, so hopefully they won't change.
---
v2:
Style fixes
Don't bump XEN_SYSCTL_INTERFACE_VERSION
Drop cpufreq.h comment divider
Expand xen_hwp_para comment
Add HWP activity window mantissa/exponent defines
Handle union rename
Add const to get_hwp_para
Remove hw_ prefix from xen_hwp_para members
Use XEN_HWP_GOVERNOR
Use per_cpu for hwp_drv_data
--- xen/arch/x86/acpi/cpufreq/hwp.c | 25 +++++++++++++++++++++++++ xen/drivers/acpi/pmstat.c | 5 +++++ xen/include/acpi/cpufreq/cpufreq.h | 2 ++ xen/include/public/sysctl.h | 26 ++++++++++++++++++++++++++ 4 files changed, 58 insertions(+)
xen/arch/x86/acpi/cpufreq/hwp.c +25 -0
@@ -506,6 +506,31 @@ static const struct cpufreq_driver __initconstrel hwp_cpufreq_driver = .update = hwp_cpufreq_update, }; +int get_hwp_para (const struct cpufreq_policy *policy, +struct xen_hwp_para *hwp_para) +{ +unsigned int cpu = policy->cpu; +const struct hwp_drv_data *data =per_cpu (hwp_drv_data, cpu); + +if ( data ==NULL ) +return -EINVAL ; + + hwp_para->features = + (feature_hwp_activity_window ?XEN_SYSCTL_HWP_FEAT_ACT_WINDOW :0 ) | + (feature_hwp_energy_perf ?XEN_SYSCTL_HWP_FEAT_ENERGY_PERF :0 ); + hwp_para->lowest = data->hw.lowest; + hwp_para->most_efficient = data->hw.most_efficient; + hwp_para->guaranteed = data->hw.guaranteed; + hwp_para->highest = data->hw.highest; + hwp_para->minimum = data->minimum; + hwp_para->maximum = data->maximum; + hwp_para->energy_perf = data->energy_perf; + hwp_para->activity_window = data->activity_window; + hwp_para->desired = data->desired; + +return 0 ; +} +int __init hwp_register_driver (void ) {return cpufreq_register_driver (&hwp_cpufreq_driver);
xen/drivers/acpi/pmstat.c +5 -0
@@ -290,6 +290,11 @@ static int get_cpufreq_para(struct xen_sysctl_pm_op *op) &op->u.get_para.u.ondemand.sampling_rate, &op->u.get_para.u.ondemand.up_threshold); } + +if ( !strncasecmp (op->u.get_para.scaling_governor,XEN_HWP_GOVERNOR , +CPUFREQ_NAME_LEN ) ) + ret =get_hwp_para (policy, &op->u.get_para.u.hwp_para); + op->u.get_para.turbo_enabled =cpufreq_get_turbo_status (op->cpuid);return ret;
xen/include/acpi/cpufreq/cpufreq.h +2 -0
@@ -247,5 +247,7 @@ void intel_feature_detect(struct cpufreq_policy *policy);extern bool opt_cpufreq_hwp;extern bool opt_cpufreq_hdc; +int get_hwp_para (const struct cpufreq_policy *policy, +struct xen_hwp_para *hwp_para);#endif /* __XEN_CPUFREQ_PM_H__ */
xen/include/public/sysctl.h +26 -0
@@ -292,6 +292,31 @@ struct xen_ondemand {uint32_t up_threshold; }; +struct xen_hwp_para { +/* +* bits 6:0 - 7bit mantissa +* bits 9:7 - 3bit base-10 exponent +* btis 15:10 - Unused - must be 0 +*/ +#define HWP_ACT_WINDOW_MANTISSA_MASK 0x7f +#define HWP_ACT_WINDOW_EXPONENT_MASK 0x7 +#define HWP_ACT_WINDOW_EXPONENT_SHIFT 7 +uint16_t activity_window; +/* energy_perf range 0-255 if 1. Otherwise 0-15 */ +#define XEN_SYSCTL_HWP_FEAT_ENERGY_PERF (1 << 0) +/* activity_window supported if 1 */ +#define XEN_SYSCTL_HWP_FEAT_ACT_WINDOW (1 << 1) +uint8_t features;/* bit flags for features */ +uint8_t lowest; +uint8_t most_efficient; +uint8_t guaranteed; +uint8_t highest; +uint8_t minimum; +uint8_t maximum; +uint8_t desired; +uint8_t energy_perf; +}; +#define XEN_HWP_GOVERNOR "hwp-internal"/* * cpufreq para name of this structure named
@@ -324,6 +349,7 @@ struct xen_get_cpufreq_para {union {struct xen_userspace userspace;struct xen_ondemand ondemand; +struct xen_hwp_para hwp_para; } u;int32_t turbo_enabled;
Signature · 1 line
2.40.0
Re: [PATCH v3 07/14 RESEND] cpufreq: Export HWP parameters to userspace
Quoted 10 lines · Jason Andryuk
Extend
xen_get_cpufreq_parato return hwp parameters. These match the hardware rather closely.We need the features bitmask to indicated fields supported by the actual hardware.
The use of
uint8_tparameters matches the hardware size.uint32_tentries grows thesysctl_tpast the build assertion insetup.c. Theuint8_tranges are supported across multiple generations, so hopefully they won't change.
Still it feels a little odd for values to be this narrow. Aiui the scaling_governor[] and scaling_{max,min}_freq fields aren't (really) used by HWP. So you could widen the union in struct xen_get_cpufreq_para (in a binary but not necessarily source compatible manner), gaining you 6 more uint32_t slots. Possibly the somewhat oddly placed scaling_cur_freq could be included as well ...
xen/arch/x86/acpi/cpufreq/hwp.c static const struct cpufreq_driver __initconstrel hwp_cpufreq_driver = · line 509
Quoted 7 lines
xen/arch/x86/acpi/cpufreq/hwp.c +1
-0@@ -506,6 +506,31 @@ static const struct cpufreq_driver __initconstrel hwp_cpufreq_driver = .update = hwp_cpufreq_update, }; +int get_hwp_para(const struct cpufreq_policy *policy,
While I don't really mind a policy being passed into here, ...
xen/arch/x86/acpi/cpufreq/hwp.c static const struct cpufreq_driver __initconstrel hwp_cpufreq_driver = · line 512
Quoted 3 lines
xen/arch/x86/acpi/cpufreq/hwp.c +3
-0+ struct xen_hwp_para *hwp_para) +{ +unsigned int cpu = policy->cpu;
... this is its only use afaics, and hence the caller could as well pass in just a CPU number?
Quoted 19 lines
xen/include/public/sysctl.h +13
-0@@ -292,6 +292,31 @@ struct xen_ondemand {uint32_t up_threshold; }; +struct xen_hwp_para { +/* +* bits 6:0 - 7bit mantissa +* bits 9:7 - 3bit base-10 exponent +* btis 15:10 - Unused - must be 0 +*/ +#define HWP_ACT_WINDOW_MANTISSA_MASK 0x7f +#define HWP_ACT_WINDOW_EXPONENT_MASK 0x7 +#define HWP_ACT_WINDOW_EXPONENT_SHIFT 7 +uint16_t activity_window; +/* energy_perf range 0-255 if 1. Otherwise 0-15 */ +#define XEN_SYSCTL_HWP_FEAT_ENERGY_PERF (1 << 0) +/* activity_window supported if 1 */
xen/include/public/sysctl.h struct xen_ondemand { · line 317
Quoted 10 lines
xen/include/public/sysctl.h +10
-0+#define XEN_SYSCTL_HWP_FEAT_ACT_WINDOW (1 << 1) +uint8_t features;/* bit flags for features */ +uint8_t lowest; +uint8_t most_efficient; +uint8_t guaranteed; +uint8_t highest; +uint8_t minimum; +uint8_t maximum; +uint8_t desired; +uint8_t energy_perf;
These fields could do with some more commentary. To be honest I had trouble figuring (from the SDM) what exact meaning specific numeric values have. Readers of this header should at the very least be told where they can turn to in order to understand what these fields communicate. (FTAOD this could be section names, but please not section numbers. The latter are fine to use in a discussion, but they're changing too frequently to make them useful in code comments.)
xen/include/public/sysctl.h struct xen_ondemand { · line 318
Quoted 1 line
xen/include/public/sysctl.h +1
-0+};
Also, if you decide to stick to uint8_t, then the trailing padding field (another uint8_t) wants making explicit. I'm on the edge whether to ask to also check the field: Right here the struct is "get only", and peeking ahead you look to be introducing a separate sub-op for "set". Perhaps if you added /* OUT */ at the top of the new struct? (But if you don't check the field for being zero, then you'll want to set it to zero for forward compatibility.)
Jan
Re: [PATCH v3 07/14 RESEND] cpufreq: Export HWP parameters to userspace
Quoted 12 lines · Jan Beulich
Quoted 10 lines · Jason Andryuk
Extend
xen_get_cpufreq_parato return hwp parameters. These match the hardware rather closely.We need the features bitmask to indicated fields supported by the actual hardware.
The use of
uint8_tparameters matches the hardware size.uint32_tentries grows thesysctl_tpast the build assertion insetup.c. Theuint8_tranges are supported across multiple generations, so hopefully they won't change.
Quoted 6 lines
Still it feels a little odd for values to be this narrow. Aiui the scaling_governor[] and scaling_{max,min}_freq fields aren't (really) used by HWP. So you could widen the union in struct
xen_get_cpufreq_para(in a binary but not necessarily source compatible manner), gaining you 6 moreuint32_tslots. Possibly the somewhat oddly placedscaling_cur_freqcould be included as well ...
Having seen patch 9 now as well, I wonder whether here (or in a separate patch) you don't want to limit providing inapplicable data (for example not filling *scaling_available_governors would even avoid an allocation, thus removing a possible reason for failure), while there (or again in a separate patch) you'd also limit what the tool reports (inapplicable output causes confusion / questions at best).
Jan
Re: [PATCH v3 07/14 RESEND] cpufreq: Export HWP parameters to userspace
Quoted 13 lines · Jan Beulich
Quoted 10 lines · Jason Andryuk
Extend
xen_get_cpufreq_parato return hwp parameters. These match the hardware rather closely.We need the features bitmask to indicated fields supported by the actual hardware.
The use of
uint8_tparameters matches the hardware size.uint32_tentries grows thesysctl_tpast the build assertion insetup.c. Theuint8_tranges are supported across multiple generations, so hopefully they won't change.
Quoted 6 lines
Still it feels a little odd for values to be this narrow. Aiui the scaling_governor[] and scaling_{max,min}_freq fields aren't (really) used by HWP. So you could widen the union in struct
xen_get_cpufreq_para(in a binary but not necessarily source compatible manner), gaining you 6 moreuint32_tslots. Possibly the somewhat oddly placedscaling_cur_freqcould be included as well ...
The values are narrow, but they match the hardware. It works for HWP, so there is no need to change at this time AFAICT.
Do you want me to make this change?
Quoted 10 lines
xen/arch/x86/acpi/cpufreq/hwp.c static const struct cpufreq_driver __initconstrel hwp_cpufreq_driver = · line 509
Quoted 7 lines
xen/arch/x86/acpi/cpufreq/hwp.c +1
-0@@ -506,6 +506,31 @@ static const struct cpufreq_driver __initconstrel hwp_cpufreq_driver = .update = hwp_cpufreq_update, }; +int get_hwp_para(const struct cpufreq_policy *policy,While I don't really mind a policy being passed into here, ...
Quoted 6 lines
xen/arch/x86/acpi/cpufreq/hwp.c static const struct cpufreq_driver __initconstrel hwp_cpufreq_driver = · line 512
Quoted 3 lines
xen/arch/x86/acpi/cpufreq/hwp.c +3
-0+ struct xen_hwp_para *hwp_para) +{ +unsigned int cpu = policy->cpu;... this is its only use afaics, and hence the caller could as well pass in just a CPU number?
Sounds good.
Quoted 30 lines
Quoted 19 lines
xen/include/public/sysctl.h +13
-0@@ -292,6 +292,31 @@ struct xen_ondemand {uint32_t up_threshold; }; +struct xen_hwp_para { +/* +* bits 6:0 - 7bit mantissa +* bits 9:7 - 3bit base-10 exponent +* btis 15:10 - Unused - must be 0 +*/ +#define HWP_ACT_WINDOW_MANTISSA_MASK 0x7f +#define HWP_ACT_WINDOW_EXPONENT_MASK 0x7 +#define HWP_ACT_WINDOW_EXPONENT_SHIFT 7 +uint16_t activity_window; +/* energy_perf range 0-255 if 1. Otherwise 0-15 */ +#define XEN_SYSCTL_HWP_FEAT_ENERGY_PERF (1 << 0) +/* activity_window supported if 1 */ xen/include/public/sysctl.h struct xen_ondemand { · line 317
Quoted 10 lines
xen/include/public/sysctl.h +10
-0+#define XEN_SYSCTL_HWP_FEAT_ACT_WINDOW (1 << 1) +uint8_t features;/* bit flags for features */ +uint8_t lowest; +uint8_t most_efficient; +uint8_t guaranteed; +uint8_t highest; +uint8_t minimum; +uint8_t maximum; +uint8_t desired; +uint8_t energy_perf;
Quoted 8 lines
These fields could do with some more commentary. To be honest I had trouble figuring (from the SDM) what exact meaning specific numeric values have. Readers of this header should at the very least be told where they can turn to in order to understand what these fields communicate. (FTAOD this could be section names, but please not section numbers. The latter are fine to use in a discussion, but they're changing too frequently to make them useful in code comments.)
Sounds good. I'll add some description.
Quoted 9 lines
xen/include/public/sysctl.h struct xen_ondemand { · line 318
Quoted 1 line
xen/include/public/sysctl.h +1
-0+};Also, if you decide to stick to
uint8_t, then the trailing padding field (anotheruint8_t) wants making explicit. I'm on the edge whether to ask to also check the field: Right here the struct is "get only", and peeking ahead you look to be introducing a separate sub-op for "set". Perhaps if you added /* OUT */ at the top of the new struct? (But if you don't check the field for being zero, then you'll want to set it to zero for forward compatibility.)
Thanks for catching. I'll add the padding field and zero it.
Quoted 21 lines · Jan Beulich
Quoted 12 lines · Jan Beulich
Quoted 10 lines · Jason Andryuk
Extend
xen_get_cpufreq_parato return hwp parameters. These match the hardware rather closely.We need the features bitmask to indicated fields supported by the actual hardware.
The use of
uint8_tparameters matches the hardware size.uint32_tentries grows thesysctl_tpast the build assertion insetup.c. Theuint8_tranges are supported across multiple generations, so hopefully they won't change.Quoted 6 lines
Still it feels a little odd for values to be this narrow. Aiui the scaling_governor[] and scaling_{max,min}_freq fields aren't (really) used by HWP. So you could widen the union in struct
xen_get_cpufreq_para(in a binary but not necessarily source compatible manner), gaining you 6 moreuint32_tslots. Possibly the somewhat oddly placedscaling_cur_freqcould be included as well ...
Quoted 6 lines
Having seen patch 9 now as well, I wonder whether here (or in a separate patch) you don't want to limit providing inapplicable data (for example not filling
*scaling_available_governorswould even avoid an allocation, thus removing a possible reason for failure), while there (or again in a separate patch) you'd also limit what the tool reports (inapplicable output causes confusion / questions at best).
The xenpm output only shows relevant information:
# xenpm get-cpufreq-para 11
cpu id : 11
affected_cpus : 11
cpuinfo frequency : base [1600000] max [4900000]
scaling_driver : hwp-cpufreq
scaling_avail_gov : hwp
current_governor : hwp
hwp variables :
hardware limits : lowest [1] most_efficient [11]
: guaranteed [11] highest [49]
configured limits : min [1] max [255] energy_perf [128]
: activity_window [0 hardware selected]
: desired [0 hw autonomous]
turbo mode : enabledThe scaling_*_freq values, policy->{min,max,cur} are filled in with base, max and 0 in hwp_get_cpu_speeds(), so it's not totally invalid values being returned. The governor registration restricting to only internal governors when HWP is active means it only has the single governor. I think it's okay as-is, but let me know if you want something changed.
Regards,
Jason
Re: [PATCH v3 07/14 RESEND] cpufreq: Export HWP parameters to userspace
Quoted 21 lines · Jason Andryuk
Quoted 13 lines · Jan Beulich
Quoted 10 lines · Jason Andryuk
Extend
xen_get_cpufreq_parato return hwp parameters. These match the hardware rather closely.We need the features bitmask to indicated fields supported by the actual hardware.
The use of
uint8_tparameters matches the hardware size.uint32_tentries grows thesysctl_tpast the build assertion insetup.c. Theuint8_tranges are supported across multiple generations, so hopefully they won't change.Quoted 6 lines
Still it feels a little odd for values to be this narrow. Aiui the scaling_governor[] and scaling_{max,min}_freq fields aren't (really) used by HWP. So you could widen the union in struct
xen_get_cpufreq_para(in a binary but not necessarily source compatible manner), gaining you 6 moreuint32_tslots. Possibly the somewhat oddly placedscaling_cur_freqcould be included as well ...
Quoted 4 lines
The values are narrow, but they match the hardware. It works for HWP, so there is no need to change at this time AFAICT.
Do you want me to make this change?
Well, much depends on what these 8-bit values actually express (I did raise this question in one of the replies to your patches, as I wasn't able to find anything in the SDM). That'll then hopefully allow to make some educated prediction on on how likely it is that a future variant of hwp would want to widen them. (Was it energy_perf that went from 4 to 8 bits at some point, which you even comment upon in the public header?)
Quoted 45 lines · Jan Beulich
Quoted 20 lines · Jan Beulich
Quoted 12 lines · Jason Andryuk
Quoted 10 lines
Extend
xen_get_cpufreq_parato return hwp parameters. These match the hardware rather closely.We need the features bitmask to indicated fields supported by the actual hardware.
The use of
uint8_tparameters matches the hardware size.uint32_tentries grows thesysctl_tpast the build assertion insetup.c. Theuint8_tranges are supported across multiple generations, so hopefully they won't change.Quoted 6 lines
Still it feels a little odd for values to be this narrow. Aiui the scaling_governor[] and scaling_{max,min}_freq fields aren't (really) used by HWP. So you could widen the union in struct
xen_get_cpufreq_para(in a binary but not necessarily source compatible manner), gaining you 6 moreuint32_tslots. Possibly the somewhat oddly placedscaling_cur_freqcould be included as well ...Quoted 6 lines
Having seen patch 9 now as well, I wonder whether here (or in a separate patch) you don't want to limit providing inapplicable data (for example not filling
*scaling_available_governorswould even avoid an allocation, thus removing a possible reason for failure), while there (or again in a separate patch) you'd also limit what the tool reports (inapplicable output causes confusion / questions at best).The xenpm output only shows relevant information:
# xenpm get-cpufreq-para 11 cpu id : 11 affected_cpus : 11 cpuinfo frequency : base [1600000] max [4900000] scaling_driver : hwp-cpufreq scaling_avail_gov : hwp current_governor : hwp hwp variables : hardware limits : lowest [1] most_efficient [11] : guaranteed [11] highest [49] configured limits : min [1] max [255] energy_perf [128] : activity_window [0 hardware selected] : desired [0 hw autonomous] turbo mode : enabled
Quoted 6 lines
The scaling_*_freq values, policy->{min,max,cur} are filled in with base, max and 0 in
hwp_get_cpu_speeds(), so it's not totally invalid values being returned. The governor registration restricting to only internal governors when HWP is active means it only has the single governor. I think it's okay as-is, but let me know if you want something changed.
Well, the main connection here was to the possible overloading of space in the sysctl struct, by widening what the union covers. That can of course only be done for fields which don't convey useful data. If we go without the further overloading, I guess we can for now leave the tool as you have it, and deal with possible tidying later on.
Jan
Re: [PATCH v3 07/14 RESEND] cpufreq: Export HWP parameters to userspace
Quoted 26 lines · Jan Beulich
Quoted 24 lines · Jason Andryuk
Quoted 13 lines · Jan Beulich
Quoted 10 lines · Jason Andryuk
Extend
xen_get_cpufreq_parato return hwp parameters. These match the hardware rather closely.We need the features bitmask to indicated fields supported by the actual hardware.
The use of
uint8_tparameters matches the hardware size.uint32_tentries grows thesysctl_tpast the build assertion insetup.c. Theuint8_tranges are supported across multiple generations, so hopefully they won't change.Quoted 6 lines
Still it feels a little odd for values to be this narrow. Aiui the scaling_governor[] and scaling_{max,min}_freq fields aren't (really) used by HWP. So you could widen the union in struct
xen_get_cpufreq_para(in a binary but not necessarily source compatible manner), gaining you 6 moreuint32_tslots. Possibly the somewhat oddly placedscaling_cur_freqcould be included as well ...The values are narrow, but they match the hardware. It works for HWP, so there is no need to change at this time AFAICT.
Quoted 7 lines
Quoted 1 line
Do you want me to make this change?
Well, much depends on what these 8-bit values actually express (I did raise this question in one of the replies to your patches, as I wasn't able to find anything in the SDM). That'll then hopefully allow to make some educated prediction on on how likely it is that a future variant of hwp would want to widen them.
Sorry for not providing a reference earlier. In the SDM, HARDWARE-CONTROLLED PERFORMANCE STATES (HWP) section, there is this second paragraph:
"""
In contrast, HWP is an implementation of the ACPI-defined Collaborative Processor Performance Control (CPPC), which specifies that the platform enumerates a continuous, abstract unit-less, performance value scale that is not tied to a specific performance state / frequency by definition. While the enumerated scale is roughly linear in terms of a delivered integer workload performance result, the OS is required to characterize the performance value range to comprehend the delivered performance for an applied workload. """
The numbers are "continuous, abstract unit-less, performance value." So there isn't much to go on there, but generally, smaller numbers mean slower and bigger numbers mean faster.
Cross referencing the ACPI spec here:
https://uefi.org/specs/ACPI/6.5/08_Processor_Configuration_and_Control.html#collaborative-processor-performance-control
Scrolling down you can find the register entries such as
Highest Performance
Register or DWORD Attribute: Read Size: 8-32 bits
AMD has its own pstate implementation that is similar to HWP. Looking at the Linux support, the AMD hardware also use 8 bit values for the comparable fields:
https://elixir.bootlin.com/linux/latest/source/arch/x86/include/asm/msr-index.h#L612
So Intel and AMD are 8bit for now at least. Something could do 32bits according to the ACPI spec.
8 bits of granularity for slow to fast seems like plenty to me. I'm not sure what one would gain from 16 or 32 bits, but I'm not designing the hardware. From the earlier xenpm output, "highest" was 49, so still a decent amount of room in an 8 bit range.
Quoted 3 lines
(Was it
energy_perfthat went
from 4 to 8 bits at some point, which you even comment upon in the public header?)
energy_perf (Energy_Performanc_Preference) had a fallback: "If CPUID.06H:EAX[bit 10] indicates that this field is not supported, HWP uses the value of the IA32_ENERGY_PERF_BIAS MSR to determine the energy efficiency / performance preference." So it had a different range, but that was because it was being put into an older register.
However, I've removed that fallback code in v4.
Regards,
Jason
Re: [PATCH v3 07/14 RESEND] cpufreq: Export HWP parameters to userspace
Quoted 67 lines · Jason Andryuk
Quoted 26 lines · Jan Beulich
Quoted 24 lines · Jason Andryuk
Quoted 13 lines · Jan Beulich
Quoted 10 lines · Jason Andryuk
Extend
xen_get_cpufreq_parato return hwp parameters. These match the hardware rather closely.We need the features bitmask to indicated fields supported by the actual hardware.
The use of
uint8_tparameters matches the hardware size.uint32_tentries grows thesysctl_tpast the build assertion insetup.c. Theuint8_tranges are supported across multiple generations, so hopefully they won't change.Quoted 6 lines
Still it feels a little odd for values to be this narrow. Aiui the scaling_governor[] and scaling_{max,min}_freq fields aren't (really) used by HWP. So you could widen the union in struct
xen_get_cpufreq_para(in a binary but not necessarily source compatible manner), gaining you 6 moreuint32_tslots. Possibly the somewhat oddly placedscaling_cur_freqcould be included as well ...The values are narrow, but they match the hardware. It works for HWP, so there is no need to change at this time AFAICT.
Quoted 7 lines
Quoted 1 line
Do you want me to make this change?
Well, much depends on what these 8-bit values actually express (I did raise this question in one of the replies to your patches, as I wasn't able to find anything in the SDM). That'll then hopefully allow to make some educated prediction on on how likely it is that a future variant of hwp would want to widen them.
Sorry for not providing a reference earlier. In the SDM, HARDWARE-CONTROLLED PERFORMANCE STATES (HWP) section, there is this second paragraph:
"""
In contrast, HWP is an implementation of the ACPI-defined Collaborative Processor Performance Control (CPPC), which specifies that the platform enumerates a continuous, abstract unit-less, performance value scale that is not tied to a specific performance state / frequency by definition. While the enumerated scale is roughly linear in terms of a delivered integer workload performance result, the OS is required to characterize the performance value range to comprehend the delivered performance for an applied workload. """The numbers are "continuous, abstract unit-less, performance value." So there isn't much to go on there, but generally, smaller numbers mean slower and bigger numbers mean faster.
Cross referencing the ACPI spec here:
https://uefi.org/specs/ACPI/6.5/08_Processor_Configuration_and_Control.html#collaborative-processor-performance-controlScrolling down you can find the register entries such as
Highest Performance
Register or DWORD Attribute: Read Size: 8-32 bitsAMD has its own pstate implementation that is similar to HWP. Looking at the Linux support, the AMD hardware also use 8 bit values for the comparable fields:
https://elixir.bootlin.com/linux/latest/source/arch/x86/include/asm/msr-index.h#L612
Quoted 7 lines
So Intel and AMD are 8bit for now at least. Something could do 32bits according to the ACPI spec.
8 bits of granularity for slow to fast seems like plenty to me. I'm not sure what one would gain from 16 or 32 bits, but I'm not designing the hardware. From the earlier xenpm output, "highest" was 49, so still a decent amount of room in an 8 bit range.
Hmm, thanks for the pointers. I'm still somewhat undecided. I guess I'm okay with you keeping things as you have them. If and when needed we can still rework the structure - it is possible to change it as it's (for the time being at least) still an unstable interface.
Jan
Re: [PATCH v3 07/14 RESEND] cpufreq: Export HWP parameters to userspace
Quoted 77 lines · Jan Beulich
Quoted 67 lines · Jason Andryuk
Quoted 26 lines · Jan Beulich
Quoted 24 lines · Jason Andryuk
Quoted 13 lines · Jan Beulich
Quoted 10 lines · Jason Andryuk
Extend
xen_get_cpufreq_parato return hwp parameters. These match the hardware rather closely.We need the features bitmask to indicated fields supported by the actual hardware.
The use of
uint8_tparameters matches the hardware size.uint32_tentries grows thesysctl_tpast the build assertion insetup.c. Theuint8_tranges are supported across multiple generations, so hopefully they won't change.Quoted 6 lines
Still it feels a little odd for values to be this narrow. Aiui the scaling_governor[] and scaling_{max,min}_freq fields aren't (really) used by HWP. So you could widen the union in struct
xen_get_cpufreq_para(in a binary but not necessarily source compatible manner), gaining you 6 moreuint32_tslots. Possibly the somewhat oddly placedscaling_cur_freqcould be included as well ...The values are narrow, but they match the hardware. It works for HWP, so there is no need to change at this time AFAICT.
Quoted 7 lines
Quoted 1 line
Do you want me to make this change?
Well, much depends on what these 8-bit values actually express (I did raise this question in one of the replies to your patches, as I wasn't able to find anything in the SDM). That'll then hopefully allow to make some educated prediction on on how likely it is that a future variant of hwp would want to widen them.
Sorry for not providing a reference earlier. In the SDM, HARDWARE-CONTROLLED PERFORMANCE STATES (HWP) section, there is this second paragraph:
"""
In contrast, HWP is an implementation of the ACPI-defined Collaborative Processor Performance Control (CPPC), which specifies that the platform enumerates a continuous, abstract unit-less, performance value scale that is not tied to a specific performance state / frequency by definition. While the enumerated scale is roughly linear in terms of a delivered integer workload performance result, the OS is required to characterize the performance value range to comprehend the delivered performance for an applied workload. """The numbers are "continuous, abstract unit-less, performance value." So there isn't much to go on there, but generally, smaller numbers mean slower and bigger numbers mean faster.
Cross referencing the ACPI spec here:
https://uefi.org/specs/ACPI/6.5/08_Processor_Configuration_and_Control.html#collaborative-processor-performance-controlScrolling down you can find the register entries such as
Highest Performance
Register or DWORD Attribute: Read Size: 8-32 bitsAMD has its own pstate implementation that is similar to HWP. Looking at the Linux support, the AMD hardware also use 8 bit values for the comparable fields:
https://elixir.bootlin.com/linux/latest/source/arch/x86/include/asm/msr-index.h#L612Quoted 7 lines
So Intel and AMD are 8bit for now at least. Something could do 32bits according to the ACPI spec.
8 bits of granularity for slow to fast seems like plenty to me. I'm not sure what one would gain from 16 or 32 bits, but I'm not designing the hardware. From the earlier xenpm output, "highest" was 49, so still a decent amount of room in an 8 bit range.
Quoted 4 lines
Hmm, thanks for the pointers. I'm still somewhat undecided. I guess I'm okay with you keeping things as you have them. If and when needed we can still rework the structure - it is possible to change it as it's (for the time being at least) still an unstable interface.
With an anonymous union and anonymous struct, struct xen_get_cpufreq_para can be re-arranged and compile without any changes to other cpufreq code. struct xen_hwp_para becomes 10 uint32_t's. The old scaling is 3 * uint32_t + 16 bytes CPUFREQ_NAME_LEN + 4 * uint32_t for xen_ondemand = 11 uint32_t. So int32_t turbo_enabled doesn't move and it's binary compatible.
Anonymous unions and structs aren't allowed in the public header though, right? So that would need to change, though it doesn't seem too bad. There isn't too much churn.
I have no plans to tackle AMD pstate. But having glanced at it this morning, maybe these hwp sysctls should be renamed cppc? AMD pstate and HWP are both implementations of CPPC, so that could be more future proof? But, again, I only glanced at the AMD stuff, so there may be other changes needed.
Regards,
Jason
Re: [PATCH v3 07/14 RESEND] cpufreq: Export HWP parameters to userspace
Quoted 90 lines · Jason Andryuk
Quoted 77 lines · Jan Beulich
Quoted 67 lines · Jason Andryuk
Quoted 26 lines · Jan Beulich
Quoted 24 lines · Jason Andryuk
Quoted 13 lines · Jan Beulich
Quoted 10 lines · Jason Andryuk
Extend
xen_get_cpufreq_parato return hwp parameters. These match the hardware rather closely.We need the features bitmask to indicated fields supported by the actual hardware.
The use of
uint8_tparameters matches the hardware size.uint32_tentries grows thesysctl_tpast the build assertion insetup.c. Theuint8_tranges are supported across multiple generations, so hopefully they won't change.Quoted 6 lines
Still it feels a little odd for values to be this narrow. Aiui the scaling_governor[] and scaling_{max,min}_freq fields aren't (really) used by HWP. So you could widen the union in struct
xen_get_cpufreq_para(in a binary but not necessarily source compatible manner), gaining you 6 moreuint32_tslots. Possibly the somewhat oddly placedscaling_cur_freqcould be included as well ...The values are narrow, but they match the hardware. It works for HWP, so there is no need to change at this time AFAICT.
Quoted 7 lines
Quoted 1 line
Do you want me to make this change?
Well, much depends on what these 8-bit values actually express (I did raise this question in one of the replies to your patches, as I wasn't able to find anything in the SDM). That'll then hopefully allow to make some educated prediction on on how likely it is that a future variant of hwp would want to widen them.
Sorry for not providing a reference earlier. In the SDM, HARDWARE-CONTROLLED PERFORMANCE STATES (HWP) section, there is this second paragraph:
"""
In contrast, HWP is an implementation of the ACPI-defined Collaborative Processor Performance Control (CPPC), which specifies that the platform enumerates a continuous, abstract unit-less, performance value scale that is not tied to a specific performance state / frequency by definition. While the enumerated scale is roughly linear in terms of a delivered integer workload performance result, the OS is required to characterize the performance value range to comprehend the delivered performance for an applied workload. """The numbers are "continuous, abstract unit-less, performance value." So there isn't much to go on there, but generally, smaller numbers mean slower and bigger numbers mean faster.
Cross referencing the ACPI spec here:
https://uefi.org/specs/ACPI/6.5/08_Processor_Configuration_and_Control.html#collaborative-processor-performance-controlScrolling down you can find the register entries such as
Highest Performance
Register or DWORD Attribute: Read Size: 8-32 bitsAMD has its own pstate implementation that is similar to HWP. Looking at the Linux support, the AMD hardware also use 8 bit values for the comparable fields:
https://elixir.bootlin.com/linux/latest/source/arch/x86/include/asm/msr-index.h#L612Quoted 7 lines
So Intel and AMD are 8bit for now at least. Something could do 32bits according to the ACPI spec.
8 bits of granularity for slow to fast seems like plenty to me. I'm not sure what one would gain from 16 or 32 bits, but I'm not designing the hardware. From the earlier xenpm output, "highest" was 49, so still a decent amount of room in an 8 bit range.
Quoted 4 lines
Hmm, thanks for the pointers. I'm still somewhat undecided. I guess I'm okay with you keeping things as you have them. If and when needed we can still rework the structure - it is possible to change it as it's (for the time being at least) still an unstable interface.
With an anonymous union and anonymous struct, struct
xen_get_cpufreq_paracan be re-arranged and compile without any changes to other cpufreq code. structxen_hwp_parabecomes 10 uint32_t's. The old scaling is 3 *uint32_t+ 16 bytesCPUFREQ_NAME_LEN+ 4 *uint32_tforxen_ondemand= 11uint32_t. Soint32_tturbo_enableddoesn't move and it's binary compatible.
Quoted 2 lines
Anonymous unions and structs aren't allowed in the public header though, right?
Correct.
Quoted 8 lines
So that would need to change, though it doesn't seem
too bad. There isn't too much churn.I have no plans to tackle AMD pstate. But having glanced at it this morning, maybe these hwp sysctls should be renamed cppc? AMD pstate and HWP are both implementations of CPPC, so that could be more future proof? But, again, I only glanced at the AMD stuff, so there may be other changes needed.
I consider this naming change plan plausible. If further adjustments end up necessary for AMD, that'll be no worse (but maybe better) than if we have to go from HWP to a more general name altogether.
Jan
PATCH RESEND v3 8/14 libxc: Include hwp_para in definitions
In reply to Jason AndryukExpose the hwp_para fields through libxc.
--- tools/include/xenctrl.h | 2 ++ 1 file changed, 2 insertions(+)
tools/include/xenctrl.h +2 -0
@@ -1903,6 +1903,7 @@ int xc_smt_disable(xc_interface *xch);*/ typedef struct xen_userspace xc_userspace_t ;typedef struct xen_ondemand xc_ondemand_t ; +typedef struct xen_hwp_para xc_hwp_para_t ;struct xc_get_cpufreq_para {/* IN/OUT variable */
@@ -1930,6 +1931,7 @@ struct xc_get_cpufreq_para {union {xc_userspace_t userspace;xc_ondemand_t ondemand; +xc_hwp_para_t hwp_para; } u;int32_t turbo_enabled;
Signature · 1 line
2.40.0
Re: [PATCH v3 08/14 RESEND] libxc: Include hwp_para in definitions
Quoted 3 lines · Jason Andryuk
Expose the
hwp_parafields through libxc.Signed-off-by Jason Andryuk <[email protected]>
Thanks,
Signature · 1 line
Anthony PERARD
PATCH RESEND v3 9/14 xenpm: Print HWP parameters
In reply to Jason AndryukPrint HWP-specific parameters. Some are always present, but others depend on hardware support.
---
v2:
Style fixes
Declare i outside loop
Replace repearted hardware/configured limits with spaces Fixup for hw_ removal
Use XEN_HWP_GOVERNOR
Use HWP_ACT_WINDOW_EXPONENT_*
Remove energy_perf hw autonomous - 0 doesn't mean autonomous
--- tools/misc/xenpm.c | 65 ++++++++++++++++++++++++++++++++++++++++++++++ 1 file changed, 65 insertions(+)
tools/misc/xenpm.c +65 -0
@@ -708,6 +708,44 @@ void start_gather_func(int argc, char *argv[])pause (); } +static void calculate_hwp_activity_window (const xc_hwp_para_t *hwp, +unsigned int *activity_window, +const char **units) +{ +unsigned int mantissa = hwp->activity_window &HWP_ACT_WINDOW_MANTISSA_MASK ; +unsigned int exponent = + (hwp->activity_window >>HWP_ACT_WINDOW_EXPONENT_SHIFT ) & +HWP_ACT_WINDOW_EXPONENT_MASK ; +unsigned int multiplier =1 ; +unsigned int i; + +if ( hwp->activity_window ==0 ) + { + *units ="hardware selected" ; + *activity_window =0 ; + +return ; + } + +if ( exponent >=6 ) + { + *units ="s" ; + exponent -=6 ; + } +else if ( exponent >=3 ) + { + *units ="ms" ; + exponent -=3 ; + } +else + *units ="us" ; + +for ( i =0 ; i < exponent; i++ ) + multiplier *=10 ; + + *activity_window = mantissa * multiplier; +} +/* print out parameters about cpu frequency */ static void print_cpufreq_para (int cpuid,struct xc_get_cpufreq_para *p_cpufreq) {
@@ -773,6 +811,33 @@ static void print_cpufreq_para(int cpuid, struct xc_get_cpufreq_para *p_cpufreq) p_cpufreq->scaling_cur_freq); } +if (strcmp (p_cpufreq->scaling_governor,XEN_HWP_GOVERNOR ) ==0 ) + { +const xc_hwp_para_t *hwp = &p_cpufreq->u.hwp_para; + +printf ("hwp variables :\n" ); +printf (" hardware limits : lowest [%u] most_efficient [%u]\n" , + hwp->lowest, hwp->most_efficient); +printf (" : guaranteed [%u] highest [%u]\n" , + hwp->guaranteed, hwp->highest); +printf (" configured limits : min [%u] max [%u] energy_perf [%u]\n" , + hwp->minimum, hwp->maximum, hwp->energy_perf); + +if ( hwp->features &XEN_SYSCTL_HWP_FEAT_ACT_WINDOW ) + { +unsigned int activity_window; +const char *units; + +calculate_hwp_activity_window (hwp, &activity_window, &units); +printf (" : activity_window [%u %s]\n" , + activity_window, units); + } + +printf (" : desired [%u%s]\n" , + hwp->desired, + hwp->desired ?"" :" hw autonomous" ); + } +printf ("turbo mode : %s\n" , p_cpufreq->turbo_enabled ?"enabled" :"disabled or n/a" );printf ("\n" );
Signature · 1 line
2.40.0
Re: [PATCH v3 09/14 RESEND] xenpm: Print HWP parameters
Quoted 22 lines · Jason Andryuk
Print HWP-specific parameters. Some are always present, but others depend on hardware support.
Signed-off-by Jason Andryuk <[email protected]>---
v2:
Style fixes
Declare i outside loop
Replace repearted hardware/configured limits with spaces Fixup forhw_removal
UseXEN_HWP_GOVERNOR
Use HWP_ACT_WINDOW_EXPONENT_*
Removeenergy_perfhw autonomous - 0 doesn't mean autonomous--- tools/misc/xenpm.c | 65 ++++++++++++++++++++++++++++++++++++++++++++++ 1 file changed, 65 insertions(+)tools/misc/xenpm.c +0
-0
tools/misc/xenpm.c void start_gather_func(int argc, char *argv[]) · line 713
Quoted 6 lines
tools/misc/xenpm.c +3
-0@@ -708,6 +708,44 @@ void start_gather_func(int argc, char *argv[])pause (); } +static void calculate_hwp_activity_window (const xc_hwp_para_t *hwp, +unsigned int *activity_window, +const char **units)
The function's return value would be nice to use for one of the two values that are being returned.
tools/misc/xenpm.c void start_gather_func(int argc, char *argv[]) · line 718
Quoted 5 lines
tools/misc/xenpm.c +5
-0+{ +unsigned int mantissa = hwp->activity_window &HWP_ACT_WINDOW_MANTISSA_MASK ; +unsigned int exponent = + (hwp->activity_window >>HWP_ACT_WINDOW_EXPONENT_SHIFT ) & +HWP_ACT_WINDOW_EXPONENT_MASK ;
I wish we had MASK_EXTR() in common-macros.h. While really a comment on patch 7 - HWP_ACT_WINDOW_EXPONENT_SHIFT is redundant information and should imo be omitted from the public interface, in favor of just a (suitably shifted) mask value. Also note how those constants all lack proper XEN_ prefixes.
tools/misc/xenpm.c void start_gather_func(int argc, char *argv[]) · line 728
Quoted 10 lines
tools/misc/xenpm.c +10
-0+unsigned int multiplier =1 ; +unsigned int i; + +if ( hwp->activity_window ==0 ) + { + *units ="hardware selected" ; + *activity_window =0 ; + +return ; + }
While in line with documentation, any mantissa of 0 results in a 0us window, which I assume would then also mean "hardware selected".
tools/misc/xenpm.c static void print_cpufreq_para(int cpuid, struct xc_get_cpufreq_para *p_cpufreq) · line 819
Quoted 10 lines
tools/misc/xenpm.c +6
-0@@ -773,6 +811,33 @@ static void print_cpufreq_para(int cpuid, struct xc_get_cpufreq_para *p_cpufreq) p_cpufreq->scaling_cur_freq); } +if (strcmp (p_cpufreq->scaling_governor,XEN_HWP_GOVERNOR ) ==0 ) + { +const xc_hwp_para_t *hwp = &p_cpufreq->u.hwp_para; + +printf ("hwp variables :\n" ); + printf(" hardware limits : lowest [%u] most_efficient [%u]\n",
Here and ...
tools/misc/xenpm.c static void print_cpufreq_para(int cpuid, struct xc_get_cpufreq_para *p_cpufreq) · line 823
Quoted 4 lines
tools/misc/xenpm.c +4
-0+ hwp->lowest, hwp->most_efficient); +printf (" : guaranteed [%u] highest [%u]\n" , + hwp->guaranteed, hwp->highest); + printf(" configured limits : min [%u] max [%u] energy_perf [%u]\n",
... here I wonder what use the underscores are in produced output. I'd use blanks. If you really want a separator there, then please use dashes.
Jan
Re: [PATCH v3 09/14 RESEND] xenpm: Print HWP parameters
Quoted 27 lines · Jan Beulich
Quoted 25 lines · Jason Andryuk
Print HWP-specific parameters. Some are always present, but others depend on hardware support.
Signed-off-by Jason Andryuk <[email protected]>---
v2:
Style fixes
Declare i outside loop
Replace repearted hardware/configured limits with spaces Fixup forhw_removal
UseXEN_HWP_GOVERNOR
Use HWP_ACT_WINDOW_EXPONENT_*
Removeenergy_perfhw autonomous - 0 doesn't mean autonomous--- tools/misc/xenpm.c | 65 ++++++++++++++++++++++++++++++++++++++++++++++ 1 file changed, 65 insertions(+)tools/misc/xenpm.c +0
-0@@ -708,6 +708,44 @@ void start_gather_func(int argc, char *argv[])pause (); }
Quoted 6 lines
tools/misc/xenpm.c void start_gather_func(int argc, char *argv[]) · line 713
Quoted 3 lines
tools/misc/xenpm.c +3
-0+static void calculate_hwp_activity_window (const xc_hwp_para_t *hwp, +unsigned int *activity_window, +const char **units)The function's return value would be nice to use for one of the two values that are being returned.
Ok, I'll return activity_window.
Quoted 11 lines
tools/misc/xenpm.c void start_gather_func(int argc, char *argv[]) · line 718
Quoted 5 lines
tools/misc/xenpm.c +5
-0+{ +unsigned int mantissa = hwp->activity_window &HWP_ACT_WINDOW_MANTISSA_MASK ; +unsigned int exponent = + (hwp->activity_window >>HWP_ACT_WINDOW_EXPONENT_SHIFT ) & +HWP_ACT_WINDOW_EXPONENT_MASK ;I wish we had
MASK_EXTR()incommon-macros.h. While really a comment on patch 7 -HWP_ACT_WINDOW_EXPONENT_SHIFTis redundant information and should imo be omitted from the public interface, in favor of just a (suitably shifted) mask value. Also note how those constants all lack properXEN_prefixes.
I'll add a patch adding MASK_EXTR() & MASK_INSR() to common-macros.h and use those - is there any reason not to do that?
I'll also add XEN_ prefixes.
Quoted 5 lines
Quoted 5 lines
tools/misc/xenpm.c +5
-0+unsigned int multiplier =1 ; +unsigned int i; + +if ( hwp->activity_window ==0 ) + {
Quoted 8 lines
tools/misc/xenpm.c void start_gather_func(int argc, char *argv[]) · line 728
Quoted 5 lines
tools/misc/xenpm.c +5
-0+ *units ="hardware selected" ; + *activity_window =0 ; + +return ; + }While in line with documentation, any mantissa of 0 results in a 0us window, which I assume would then also mean "hardware selected".
I hadn't considered that. The hardware seems to allow you to write a 0 mantissa, non-0 exponent. From the SDM, it's unclear what that would mean. The code as written would display "0 us", "0 ms", or "0 s" - not "0 hardware selected". Do you want more explicity printing for those cases? I think it's fine to have a distinction between the output. "0 hardware selected" is the known valid value that is working as expected. The other ones being something different seems good to me since we don't really know what they mean.
Quoted 13 lines
tools/misc/xenpm.c static void print_cpufreq_para(int cpuid, struct xc_get_cpufreq_para *p_cpufreq) · line 819
Quoted 10 lines
tools/misc/xenpm.c +6
-0@@ -773,6 +811,33 @@ static void print_cpufreq_para(int cpuid, struct xc_get_cpufreq_para *p_cpufreq) p_cpufreq->scaling_cur_freq); } +if (strcmp (p_cpufreq->scaling_governor,XEN_HWP_GOVERNOR ) ==0 ) + { +const xc_hwp_para_t *hwp = &p_cpufreq->u.hwp_para; + +printf ("hwp variables :\n" ); + printf(" hardware limits : lowest [%u] most_efficient [%u]\n",Here and ...
Quoted 8 lines
tools/misc/xenpm.c static void print_cpufreq_para(int cpuid, struct xc_get_cpufreq_para *p_cpufreq) · line 823
Quoted 4 lines
tools/misc/xenpm.c +4
-0+ hwp->lowest, hwp->most_efficient); +printf (" : guaranteed [%u] highest [%u]\n" , + hwp->guaranteed, hwp->highest); + printf(" configured limits : min [%u] max [%u] energy_perf [%u]\n",... here I wonder what use the underscores are in produced output. I'd use blanks. If you really want a separator there, then please use dashes.
I'll use blanks.
Regards,
Jason
Re: [PATCH v3 09/14 RESEND] xenpm: Print HWP parameters
Quoted 23 lines · Jason Andryuk
Quoted 7 lines · Jan Beulich
Quoted 6 lines · Jason Andryuk
tools/misc/xenpm.c +0
-0@@ -708,6 +708,44 @@ void start_gather_func(int argc, char *argv[])pause (); }Quoted 14 lines
tools/misc/xenpm.c void start_gather_func(int argc, char *argv[]) · line 718
Quoted 8 lines
tools/misc/xenpm.c +8
-0+static void calculate_hwp_activity_window (const xc_hwp_para_t *hwp, +unsigned int *activity_window, +const char **units) +{ +unsigned int mantissa = hwp->activity_window &HWP_ACT_WINDOW_MANTISSA_MASK ; +unsigned int exponent = + (hwp->activity_window >>HWP_ACT_WINDOW_EXPONENT_SHIFT ) & +HWP_ACT_WINDOW_EXPONENT_MASK ;I wish we had
MASK_EXTR()incommon-macros.h. While really a comment on patch 7 -HWP_ACT_WINDOW_EXPONENT_SHIFTis redundant information and should imo be omitted from the public interface, in favor of just a (suitably shifted) mask value. Also note how those constants all lack properXEN_prefixes.
Quoted 2 lines
I'll add a patch adding
MASK_EXTR()&MASK_INSR()tocommon-macros.hand use those - is there any reason not to do that?
I don't think there is, but I'm also not a maintainer of that code.
Quoted 14 lines
Quoted 5 lines
Quoted 5 lines
tools/misc/xenpm.c +5
-0+unsigned int multiplier =1 ; +unsigned int i; + +if ( hwp->activity_window ==0 ) + {Quoted 8 lines
tools/misc/xenpm.c void start_gather_func(int argc, char *argv[]) · line 728
Quoted 5 lines
tools/misc/xenpm.c +5
-0+ *units ="hardware selected" ; + *activity_window =0 ; + +return ; + }While in line with documentation, any mantissa of 0 results in a 0us window, which I assume would then also mean "hardware selected".
Quoted 8 lines
I hadn't considered that. The hardware seems to allow you to write a 0 mantissa, non-0 exponent. From the SDM, it's unclear what that would mean. The code as written would display "0 us", "0 ms", or "0 s" - not "0 hardware selected". Do you want more explicity printing for those cases? I think it's fine to have a distinction between the output. "0 hardware selected" is the known valid value that is working as expected. The other ones being something different seems good to me since we don't really know what they mean.
Keeping things - apart from perhaps adding a respective comment - is okay, as long as we don't know any better.
Jan
PATCH RESEND v3 10/14 xen: Add SET_CPUFREQ_HWP xen_sysctl_pm_op
In reply to Jason AndryukAdd SET_CPUFREQ_HWP xen_sysctl_pm_op to set HWP parameters. The sysctl supports setting multiple values simultaneously as indicated by the set_params bits. This allows atomically applying new HWP configuration via a single wrmsr.
XEN_SYSCTL_HWP_SET_PRESET_BALANCE/PERFORMANCE/POWERSAVE provide three common presets. Setting them depends on hardware limits which the hypervisor is already caching. So using them allows skipping a hypercall to query the limits (lowest/highest) to then set those same values. The code is organized to allow a preset to be refined with additional stuff if desired.
"most_efficient" and "guaranteed" could be additional presets in the future, but the are not added now. Those levels can change at runtime, but we don't have code in place to monitor and update for those events.
---
v3:
Remove cpufreq_governor_internal from set_cpufreq_hwp
v2:
Update for naming anonymous union
Drop hwp_err for invalid input in set_hwp_para() Drop uint16_t cast in XEN_SYSCTL_HWP_SET_PARAM_MASK Drop parens for HWP_SET_PRESET defines
Reference activity_window format comment
Place SET_CPUFREQ_HWP after SET_CPUFREQ_PARA
Add {HWP,IA32}_ENERGY_PERF_MAX_{PERFORMANCE,POWERSAVE} defines Order defines before fields in sysctl.h
Use XEN_HWP_GOVERNOR
Use per_cpu for hwp_drv_data
--- xen/arch/x86/acpi/cpufreq/hwp.c | 96 ++++++++++++++++++++++++++++++ xen/drivers/acpi/pmstat.c | 18 ++++++ xen/include/acpi/cpufreq/cpufreq.h | 2 + xen/include/public/sysctl.h | 30 ++++++++++ 4 files changed, 146 insertions(+)
xen/arch/x86/acpi/cpufreq/hwp.c +96 -0
@@ -27,7 +27,9 @@ static bool feature_hdc;__initdata bool opt_cpufreq_hwp = false;__initdata bool opt_cpufreq_hdc = true; +#define HWP_ENERGY_PERF_MAX_PERFORMANCE 0#define HWP_ENERGY_PERF_BALANCE 0x80 +#define HWP_ENERGY_PERF_MAX_POWERSAVE 0xff#define IA32_ENERGY_BIAS_BALANCE 0x7#define IA32_ENERGY_BIAS_MAX_POWERSAVE 0xf#define IA32_ENERGY_BIAS_MASK 0xf
@@ -531,6 +533,100 @@ int get_hwp_para(const struct cpufreq_policy *policy,return 0 ; } +int set_hwp_para (struct cpufreq_policy *policy, +struct xen_set_hwp_para *set_hwp) +{ +unsigned int cpu = policy->cpu; +struct hwp_drv_data *data =per_cpu (hwp_drv_data, cpu); + +if ( data ==NULL ) +return -EINVAL ; + +/* Validate all parameters first */ +if ( set_hwp->set_params & ~XEN_SYSCTL_HWP_SET_PARAM_MASK ) +return -EINVAL ; + +if ( set_hwp->activity_window & ~XEN_SYSCTL_HWP_ACT_WINDOW_MASK ) +return -EINVAL ; + +if ( !feature_hwp_energy_perf && + (set_hwp->set_params &XEN_SYSCTL_HWP_SET_ENERGY_PERF ) && + set_hwp->energy_perf >IA32_ENERGY_BIAS_MAX_POWERSAVE ) +return -EINVAL ; + +if ( (set_hwp->set_params &XEN_SYSCTL_HWP_SET_DESIRED ) && + set_hwp->desired !=0 && + (set_hwp->desired < data->hw.lowest || + set_hwp->desired > data->hw.highest) ) +return -EINVAL ; + +/* +* minimum & maximum are not validated as hardware doesn't seem to care +* and the SDM says CPUs will clip internally. +*/ + +/* Apply presets */ +switch ( set_hwp->set_params &XEN_SYSCTL_HWP_SET_PRESET_MASK ) + { +case XEN_SYSCTL_HWP_SET_PRESET_POWERSAVE : + data->minimum = data->hw.lowest; + data->maximum = data->hw.lowest; + data->activity_window =0 ; +if ( feature_hwp_energy_perf ) + data->energy_perf =HWP_ENERGY_PERF_MAX_POWERSAVE ; +else + data->energy_perf =IA32_ENERGY_BIAS_MAX_POWERSAVE ; + data->desired =0 ; +break ; + +case XEN_SYSCTL_HWP_SET_PRESET_PERFORMANCE : + data->minimum = data->hw.highest; + data->maximum = data->hw.highest; + data->activity_window =0 ; + data->energy_perf =HWP_ENERGY_PERF_MAX_PERFORMANCE ; + data->desired =0 ; +break ; + +case XEN_SYSCTL_HWP_SET_PRESET_BALANCE : + data->minimum = data->hw.lowest; + data->maximum = data->hw.highest; + data->activity_window =0 ; +if ( feature_hwp_energy_perf ) + data->energy_perf =HWP_ENERGY_PERF_BALANCE ; +else + data->energy_perf =IA32_ENERGY_BIAS_BALANCE ; + data->desired =0 ; +break ; + +case XEN_SYSCTL_HWP_SET_PRESET_NONE : +break ; + +default : +return -EINVAL ; + } + +/* Further customize presets if needed */ +if ( set_hwp->set_params &XEN_SYSCTL_HWP_SET_MINIMUM ) + data->minimum = set_hwp->minimum; + +if ( set_hwp->set_params &XEN_SYSCTL_HWP_SET_MAXIMUM ) + data->maximum = set_hwp->maximum; + +if ( set_hwp->set_params &XEN_SYSCTL_HWP_SET_ENERGY_PERF ) + data->energy_perf = set_hwp->energy_perf; + +if ( set_hwp->set_params &XEN_SYSCTL_HWP_SET_DESIRED ) + data->desired = set_hwp->desired; + +if ( set_hwp->set_params &XEN_SYSCTL_HWP_SET_ACT_WINDOW ) + data->activity_window = set_hwp->activity_window & +XEN_SYSCTL_HWP_ACT_WINDOW_MASK ; + +hwp_cpufreq_target (policy,0 ,0 ); + +return 0 ; +} +int __init hwp_register_driver (void ) {return cpufreq_register_driver (&hwp_cpufreq_driver);
xen/drivers/acpi/pmstat.c +18 -0
@@ -398,6 +398,20 @@ static int set_cpufreq_para(struct xen_sysctl_pm_op *op)return ret; } +static int set_cpufreq_hwp (struct xen_sysctl_pm_op *op) +{ +struct cpufreq_policy *policy =per_cpu (cpufreq_cpu_policy, op->cpuid); + +if ( !policy || !policy->governor ) +return -EINVAL ; + +if (strncasecmp (policy->governor->name,XEN_HWP_GOVERNOR , +CPUFREQ_NAME_LEN ) ) +return -EINVAL ; + +return set_hwp_para (policy, &op->u.set_hwp); +} +int do_pm_op (struct xen_sysctl_pm_op *op) {int ret =0 ;
@@ -470,6 +484,10 @@ int do_pm_op(struct xen_sysctl_pm_op *op)break ; } +case SET_CPUFREQ_HWP : + ret =set_cpufreq_hwp (op); +break ; +case GET_CPUFREQ_AVGFREQ : { op->u.get_avgfreq =cpufreq_driver_getavg (op->cpuid,USR_GETAVG );
xen/include/acpi/cpufreq/cpufreq.h +2 -0
@@ -249,5 +249,7 @@ extern bool opt_cpufreq_hwp;extern bool opt_cpufreq_hdc;int get_hwp_para (const struct cpufreq_policy *policy,struct xen_hwp_para *hwp_para); +int set_hwp_para (struct cpufreq_policy *policy, +struct xen_set_hwp_para *set_hwp);#endif /* __XEN_CPUFREQ_PM_H__ */
xen/include/public/sysctl.h +30 -0
@@ -317,6 +317,34 @@ struct xen_hwp_para {uint8_t energy_perf; }; +/* set multiple values simultaneously when set_args bit is set */ +struct xen_set_hwp_para { +#define XEN_SYSCTL_HWP_SET_DESIRED (1U << 0) +#define XEN_SYSCTL_HWP_SET_ENERGY_PERF (1U << 1) +#define XEN_SYSCTL_HWP_SET_ACT_WINDOW (1U << 2) +#define XEN_SYSCTL_HWP_SET_MINIMUM (1U << 3) +#define XEN_SYSCTL_HWP_SET_MAXIMUM (1U << 4) +#define XEN_SYSCTL_HWP_SET_PRESET_MASK 0xf000 +#define XEN_SYSCTL_HWP_SET_PRESET_NONE 0x0000 +#define XEN_SYSCTL_HWP_SET_PRESET_BALANCE 0x1000 +#define XEN_SYSCTL_HWP_SET_PRESET_POWERSAVE 0x2000 +#define XEN_SYSCTL_HWP_SET_PRESET_PERFORMANCE 0x3000 +#define XEN_SYSCTL_HWP_SET_PARAM_MASK ( \ + XEN_SYSCTL_HWP_SET_PRESET_MASK | \ + XEN_SYSCTL_HWP_SET_DESIRED | \ + XEN_SYSCTL_HWP_SET_ENERGY_PERF | \ + XEN_SYSCTL_HWP_SET_ACT_WINDOW | \ + XEN_SYSCTL_HWP_SET_MINIMUM | \ + XEN_SYSCTL_HWP_SET_MAXIMUM ) +uint16_t set_params;/* bitflags for valid values */ +#define XEN_SYSCTL_HWP_ACT_WINDOW_MASK 0x03ff +uint16_t activity_window;/* See comment in struct xen_hwp_para */ +uint8_t minimum; +uint8_t maximum; +uint8_t desired; +uint8_t energy_perf;/* 0-255 or 0-15 depending on HW support */ +}; +#define XEN_HWP_GOVERNOR "hwp-internal"/* * cpufreq para name of this structure named
@@ -379,6 +407,7 @@ struct xen_sysctl_pm_op {#define SET_CPUFREQ_GOV (CPUFREQ_PARA | 0x02)#define SET_CPUFREQ_PARA (CPUFREQ_PARA | 0x03)#define GET_CPUFREQ_AVGFREQ (CPUFREQ_PARA | 0x04) +#define SET_CPUFREQ_HWP (CPUFREQ_PARA | 0x05)/* set/reset scheduler power saving option */ #define XEN_SYSCTL_pm_op_set_sched_opt_smt 0x21
@@ -405,6 +434,7 @@ struct xen_sysctl_pm_op {struct xen_get_cpufreq_para get_para;struct xen_set_cpufreq_gov set_gov;struct xen_set_cpufreq_para set_para; +struct xen_set_hwp_para set_hwp;uint64_aligned_t get_avgfreq;uint32_t set_sched_opt_smt;#define XEN_SYSCTL_CX_UNLIMITED 0xffffffff
Signature · 1 line
2.40.0
Re: [PATCH v3 10/14 RESEND] xen: Add SET_CPUFREQ_HWP xen_sysctl_pm_op
xen/arch/x86/acpi/cpufreq/hwp.c int get_hwp_para(const struct cpufreq_policy *policy, · line 537
Quoted 6 lines · Jason Andryuk
xen/arch/x86/acpi/cpufreq/hwp.c +2
-0@@ -531,6 +533,100 @@ int get_hwp_para(const struct cpufreq_policy *policy,return 0 ; } +int set_hwp_para (struct cpufreq_policy *policy, +struct xen_set_hwp_para *set_hwp)
const?
xen/arch/x86/acpi/cpufreq/hwp.c int get_hwp_para(const struct cpufreq_policy *policy, · line 550
Quoted 13 lines
xen/arch/x86/acpi/cpufreq/hwp.c +13
-0+{ +unsigned int cpu = policy->cpu; +struct hwp_drv_data *data =per_cpu (hwp_drv_data, cpu); + +if ( data ==NULL ) +return -EINVAL ; + +/* Validate all parameters first */ +if ( set_hwp->set_params & ~XEN_SYSCTL_HWP_SET_PARAM_MASK ) +return -EINVAL ; + +if ( set_hwp->activity_window & ~XEN_SYSCTL_HWP_ACT_WINDOW_MASK ) +return -EINVAL ;
Below you limit checks to when the respective control bit is set. I think you want the same here.
Quoted 45 lines
xen/arch/x86/acpi/cpufreq/hwp.c +45
-0+if ( !feature_hwp_energy_perf && + (set_hwp->set_params &XEN_SYSCTL_HWP_SET_ENERGY_PERF ) && + set_hwp->energy_perf >IA32_ENERGY_BIAS_MAX_POWERSAVE ) +return -EINVAL ; + +if ( (set_hwp->set_params &XEN_SYSCTL_HWP_SET_DESIRED ) && + set_hwp->desired !=0 && + (set_hwp->desired < data->hw.lowest || + set_hwp->desired > data->hw.highest) ) +return -EINVAL ; + +/* +* minimum & maximum are not validated as hardware doesn't seem to care +* and the SDM says CPUs will clip internally. +*/ + +/* Apply presets */ +switch ( set_hwp->set_params &XEN_SYSCTL_HWP_SET_PRESET_MASK ) + { +case XEN_SYSCTL_HWP_SET_PRESET_POWERSAVE : + data->minimum = data->hw.lowest; + data->maximum = data->hw.lowest; + data->activity_window =0 ; +if ( feature_hwp_energy_perf ) + data->energy_perf =HWP_ENERGY_PERF_MAX_POWERSAVE ; +else + data->energy_perf =IA32_ENERGY_BIAS_MAX_POWERSAVE ; + data->desired =0 ; +break ; + +case XEN_SYSCTL_HWP_SET_PRESET_PERFORMANCE : + data->minimum = data->hw.highest; + data->maximum = data->hw.highest; + data->activity_window =0 ; + data->energy_perf =HWP_ENERGY_PERF_MAX_PERFORMANCE ; + data->desired =0 ; +break ; + +case XEN_SYSCTL_HWP_SET_PRESET_BALANCE : + data->minimum = data->hw.lowest; + data->maximum = data->hw.highest; + data->activity_window =0 ; +if ( feature_hwp_energy_perf ) + data->energy_perf =HWP_ENERGY_PERF_BALANCE ; +else
xen/arch/x86/acpi/cpufreq/hwp.c int get_hwp_para(const struct cpufreq_policy *policy, · line 606
Quoted 10 lines
xen/arch/x86/acpi/cpufreq/hwp.c +10
-0+ data->energy_perf =IA32_ENERGY_BIAS_BALANCE ; + data->desired =0 ; +break ; + +case XEN_SYSCTL_HWP_SET_PRESET_NONE : +break ; + +default : +return -EINVAL ; + }
So presets set all the values for which the individual item control bits are clear. That's not exactly what I would have expected, and it took me reading the code several times until I realized that you write life per- CPU data fields here, not fields of some intermediate variable. I think this could do with saying explicitly in the public header (if indeed the intended model).
Quoted 10 lines
xen/arch/x86/acpi/cpufreq/hwp.c +10
-0+/* Further customize presets if needed */ +if ( set_hwp->set_params &XEN_SYSCTL_HWP_SET_MINIMUM ) + data->minimum = set_hwp->minimum; + +if ( set_hwp->set_params &XEN_SYSCTL_HWP_SET_MAXIMUM ) + data->maximum = set_hwp->maximum; + +if ( set_hwp->set_params &XEN_SYSCTL_HWP_SET_ENERGY_PERF ) + data->energy_perf = set_hwp->energy_perf; +
xen/arch/x86/acpi/cpufreq/hwp.c int get_hwp_para(const struct cpufreq_policy *policy, · line 627
Quoted 10 lines
xen/arch/x86/acpi/cpufreq/hwp.c +10
-0+if ( set_hwp->set_params &XEN_SYSCTL_HWP_SET_DESIRED ) + data->desired = set_hwp->desired; + +if ( set_hwp->set_params &XEN_SYSCTL_HWP_SET_ACT_WINDOW ) + data->activity_window = set_hwp->activity_window & +XEN_SYSCTL_HWP_ACT_WINDOW_MASK ; + +hwp_cpufreq_target (policy,0 ,0 ); + +return 0 ;
I don't think you should assume here that hwp_cpufreq_target() will only ever return 0. Plus by returning its return value here you allow the compiler to tail-call optimize this code.
xen/drivers/acpi/pmstat.c static int set_cpufreq_para(struct xen_sysctl_pm_op *op) · line 401
Quoted 7 lines
xen/drivers/acpi/pmstat.c +1
-0@@ -398,6 +398,20 @@ static int set_cpufreq_para(struct xen_sysctl_pm_op *op)return ret; } +static int set_cpufreq_hwp (struct xen_sysctl_pm_op *op)
const?
xen/include/public/sysctl.h struct xen_hwp_para { · line 320
Quoted 7 lines
xen/include/public/sysctl.h +1
-0@@ -317,6 +317,34 @@ struct xen_hwp_para {uint8_t energy_perf; }; +/* set multiple values simultaneously when set_args bit is set */
What "set_args bit" does this comment refer to?
Quoted 15 lines
xen/include/public/sysctl.h +15
-0+struct xen_set_hwp_para { +#define XEN_SYSCTL_HWP_SET_DESIRED (1U << 0) +#define XEN_SYSCTL_HWP_SET_ENERGY_PERF (1U << 1) +#define XEN_SYSCTL_HWP_SET_ACT_WINDOW (1U << 2) +#define XEN_SYSCTL_HWP_SET_MINIMUM (1U << 3) +#define XEN_SYSCTL_HWP_SET_MAXIMUM (1U << 4) +#define XEN_SYSCTL_HWP_SET_PRESET_MASK 0xf000 +#define XEN_SYSCTL_HWP_SET_PRESET_NONE 0x0000 +#define XEN_SYSCTL_HWP_SET_PRESET_BALANCE 0x1000 +#define XEN_SYSCTL_HWP_SET_PRESET_POWERSAVE 0x2000 +#define XEN_SYSCTL_HWP_SET_PRESET_PERFORMANCE 0x3000 +#define XEN_SYSCTL_HWP_SET_PARAM_MASK ( \ + XEN_SYSCTL_HWP_SET_PRESET_MASK | \ + XEN_SYSCTL_HWP_SET_DESIRED | \ + XEN_SYSCTL_HWP_SET_ENERGY_PERF | \
xen/include/public/sysctl.h struct xen_hwp_para { · line 345
Quoted 10 lines
xen/include/public/sysctl.h +10
-0+XEN_SYSCTL_HWP_SET_ACT_WINDOW | \ +XEN_SYSCTL_HWP_SET_MINIMUM | \ + XEN_SYSCTL_HWP_SET_MAXIMUM ) + uint16_t set_params; /* bitflags for valid values */ +#define XEN_SYSCTL_HWP_ACT_WINDOW_MASK 0x03ff +uint16_t activity_window;/* See comment in struct xen_hwp_para */ +uint8_t minimum; +uint8_t maximum; +uint8_t desired; +uint8_t energy_perf;/* 0-255 or 0-15 depending on HW support */
Instead of (or in addition to) the "HW support" reference, could this gain a reference to the "get para" bit determining which range to use?
Jan
Re: [PATCH v3 10/14 RESEND] xen: Add SET_CPUFREQ_HWP xen_sysctl_pm_op
Quoted 10 lines · Jan Beulich
xen/arch/x86/acpi/cpufreq/hwp.c int get_hwp_para(const struct cpufreq_policy *policy, · line 537
Quoted 6 lines · Jason Andryuk
xen/arch/x86/acpi/cpufreq/hwp.c +2
-0@@ -531,6 +533,100 @@ int get_hwp_para(const struct cpufreq_policy *policy,return 0 ; } +int set_hwp_para (struct cpufreq_policy *policy, +struct xen_set_hwp_para *set_hwp)const?
set_hwp can be const. policy is passed to hwp_cpufreq_target() & on_selected_cpus(), so it cannot readily be made const.
Quoted 8 lines
Quoted 8 lines
xen/arch/x86/acpi/cpufreq/hwp.c +8
-0+{ +unsigned int cpu = policy->cpu; +struct hwp_drv_data *data =per_cpu (hwp_drv_data, cpu); + +if ( data ==NULL ) +return -EINVAL ; + +/* Validate all parameters first */
Quoted 8 lines
xen/arch/x86/acpi/cpufreq/hwp.c int get_hwp_para(const struct cpufreq_policy *policy, · line 550
Quoted 5 lines
xen/arch/x86/acpi/cpufreq/hwp.c +5
-0+if ( set_hwp->set_params & ~XEN_SYSCTL_HWP_SET_PARAM_MASK ) +return -EINVAL ; + +if ( set_hwp->activity_window & ~XEN_SYSCTL_HWP_ACT_WINDOW_MASK ) +return -EINVAL ;Below you limit checks to when the respective control bit is set. I think you want the same here.
Not sure if you mean feature_hwp_activity_window or the bit in set_params as control bit. But, yes, they can both use some additional checking. IIRC, I wanted to always check ~XEN_SYSCTL_HWP_ACT_WINDOW_MASK, because bits should never be set whether or not the activity window is supported by hardware.
Quoted 54 lines
Quoted 54 lines
xen/arch/x86/acpi/cpufreq/hwp.c +54
-0+if ( !feature_hwp_energy_perf && + (set_hwp->set_params &XEN_SYSCTL_HWP_SET_ENERGY_PERF ) && + set_hwp->energy_perf >IA32_ENERGY_BIAS_MAX_POWERSAVE ) +return -EINVAL ; + +if ( (set_hwp->set_params &XEN_SYSCTL_HWP_SET_DESIRED ) && + set_hwp->desired !=0 && + (set_hwp->desired < data->hw.lowest || + set_hwp->desired > data->hw.highest) ) +return -EINVAL ; + +/* +* minimum & maximum are not validated as hardware doesn't seem to care +* and the SDM says CPUs will clip internally. +*/ + +/* Apply presets */ +switch ( set_hwp->set_params &XEN_SYSCTL_HWP_SET_PRESET_MASK ) + { +case XEN_SYSCTL_HWP_SET_PRESET_POWERSAVE : + data->minimum = data->hw.lowest; + data->maximum = data->hw.lowest; + data->activity_window =0 ; +if ( feature_hwp_energy_perf ) + data->energy_perf =HWP_ENERGY_PERF_MAX_POWERSAVE ; +else + data->energy_perf =IA32_ENERGY_BIAS_MAX_POWERSAVE ; + data->desired =0 ; +break ; + +case XEN_SYSCTL_HWP_SET_PRESET_PERFORMANCE : + data->minimum = data->hw.highest; + data->maximum = data->hw.highest; + data->activity_window =0 ; + data->energy_perf =HWP_ENERGY_PERF_MAX_PERFORMANCE ; + data->desired =0 ; +break ; + +case XEN_SYSCTL_HWP_SET_PRESET_BALANCE : + data->minimum = data->hw.lowest; + data->maximum = data->hw.highest; + data->activity_window =0 ; +if ( feature_hwp_energy_perf ) + data->energy_perf =HWP_ENERGY_PERF_BALANCE ; +else + data->energy_perf =IA32_ENERGY_BIAS_BALANCE ; + data->desired =0 ; +break ; + +case XEN_SYSCTL_HWP_SET_PRESET_NONE : +break ; + +default : +return -EINVAL ;
Quoted 8 lines
Review int get_hwp_para(const struct cpufreq_policy *policy, · line 605
Quoted 1 line
(quoted diff) +1
-0+ }So presets set all the values for which the individual item control bits are clear. That's not exactly what I would have expected, and it took me reading the code several times until I realized that you write life per- CPU data fields here, not fields of some intermediate variable. I think this could do with saying explicitly in the public header (if indeed the intended model).
The commit message mentioned the idea of using a preset and further refinement. The comments above "/* Apply presets */" and below "/* Further customize presets if needed */" were an attempt to highlight that. But you are right that the public header should state this clearly.
Quoted 16 lines
Quoted 16 lines
xen/arch/x86/acpi/cpufreq/hwp.c +16
-0+/* Further customize presets if needed */ +if ( set_hwp->set_params &XEN_SYSCTL_HWP_SET_MINIMUM ) + data->minimum = set_hwp->minimum; + +if ( set_hwp->set_params &XEN_SYSCTL_HWP_SET_MAXIMUM ) + data->maximum = set_hwp->maximum; + +if ( set_hwp->set_params &XEN_SYSCTL_HWP_SET_ENERGY_PERF ) + data->energy_perf = set_hwp->energy_perf; + +if ( set_hwp->set_params &XEN_SYSCTL_HWP_SET_DESIRED ) + data->desired = set_hwp->desired; + +if ( set_hwp->set_params &XEN_SYSCTL_HWP_SET_ACT_WINDOW ) + data->activity_window = set_hwp->activity_window & +XEN_SYSCTL_HWP_ACT_WINDOW_MASK ;
Quoted 8 lines
xen/arch/x86/acpi/cpufreq/hwp.c int get_hwp_para(const struct cpufreq_policy *policy, · line 627
Quoted 4 lines
xen/arch/x86/acpi/cpufreq/hwp.c +4
-0+ +hwp_cpufreq_target (policy,0 ,0 ); + +return 0 ;I don't think you should assume here that
hwp_cpufreq_target()will only ever return 0. Plus by returning its return value here you allow the compiler to tail-call optimize this code.
Thanks for catching that. Yeah, I made hwp_cpufreq_target() return a value per your earlier comment, so its value should be returned now.
Quoted 9 lines
xen/drivers/acpi/pmstat.c static int set_cpufreq_para(struct xen_sysctl_pm_op *op) · line 401
Quoted 7 lines
xen/drivers/acpi/pmstat.c +1
-0@@ -398,6 +398,20 @@ static int set_cpufreq_para(struct xen_sysctl_pm_op *op)return ret; } +static int set_cpufreq_hwp (struct xen_sysctl_pm_op *op)const?
Yes
Quoted 9 lines
xen/include/public/sysctl.h struct xen_hwp_para { · line 320
Quoted 7 lines
xen/include/public/sysctl.h +1
-0@@ -317,6 +317,34 @@ struct xen_hwp_para {uint8_t energy_perf; }; +/* set multiple values simultaneously when set_args bit is set */ What "
set_argsbit" does this comment refer to?
That should be set_params. IIRC, set_args was the previous name.
Quoted 20 lines
Quoted 20 lines
xen/include/public/sysctl.h +20
-0+struct xen_set_hwp_para { +#define XEN_SYSCTL_HWP_SET_DESIRED (1U << 0) +#define XEN_SYSCTL_HWP_SET_ENERGY_PERF (1U << 1) +#define XEN_SYSCTL_HWP_SET_ACT_WINDOW (1U << 2) +#define XEN_SYSCTL_HWP_SET_MINIMUM (1U << 3) +#define XEN_SYSCTL_HWP_SET_MAXIMUM (1U << 4) +#define XEN_SYSCTL_HWP_SET_PRESET_MASK 0xf000 +#define XEN_SYSCTL_HWP_SET_PRESET_NONE 0x0000 +#define XEN_SYSCTL_HWP_SET_PRESET_BALANCE 0x1000 +#define XEN_SYSCTL_HWP_SET_PRESET_POWERSAVE 0x2000 +#define XEN_SYSCTL_HWP_SET_PRESET_PERFORMANCE 0x3000 +#define XEN_SYSCTL_HWP_SET_PARAM_MASK ( \ + XEN_SYSCTL_HWP_SET_PRESET_MASK | \ + XEN_SYSCTL_HWP_SET_DESIRED | \ + XEN_SYSCTL_HWP_SET_ENERGY_PERF | \ + XEN_SYSCTL_HWP_SET_ACT_WINDOW | \ + XEN_SYSCTL_HWP_SET_MINIMUM | \ + XEN_SYSCTL_HWP_SET_MAXIMUM ) +uint16_t set_params;/* bitflags for valid values */ +#define XEN_SYSCTL_HWP_ACT_WINDOW_MASK 0x03ff
Quoted 8 lines
xen/include/public/sysctl.h struct xen_hwp_para { · line 345
Quoted 5 lines
xen/include/public/sysctl.h +5
-0+uint16_t activity_window;/* See comment in struct xen_hwp_para */ +uint8_t minimum; +uint8_t maximum; +uint8_t desired; +uint8_t energy_perf;/* 0-255 or 0-15 depending on HW support */ Instead of (or in addition to) the "HW support" reference, could this gain a reference to the "get para" bit determining which range to use?
I've removed the fallback 0-15 support locally, so this will be removed.
Regards,
Jason
Re: [PATCH v3 10/14 RESEND] xen: Add SET_CPUFREQ_HWP xen_sysctl_pm_op
Quoted 7 lines · Jason Andryuk
Quoted 6 lines · Jan Beulich
Quoted 4 lines · Jason Andryuk
xen/arch/x86/acpi/cpufreq/hwp.c +0
-0@@ -531,6 +533,100 @@ int get_hwp_para(const struct cpufreq_policy *policy,return 0 ; }
Quoted 7 lines
Quoted 4 lines
xen/arch/x86/acpi/cpufreq/hwp.c int get_hwp_para(const struct cpufreq_policy *policy, · line 537
Quoted 2 lines
xen/arch/x86/acpi/cpufreq/hwp.c +2
-0+int set_hwp_para (struct cpufreq_policy *policy, +struct xen_set_hwp_para *set_hwp)const?
set_hwpcan be const. policy is passed tohwp_cpufreq_target()&on_selected_cpus(), so it cannot readily be made const.
I was only meaning the 2nd parameter, yes.
Quoted 17 lines
Quoted 8 lines
Quoted 8 lines
xen/arch/x86/acpi/cpufreq/hwp.c +8
-0+{ +unsigned int cpu = policy->cpu; +struct hwp_drv_data *data =per_cpu (hwp_drv_data, cpu); + +if ( data ==NULL ) +return -EINVAL ; + +/* Validate all parameters first */ Quoted 8 lines
xen/arch/x86/acpi/cpufreq/hwp.c int get_hwp_para(const struct cpufreq_policy *policy, · line 550
Quoted 5 lines
xen/arch/x86/acpi/cpufreq/hwp.c +5
-0+if ( set_hwp->set_params & ~XEN_SYSCTL_HWP_SET_PARAM_MASK ) +return -EINVAL ; + +if ( set_hwp->activity_window & ~XEN_SYSCTL_HWP_ACT_WINDOW_MASK ) +return -EINVAL ;Below you limit checks to when the respective control bit is set. I think you want the same here.
Quoted 5 lines
Not sure if you mean
feature_hwp_activity_windowor the bit inset_paramsas control bit. But, yes, they can both use some additional checking. IIRC, I wanted to always check ~XEN_SYSCTL_HWP_ACT_WINDOW_MASK, because bits should never be set whether or not the activity window is supported by hardware.
I took ...
Quoted 10 lines
Quoted 10 lines
xen/arch/x86/acpi/cpufreq/hwp.c int get_hwp_para(const struct cpufreq_policy *policy, · line 561
Quoted 10 lines
xen/arch/x86/acpi/cpufreq/hwp.c +10
-0+if ( !feature_hwp_energy_perf && + (set_hwp->set_params &XEN_SYSCTL_HWP_SET_ENERGY_PERF ) && + set_hwp->energy_perf >IA32_ENERGY_BIAS_MAX_POWERSAVE ) +return -EINVAL ; + +if ( (set_hwp->set_params &XEN_SYSCTL_HWP_SET_DESIRED ) && + set_hwp->desired !=0 && + (set_hwp->desired < data->hw.lowest || + set_hwp->desired > data->hw.highest) ) +return -EINVAL ;
... e.g. this for comparison, where you apply the range check only when the XEN_SYSCTL_HWP_* bit is set. I think you want to be consistent in such checking: Either you always allow the caller to not care about fields that aren't going to be consumed when their controlling bit is off, or you always check validity. Both approaches have their pros and cons, I think.
Jan
Re: [PATCH v3 10/14 RESEND] xen: Add SET_CPUFREQ_HWP xen_sysctl_pm_op
Quoted 30 lines · Jan Beulich
Quoted 6 lines · Jason Andryuk
Quoted 5 lines · Jan Beulich
Quoted 2 lines · Jason Andryuk
(quoted diff) +2
-0+ if ( set_hwp->activity_window & ~XEN_SYSCTL_HWP_ACT_WINDOW_MASK ) + return -EINVAL;Quoted 8 lines
Quoted 2 lines
Below you limit checks to when the respective control bit is set. I think you want the same here.
Not sure if you mean
feature_hwp_activity_windowor the bit inset_paramsas control bit. But, yes, they can both use some additional checking. IIRC, I wanted to always check ~XEN_SYSCTL_HWP_ACT_WINDOW_MASK, because bits should never be set whether or not the activity window is supported by hardware.I took ...
Quoted 10 lines
Quoted 10 lines
xen/arch/x86/acpi/cpufreq/hwp.c int get_hwp_para(const struct cpufreq_policy *policy, · line 561
Quoted 10 lines
xen/arch/x86/acpi/cpufreq/hwp.c +10
-0+if ( !feature_hwp_energy_perf && + (set_hwp->set_params &XEN_SYSCTL_HWP_SET_ENERGY_PERF ) && + set_hwp->energy_perf >IA32_ENERGY_BIAS_MAX_POWERSAVE ) +return -EINVAL ; + +if ( (set_hwp->set_params &XEN_SYSCTL_HWP_SET_DESIRED ) && + set_hwp->desired !=0 && + (set_hwp->desired < data->hw.lowest || + set_hwp->desired > data->hw.highest) ) +return -EINVAL ;
Quoted 6 lines
... e.g. this for comparison, where you apply the range check only when the XEN_SYSCTL_HWP_* bit is set. I think you want to be consistent in such checking: Either you always allow the caller to not care about fields that aren't going to be consumed when their controlling bit is off, or you always check validity. Both approaches have their pros and cons, I think.
Ok, good point. I wrote it inconsistently because the SDM states the desired limit: "When set to a non-zero value (between the range of Lowest_Performance and Highest_Performance of IA32_HWP_CAPABILITIES) conveys an explicit performance request hint to the hardware; effectively disabling HW Autonomous selection." And I was trying to follow that. But later "The HWP hardware clips and resolves the field values as necessary to the valid range." seems to override that. I'll test to verify that it is correct, and drop the lowest/highest checking if so.
Thanks,
Jason
PATCH RESEND v3 11/14 libxc: Add xc_set_cpufreq_hwp
In reply to Jason AndryukAdd xc_set_cpufreq_hwp to allow calling xen_systctl_pm_op SET_CPUFREQ_HWP.
---
v2:
Mark xc_set_hwp_para_t const
--- tools/include/xenctrl.h | 4 ++++ tools/libs/ctrl/xc_pm.c | 18 ++++++++++++++++++ 2 files changed, 22 insertions(+)
tools/include/xenctrl.h +4 -0
@@ -1937,11 +1937,15 @@ struct xc_get_cpufreq_para {int32_t turbo_enabled; }; +typedef struct xen_set_hwp_para xc_set_hwp_para_t ; +int xc_get_cpufreq_para (xc_interface *xch,int cpuid,struct xc_get_cpufreq_para *user_para);int xc_set_cpufreq_gov (xc_interface *xch,int cpuid,char *govname);int xc_set_cpufreq_para (xc_interface *xch,int cpuid,int ctrl_type,int ctrl_value); +int xc_set_cpufreq_hwp (xc_interface *xch,int cpuid, +const xc_set_hwp_para_t *set_hwp);int xc_get_cpufreq_avgfreq (xc_interface *xch,int cpuid,int *avg_freq);int xc_set_sched_opt_smt (xc_interface *xch,uint32_t value);
tools/libs/ctrl/xc_pm.c +18 -0
@@ -330,6 +330,24 @@ int xc_set_cpufreq_para(xc_interface *xch, int cpuid,return xc_sysctl (xch, &sysctl); } +int xc_set_cpufreq_hwp (xc_interface *xch,int cpuid, +const xc_set_hwp_para_t *set_hwp) +{ +DECLARE_SYSCTL ; + +if ( !xch ) + { + errno =EINVAL ; +return -1 ; + } + sysctl.cmd = XEN_SYSCTL_pm_op; + sysctl.u.pm_op.cmd =SET_CPUFREQ_HWP ; + sysctl.u.pm_op.cpuid = cpuid; + sysctl.u.pm_op.u.set_hwp = *set_hwp; + +return xc_sysctl (xch, &sysctl); +} +int xc_get_cpufreq_avgfreq (xc_interface *xch,int cpuid,int *avg_freq) {int ret =0 ;
Signature · 1 line
2.40.0
Re: [PATCH v3 11/14 RESEND] libxc: Add xc_set_cpufreq_hwp
Quoted 4 lines · Jason Andryuk
Add
xc_set_cpufreq_hwpto allow callingxen_systctl_pm_opSET_CPUFREQ_HWP.Signed-off-by Jason Andryuk <[email protected]>
Thanks,
Signature · 1 line
Anthony PERARD
PATCH RESEND v3 12/14 xenpm: Factor out a non-fatal cpuid_parse variant
In reply to Jason AndryukAllow cpuid_parse to be re-used without terminating xenpm. HWP will re-use it to optionally parse a cpuid. Unlike other uses of cpuid_parse, parse_hwp_opts will take a variable number of arguments and cannot just check argc.
---
v2:
Retained because cpuid_parse handles numeric cpu numbers and "all".
--- tools/misc/xenpm.c | 19 ++++++++++++++----- 1 file changed, 14 insertions(+), 5 deletions(-)
tools/misc/xenpm.c +14 -5
@@ -79,17 +79,26 @@ void help_func(int argc, char *argv[])show_help (); } -static void parse_cpuid (const char *arg,int *cpuid) +static int parse_cpuid_non_fatal (const char *arg,int *cpuid) {if (sscanf (arg,"%d" , cpuid) !=1 || *cpuid <0 ) {if (strcasecmp (arg,"all" ) ) - { -fprintf (stderr,"Invalid CPU identifier: '%s'\n" , arg); -exit (EINVAL ); - } +return -1 ; + *cpuid =-1 ; } + +return 0 ; +} + +static void parse_cpuid (const char *arg,int *cpuid) +{ +if (parse_cpuid_non_fatal (arg, cpuid) ) + { +fprintf (stderr,"Invalid CPU identifier: '%s'\n" , arg); +exit (EINVAL ); + } } static void parse_cpuid_and_int(int argc, char *argv[],
Signature · 1 line
2.40.0
Re: [PATCH v3 12/14 RESEND] xenpm: Factor out a non-fatal cpuid_parse variant
Quoted 9 lines · Jason Andryuk
Allow
cpuid_parseto be re-used without terminating xenpm. HWP will re-use it to optionally parse a cpuid. Unlike other uses ofcpuid_parse,parse_hwp_optswill take a variable number of arguments and cannot just check argc.Signed-off-by Jason Andryuk <[email protected]>---
v2:
Retained becausecpuid_parsehandles numeric cpu numbers and "all".
Assuming you can convince me of retaining this patch:
Quoted 13 lines
tools/misc/xenpm.c +1
-2@@ -79,17 +79,26 @@ void help_func(int argc, char *argv[])show_help (); } -static void parse_cpuid (const char *arg,int *cpuid) +static int parse_cpuid_non_fatal (const char *arg,int *cpuid) {if (sscanf (arg,"%d" , cpuid) !=1 || *cpuid <0 ) {if (strcasecmp (arg,"all" ) ) - {
tools/misc/xenpm.c void help_func(int argc, char *argv[]) · line 93
Quoted 10 lines
tools/misc/xenpm.c +5
-3-fprintf (stderr,"Invalid CPU identifier: '%s'\n" , arg); -exit (EINVAL ); - } +return -1 ; + *cpuid =-1 ; } + +return 0 ; +}
Looks like this function wants to return bool?
Jan
PATCH RESEND v3 13/14 xenpm: Add set-cpufreq-hwp subcommand
In reply to Jason Andryukset-cpufreq-hwp allows setting the Hardware P-State (HWP) parameters.
It can be run on all or just a single cpu. There are presets of balance, powersave & performance. Those can be further tweaked by param:val arguments as explained in the usage description.
Parameter names are just checked to the first 3 characters to shorten typing.
Some options are hardware dependent, and ranges can be found in get-cpufreq-para.
---
v2:
Compare provided parameter name and not just 3 characters. Use "-" in parameter names
Remove hw_
Replace sscanf with strchr & strtoul.
Remove toplevel error message with lower level ones. Help text s/127/128/
Help text mention truncation.
Avoid some truncation rounding down by adding 5 before division. Help test mention default microseconds
Also comment the limit check written to avoid overflow.
--- tools/misc/xenpm.c | 230 +++++++++++++++++++++++++++++++++++++++++++++ 1 file changed, 230 insertions(+)
tools/misc/xenpm.c +230 -0
@@ -16,6 +16,7 @@*/ #define MAX_NR_CPU 512 +#include <limits.h> #include <stdio.h> #include <stdlib.h> #include <unistd.h>
@@ -67,6 +68,27 @@ void show_help(void)" set-max-cstate <num>|'unlimited' [<num2>|'unlimited']\n" " set the C-State limitation (<num> >= 0) and\n" " optionally the C-sub-state limitation (<num2> >= 0)\n" +" set-cpufreq-hwp [cpuid] [balance|performance|powersave] <param:val>*\n" +" set Hardware P-State (HWP) parameters\n" +" optionally a preset of one of\n" +" balance|performance|powersave\n" +" an optional list of param:val arguments\n" +" minimum:N lowest ... highest\n" +" maximum:N lowest ... highest\n" +" desired:N lowest ... highest\n" +" Set explicit performance target.\n" +" non-zero disables auto-HWP mode.\n" +" energy-perf:0-255 (or 0-15)\n" +" energy/performance hint\n" +" lower - favor performance\n" +" higher - favor powersave\n" +" 128 (or 7) - balance\n" +" act-window:N{,m,u}s range 1us-1270s\n" +" window for internal calculations.\n" +" Defaults to us without units.\n" +" Truncates un-representable values.\n" +" 0 lets the hardware decide.\n" +" get-cpufreq-para returns lowest/highest.\n" " start [seconds] start collect Cx/Px statistics,\n" " output after CTRL-C or SIGINT or several seconds.\n" " enable-turbo-mode [cpuid] enable Turbo Mode for processors that support it.\n"
@@ -1299,6 +1321,213 @@ void disable_turbo_mode(int argc, char *argv[]) errno, strerror(errno)); } +/* +* Parse activity_window:NNN{us,ms,s} and validate range. +* +* Activity window is a 7bit mantissa (0-127) with a 3bit exponent (0-7) base +* 10 in microseconds. So the range is 1 microsecond to 1270 seconds. A value +* of 0 lets the hardware autonomously select the window. +* +* Return 0 on success +* -1 on error +*/ +static int parse_activity_window (xc_set_hwp_para_t *set_hwp,unsigned long u, +const char *suffix) +{ +unsigned int exponent =0 ; +unsigned int multiplier =1 ; + +if ( suffix && suffix[0 ] ) + { +if (strcasecmp (suffix,"s" ) ==0 ) + { + multiplier =1000 *1000 ; + exponent =6 ; + } +else if (strcasecmp (suffix,"ms" ) ==0 ) + { + multiplier =1000 ; + exponent =3 ; + } +else if (strcasecmp (suffix,"us" ) ==0 ) + { + multiplier =1 ; + exponent =0 ; + } +else + { +fprintf (stderr,"invalid activity window units: \"%s\"\n" , suffix); + +return -1 ; + } + } + +/* u * multipler > 1270 * 1000 * 1000 transformed to avoid overflow. */ +if ( u >1270 *1000 *1000 / multiplier ) + { +fprintf (stderr,"activity window is too large\n" ); + +return -1 ; + } + +/* looking for 7 bits of mantissa and 3 bits of exponent */ +while ( u >127 ) + { + u +=5 ;/* Round up to mitigate truncation rounding down +e.g. 128 -> 120 vs 128 -> 130. */ + u /=10 ; + exponent +=1 ; + } + + set_hwp->activity_window = (exponent &HWP_ACT_WINDOW_EXPONENT_MASK ) << +HWP_ACT_WINDOW_EXPONENT_SHIFT | + (u &HWP_ACT_WINDOW_MANTISSA_MASK ); + set_hwp->set_params |=XEN_SYSCTL_HWP_SET_ACT_WINDOW ; + +return 0 ; +} + +static int parse_hwp_opts (xc_set_hwp_para_t *set_hwp,int *cpuid, +int argc,char *argv[]) +{ +int i =0 ; + +if ( argc <1 ) { +fprintf (stderr,"Missing arguments\n" ); +return -1 ; + } + +if (parse_cpuid_non_fatal (argv[i], cpuid) ==0 ) + { + i++; + } + +if ( i == argc ) { +fprintf (stderr,"Missing arguments\n" ); +return -1 ; + } + +if (strcasecmp (argv[i],"powersave" ) ==0 ) + { + set_hwp->set_params =XEN_SYSCTL_HWP_SET_PRESET_POWERSAVE ; + i++; + } +else if (strcasecmp (argv[i],"performance" ) ==0 ) + { + set_hwp->set_params =XEN_SYSCTL_HWP_SET_PRESET_PERFORMANCE ; + i++; + } +else if (strcasecmp (argv[i],"balance" ) ==0 ) + { + set_hwp->set_params =XEN_SYSCTL_HWP_SET_PRESET_BALANCE ; + i++; + } + +for ( ; i < argc; i++) + { +unsigned long val; +char *param = argv[i]; +char *value; +char *suffix; +int ret; + + value =strchr (param,':' ); +if ( value ==NULL ) + { +fprintf (stderr,"\"%s\" is an invalid hwp parameter\n" , argv[i]); +return -1 ; + } + + value[0 ] ='\0' ; + value++; + + errno =0 ; + val =strtoul (value, &suffix,10 ); +if ( (errno && val ==ULONG_MAX ) || value == suffix ) + { +fprintf (stderr,"Could not parse number \"%s\"\n" , value); +return -1 ; + } + +if (strncasecmp (param,"act-window" ,strlen (param)) ==0 ) + { + ret =parse_activity_window (set_hwp, val, suffix); +if (ret) +return -1 ; + +continue ; + } + +if ( val >255 ) + { +fprintf (stderr,"\"%s\" value \"%lu\" is out of range\n" , param, + val); +return -1 ; + } + +if ( suffix && suffix[0 ] ) + { +fprintf (stderr,"Suffix \"%s\" is invalid\n" , suffix); +return -1 ; + } + +if (strncasecmp (param,"minimum" ,MAX (2 ,strlen (param))) ==0 ) + { + set_hwp->minimum = val; + set_hwp->set_params |=XEN_SYSCTL_HWP_SET_MINIMUM ; + } +else if (strncasecmp (param,"maximum" ,MAX (2 ,strlen (param))) ==0 ) + { + set_hwp->maximum = val; + set_hwp->set_params |=XEN_SYSCTL_HWP_SET_MAXIMUM ; + } +else if (strncasecmp (param,"desired" ,strlen (param)) ==0 ) + { + set_hwp->desired = val; + set_hwp->set_params |=XEN_SYSCTL_HWP_SET_DESIRED ; + } +else if (strncasecmp (param,"energy-perf" ,strlen (param)) ==0 ) + { + set_hwp->energy_perf = val; + set_hwp->set_params |=XEN_SYSCTL_HWP_SET_ENERGY_PERF ; + } +else + { +fprintf (stderr,"\"%s\" is an invalid parameter\n" , param); +return -1 ; + } + } + +if ( set_hwp->set_params ==0 ) + { +fprintf (stderr,"No parameters set in request\n" ); +return -1 ; + } + +return 0 ; +} + +static void hwp_set_func (int argc,char *argv[]) +{ +xc_set_hwp_para_t set_hwp = {}; +int cpuid =-1 ; +int i =0 ; + +if (parse_hwp_opts (&set_hwp, &cpuid, argc, argv) ) +exit (EINVAL ); + +if ( cpuid !=-1 ) + { + i = cpuid; + max_cpu_nr = i +1 ; + } + +for ( ; i < max_cpu_nr; i++ ) +if (xc_set_cpufreq_hwp (xc_handle, i, &set_hwp) ) +fprintf (stderr,"[CPU%d] failed to set hwp params (%d - %s)\n" , + i, errno,strerror (errno)); +} +struct {const char *name;void (*function)(int argc,char *argv[]);
@@ -1309,6 +1538,7 @@ struct { { "get-cpufreq-average", cpufreq_func }, { "start", start_gather_func }, { "get-cpufreq-para", cpufreq_para_func }, + { "set-cpufreq-hwp", hwp_set_func }, { "set-scaling-maxfreq", scaling_max_freq_func }, { "set-scaling-minfreq", scaling_min_freq_func }, { "set-scaling-governor", scaling_governor_func },
Signature · 1 line
2.40.0
Re: [PATCH v3 13/14 RESEND] xenpm: Add set-cpufreq-hwp subcommand
tools/misc/xenpm.c void show_help(void) · line 78
Quoted 12 lines · Jason Andryuk
tools/misc/xenpm.c +8
-0@@ -67,6 +68,27 @@ void show_help(void)" set-max-cstate <num>|'unlimited' [<num2>|'unlimited']\n" " set the C-State limitation (<num> >= 0) and\n" " optionally the C-sub-state limitation (<num2> >= 0)\n" +" set-cpufreq-hwp [cpuid] [balance|performance|powersave] <param:val>*\n" +" set Hardware P-State (HWP) parameters\n" +" optionally a preset of one of\n" +" balance|performance|powersave\n" +" an optional list of param:val arguments\n" +" minimum:N lowest ... highest\n" +" maximum:N lowest ... highest\n" +" desired:N lowest ... highest\n"
Personally I consider these three uses of "lowest ... highest" confusing:
It's not clear at all whether they're part of the option or merely mean to express the allowable range for N (which I think they do). Perhaps ...
tools/misc/xenpm.c void show_help(void) · line 81
Quoted 3 lines
tools/misc/xenpm.c +3
-0+" Set explicit performance target.\n" +" non-zero disables auto-HWP mode.\n" +" energy-perf:0-255 (or 0-15)\n"
..., also taking this into account:
" energy-perf:N (0-255 or 0-15)\n"
and then use parentheses as well for the earlier value range explanations (and again below)?
Also up from here you suddenly start having full stops on the lines. I guess you also want to be consistent in your use of capital letters at the start of lines (I didn't go check how consistent pre-existing code is in this regard).
Quoted 27 lines
tools/misc/xenpm.c +23
-0@@ -1299,6 +1321,213 @@ void disable_turbo_mode(int argc, char *argv[]) errno, strerror(errno)); } +/* +* Parse activity_window:NNN{us,ms,s} and validate range. +* +* Activity window is a 7bit mantissa (0-127) with a 3bit exponent (0-7) base +* 10 in microseconds. So the range is 1 microsecond to 1270 seconds. A value +* of 0 lets the hardware autonomously select the window. +* +* Return 0 on success +* -1 on error +*/ +static int parse_activity_window (xc_set_hwp_para_t *set_hwp,unsigned long u, +const char *suffix) +{ +unsigned int exponent =0 ; +unsigned int multiplier =1 ; + +if ( suffix && suffix[0 ] ) + { +if (strcasecmp (suffix,"s" ) ==0 ) + { + multiplier =1000 *1000 ; + exponent =6 ; + }
tools/misc/xenpm.c void disable_turbo_mode(int argc, char *argv[]) · line 1356
Quoted 10 lines
tools/misc/xenpm.c +10
-0+else if (strcasecmp (suffix,"ms" ) ==0 ) + { + multiplier =1000 ; + exponent =3 ; + } +else if (strcasecmp (suffix,"us" ) ==0 ) + { + multiplier =1 ; + exponent =0 ; + }
Considering the initializers, this "else if" body isn't really needed, and ...
Review void disable_turbo_mode(int argc, char *argv[]) · line 1357
Quoted 1 line
(quoted diff) +1
-0+ else
... instead this could become "else if ( strcmp() != 0 )".
Note also that I use strcmp() there - none of s, ms, or us are commonly expressed by capital letters. (I wonder though whether μs shouldn't also be recognized.)
Quoted 16 lines
tools/misc/xenpm.c +16
-0+ { +fprintf (stderr,"invalid activity window units: \"%s\"\n" , suffix); + +return -1 ; + } + } + +/* u * multipler > 1270 * 1000 * 1000 transformed to avoid overflow. */ +if ( u >1270 *1000 *1000 / multiplier ) + { +fprintf (stderr,"activity window is too large\n" ); + +return -1 ; + } + +/* looking for 7 bits of mantissa and 3 bits of exponent */
tools/misc/xenpm.c void disable_turbo_mode(int argc, char *argv[]) · line 1383
Quoted 10 lines
tools/misc/xenpm.c +10
-0+while ( u >127 ) + { + u +=5 ;/* Round up to mitigate truncation rounding down +e.g. 128 -> 120 vs 128 -> 130. */ + u /=10 ; + exponent +=1 ; + } + + set_hwp->activity_window = (exponent &HWP_ACT_WINDOW_EXPONENT_MASK ) << + HWP_ACT_WINDOW_EXPONENT_SHIFT |
The shift wants parenthesizing against the | and the shift amount wants indenting slightly less. (Really this would want to be MASK_INSR().)
Quoted 10 lines
tools/misc/xenpm.c +10
-0+ (u &HWP_ACT_WINDOW_MANTISSA_MASK ); + set_hwp->set_params |=XEN_SYSCTL_HWP_SET_ACT_WINDOW ; + +return 0 ; +} + +static int parse_hwp_opts (xc_set_hwp_para_t *set_hwp,int *cpuid, +int argc,char *argv[]) +{ +int i =0 ;
tools/misc/xenpm.c void disable_turbo_mode(int argc, char *argv[]) · line 1403
Quoted 10 lines
tools/misc/xenpm.c +10
-0+ +if ( argc <1 ) { +fprintf (stderr,"Missing arguments\n" ); +return -1 ; + } + +if (parse_cpuid_non_fatal (argv[i], cpuid) ==0 ) + { + i++; + }
I don't think you need the earlier patch and the separate helper:
Whether a CPU number is present can be told by checking isdigit(argv[i][0]).
Also (nit) note how you're mixing brace placement throughout this function.
Jan
Re: [PATCH v3 13/14 RESEND] xenpm: Add set-cpufreq-hwp subcommand
Quoted 11 lines · Jan Beulich
Quoted 10 lines · Jason Andryuk
tools/misc/xenpm.c +10
-0+static int parse_hwp_opts (xc_set_hwp_para_t *set_hwp,int *cpuid, +int argc,char *argv[]) +{ +int i =0 ; + +if ( argc <1 ) { +fprintf (stderr,"Missing arguments\n" ); +return -1 ; + } +
Quoted 8 lines
tools/misc/xenpm.c void disable_turbo_mode(int argc, char *argv[]) · line 1403
Quoted 4 lines
tools/misc/xenpm.c +4
-0+if (parse_cpuid_non_fatal (argv[i], cpuid) ==0 ) + { + i++; + }I don't think you need the earlier patch and the separate helper:
Whether a CPU number is present can be told by checkingisdigit(argv[i][0]).
Hmm, yes, there is "all", but your help text doesn't mention it and since you're handling a variable number of arguments anyway, there's not need for anyone to say "all" - they can simply omit the optional argument.
Jan
Re: [PATCH v3 13/14 RESEND] xenpm: Add set-cpufreq-hwp subcommand
In reply to Jan BeulichQuoted 23 lines · Jan Beulich
tools/misc/xenpm.c void show_help(void) · line 78
Quoted 12 lines · Jason Andryuk
tools/misc/xenpm.c +8
-0@@ -67,6 +68,27 @@ void show_help(void)" set-max-cstate <num>|'unlimited' [<num2>|'unlimited']\n" " set the C-State limitation (<num> >= 0) and\n" " optionally the C-sub-state limitation (<num2> >= 0)\n" +" set-cpufreq-hwp [cpuid] [balance|performance|powersave] <param:val>*\n" +" set Hardware P-State (HWP) parameters\n" +" optionally a preset of one of\n" +" balance|performance|powersave\n" +" an optional list of param:val arguments\n" +" minimum:N lowest ... highest\n" +" maximum:N lowest ... highest\n" +" desired:N lowest ... highest\n" Personally I consider these three uses of "lowest ... highest" confusing:
It's not clear at all whether they're part of the option or merely mean to express the allowable range for N (which I think they do). Perhaps ...tools/misc/xenpm.c void show_help(void) · line 81
Quoted 3 lines
tools/misc/xenpm.c +3
-0+" Set explicit performance target.\n" +" non-zero disables auto-HWP mode.\n" +" energy-perf:0-255 (or 0-15)\n"
Quoted 6 lines
..., also taking this into account:
" energy-perf:N (0-255 or 0-15)\n"
and then use parentheses as well for the earlier value range explanations (and again below)?
lowest and highest were supposed to reference the values from xenpm get-cpufreq-para. You removed some later lines that state "get-cpufreq-para returns lowest/highest". However, they aren't enforced limits. You can program from the range 0-255 and the hardware is supposed to clip internally, so your idea of "energy-perf:N (0-255)" seems good to me.
Quoted 4 lines
Also up from here you suddenly start having full stops on the lines. I guess you also want to be consistent in your use of capital letters at the start of lines (I didn't go check how consistent pre-existing code is in this regard).
Looks like the existing code is consistently non-capital letters, but the full stops are inconsistent. I'll go with non-capital and full stop for this addition.
Quoted 41 lines
Quoted 27 lines
tools/misc/xenpm.c +23
-0@@ -1299,6 +1321,213 @@ void disable_turbo_mode(int argc, char *argv[]) errno, strerror(errno)); } +/* +* Parse activity_window:NNN{us,ms,s} and validate range. +* +* Activity window is a 7bit mantissa (0-127) with a 3bit exponent (0-7) base +* 10 in microseconds. So the range is 1 microsecond to 1270 seconds. A value +* of 0 lets the hardware autonomously select the window. +* +* Return 0 on success +* -1 on error +*/ +static int parse_activity_window (xc_set_hwp_para_t *set_hwp,unsigned long u, +const char *suffix) +{ +unsigned int exponent =0 ; +unsigned int multiplier =1 ; + +if ( suffix && suffix[0 ] ) + { +if (strcasecmp (suffix,"s" ) ==0 ) + { + multiplier =1000 *1000 ; + exponent =6 ; + }tools/misc/xenpm.c void disable_turbo_mode(int argc, char *argv[]) · line 1356
Quoted 10 lines
tools/misc/xenpm.c +10
-0+else if (strcasecmp (suffix,"ms" ) ==0 ) + { + multiplier =1000 ; + exponent =3 ; + } +else if (strcasecmp (suffix,"us" ) ==0 ) + { + multiplier =1 ; + exponent =0 ; + }Considering the initializers, this "else if" body isn't really needed, and ...
Quoted 6 lines
Review void disable_turbo_mode(int argc, char *argv[]) · line 1357
Quoted 1 line
(quoted diff) +1
-0+ else... instead this could become "else if (
strcmp()!= 0 )".Note also that I use
strcmp()there - none of s, ms, or us are commonly expressed by capital letters.
That sounds fine.
Quoted 2 lines
(I wonder though whether μs shouldn't also
be recognized.)
While that makes sense, I do not plan to change it. I don't know the proper way to deal with unicode from C. (I suppose a memcmp with the UTF-8 encoding would be possible, but I don't know if there are corner cases I'm overlooking.)
Quoted 21 lines
Quoted 21 lines
tools/misc/xenpm.c +21
-0+ { +fprintf (stderr,"invalid activity window units: \"%s\"\n" , suffix); + +return -1 ; + } + } + +/* u * multipler > 1270 * 1000 * 1000 transformed to avoid overflow. */ +if ( u >1270 *1000 *1000 / multiplier ) + { +fprintf (stderr,"activity window is too large\n" ); + +return -1 ; + } + +/* looking for 7 bits of mantissa and 3 bits of exponent */ +while ( u >127 ) + { + u +=5 ;/* Round up to mitigate truncation rounding down +e.g. 128 -> 120 vs 128 -> 130. */ + u /=10 ;
Quoted 8 lines
tools/misc/xenpm.c void disable_turbo_mode(int argc, char *argv[]) · line 1383
Quoted 5 lines
tools/misc/xenpm.c +5
-0+ exponent +=1 ; + } + + set_hwp->activity_window = (exponent &HWP_ACT_WINDOW_EXPONENT_MASK ) << + HWP_ACT_WINDOW_EXPONENT_SHIFT |The shift wants parenthesizing against the | and the shift amount wants indenting slightly less. (Really this would want to be
MASK_INSR().)
I'll use MASK_INSR.
Quoted 25 lines
Quoted 10 lines
tools/misc/xenpm.c +10
-0+ (u &HWP_ACT_WINDOW_MANTISSA_MASK ); + set_hwp->set_params |=XEN_SYSCTL_HWP_SET_ACT_WINDOW ; + +return 0 ; +} + +static int parse_hwp_opts (xc_set_hwp_para_t *set_hwp,int *cpuid, +int argc,char *argv[]) +{ +int i =0 ;tools/misc/xenpm.c void disable_turbo_mode(int argc, char *argv[]) · line 1403
Quoted 10 lines
tools/misc/xenpm.c +10
-0+ +if ( argc <1 ) { +fprintf (stderr,"Missing arguments\n" ); +return -1 ; + } + +if (parse_cpuid_non_fatal (argv[i], cpuid) ==0 ) + { + i++; + }I don't think you need the earlier patch and the separate helper:
Whether a CPU number is present can be told by checkingisdigit(argv[i][0]).
Quoted 4 lines
Hmm, yes, there is "all", but your help text doesn't mention it and since you're handling a variable number of arguments anyway, there's not need for anyone to say "all" - they can simply omit the optional argument.
Most xenpm commands take "all" or a numeric cpuid, so I intended to be consistent with them. That was the whole point of parse_cpuid_non_fatal() - to reuse the existing parsing code for consistency.
I didn't read the other help text carefully enough to see that the numeric cpuid and "all" handling was repeated.
For consistency, I would retain parse_cpuid_non_fatal() and expand the help text. If you don't want that, I'll switch to isdigit(argv[i][0]) and have the omission of a digit indicate all CPUs as you suggest. Just let me know what you want.
Quoted 2 lines
Also (nit) note how you're mixing brace placement throughout this function.
Will fix.
Regards,
Jason
Re: [PATCH v3 13/14 RESEND] xenpm: Add set-cpufreq-hwp subcommand
Quoted 31 lines · Jason Andryuk
Quoted 20 lines · Jan Beulich
Quoted 4 lines · Jason Andryuk
tools/misc/xenpm.c +4
-0+static int parse_hwp_opts (xc_set_hwp_para_t *set_hwp,int *cpuid, +int argc,char *argv[]) +{ +int i =0 ;tools/misc/xenpm.c void disable_turbo_mode(int argc, char *argv[]) · line 1403
Quoted 10 lines
tools/misc/xenpm.c +10
-0+ +if ( argc <1 ) { +fprintf (stderr,"Missing arguments\n" ); +return -1 ; + } + +if (parse_cpuid_non_fatal (argv[i], cpuid) ==0 ) + { + i++; + }I don't think you need the earlier patch and the separate helper:
Whether a CPU number is present can be told by checkingisdigit(argv[i][0]).Quoted 4 lines
Hmm, yes, there is "all", but your help text doesn't mention it and since you're handling a variable number of arguments anyway, there's not need for anyone to say "all" - they can simply omit the optional argument.
Most xenpm commands take "all" or a numeric cpuid, so I intended to be consistent with them. That was the whole point of
parse_cpuid_non_fatal()- to reuse the existing parsing code for consistency.
Quoted 7 lines
I didn't read the other help text carefully enough to see that the numeric cpuid and "all" handling was repeated.
For consistency, I would retain
parse_cpuid_non_fatal()and expand the help text. If you don't want that, I'll switch toisdigit(argv[i][0])and have the omission of a digit indicate all CPUs as you suggest. Just let me know what you want.
While I don't want to push you towards something you don't like yourself, my view on the "all" has been "Why did they introduce that?" It makes some sense when it's a placeholder to avoid needing to deal with a variable number of arguments, but already that doesn't apply to all the pre-existing operations. Note how many functions already have
if ( argc > 0 )
parse_cpuid(argv[0], &cpuid);and {en,dis}able-turbo-mode don't properly mention "all" in their help text either.
Jan
PATCH RESEND v3 14/14 CHANGELOG: Add Intel HWP entry
In reply to Jason Andryuk---
v3:
Position under existing Added section
Add Henry's Ack
v2:
Add blank line
--- CHANGELOG.md | 1 + 1 file changed, 1 insertion(+)
CHANGELOG.md +1 -0
@@ -18,6 +18,7 @@ The format is based on [Keep a Changelog](https://keepachangelog.com/en/1.0.0/) - Bus-lock detection, used by Xen to mitigate (by rate-limiting) the system wide impact of a guest misusing atomic instructions. - xl/libxl can customize SMBIOS strings for HVM guests. + - Add Intel Hardware P-States (HWP) cpufreq driver. ## [4.17.0](https://xenbits.xen.org/gitweb/?p=xen.git;a=shortlog;h=RELEASE-4.17.0) - 2022-12-12
Signature · 1 line
2.40.0