On 04/21/2016 08:53 AM, Alexey Klimov wrote:
>
> On Tue, Apr 19, 2016 at 1:11 AM, Al Stone <ahs3@xxxxxxxxxx> wrote:
>>
>> When CPPC is being used by ACPI on arm64, user space tools such as
>> cpupower report CPU frequency values from sysfs that are incorrect.
>>
>> What the driver was doing was reporting the values given by ACPI tables
>> in whatever scale was used to provide them. However, the ACPI spec
>> defines the CPPC values as unitless abstract numbers. Internal kernel
>> structures such as struct perf_cap, in contrast, expect these values
>> to be in KHz. When these struct values get reported via sysfs, the
>> user space tools also assume they are in KHz, causing them to report
>> incorrect values (for example, reporting a CPU frequency of 1MHz when
>> it should be 1.8GHz).
>>
>> While the investigation for a long term fix proceeds (several options
>> are being explored, some of which may require spec changes or other
>> much more invasive fixes), this patch forces the values read by CPPC
>> to be read in KHz, regardless of what they actually represent.
>>
>> The downside is that this approach has some assumptions:
>>
>> (1) It relies on SMBIOS3 being used, *and* that the Max Frequency
>> value for a processor is set to a non-zero value.
>>
>> (2) It assumes that all processors run at the same speed. This
>
> Sometimes short-term solution becomes long-term. It's worth to place
> comment in code about this assumption.
True. I'll add a comment. Thanks.
>> patch retrieves the first CPU Max Frequency from a type 4 DMI
>> record that it can find. This may not be an issue, however, as a
>> sampling of DMI data on x86 and arm64 indicates there is often only
>> one such record regardless.
>>
>> For arm64 servers, this may be sufficient, but it does rely on
>> firmware values being set correctly. Hence, other approaches are
>> also being considered.
>>
>> This has been tested on three arm64 servers, with and without DMI, with
>> and without CPPC support.
>>
>> Changes for v2:
>> -- Corrected thinko: needed to have DEPENDS on DMI in Kconfig.arm,
>> not SELECT DMI (found by build daemon)
>>
>> Signed-off-by: Al Stone <ahs3@xxxxxxxxxx>
>> ---
>> drivers/acpi/cppc_acpi.c | 61 +++++++++++++++++++++++++++++++++++++++++----
>> drivers/cpufreq/Kconfig.arm | 1 +
>> 2 files changed, 57 insertions(+), 5 deletions(-)
>>
>> diff --git a/drivers/acpi/cppc_acpi.c b/drivers/acpi/cppc_acpi.c
>> index 8adac69..d61ced6 100644
>> --- a/drivers/acpi/cppc_acpi.c
>> +++ b/drivers/acpi/cppc_acpi.c
>> @@ -40,6 +40,9 @@
>> #include <linux/cpufreq.h>
>> #include <linux/delay.h>
>> #include <linux/ktime.h>
>> +#include <linux/dmi.h>
>> +
>> +#include <asm/unaligned.h>
>>
>> #include <acpi/cppc_acpi.h>
>> /*
>> @@ -709,6 +712,47 @@ static int cpc_write(struct cpc_reg *reg, u64 val)
>> return ret_val;
>> }
>>
>> +static u64 cppc_dmi_khz;
>> +
>> +static void cppc_find_dmi_mhz(const struct dmi_header *dm, void *private)
>> +{
>> + u16 *mhz = (u16 *)private;
>> + const u8 *dmi_data = (const u8 *)dm;
>> +
>> + if (dm->type == DMI_ENTRY_PROCESSOR && dm->length >= 48)
>> + *mhz = (u16)get_unaligned((const u16 *)(dmi_data + 0x14));
>> +}
>> +
>> +
>> +static u64 cppc_get_dmi_khz(void)
>> +{
>> + u16 mhz;
>> +
>> + dmi_walk(cppc_find_dmi_mhz, &mhz);
>> +
>> + /*
>> + * Real stupid fallback value, just in case there is no
>> + * actual value set.
>> + */
>> + mhz = mhz ? mhz : 1;
>> +
>> + return (1000 * mhz);
>> +}
>> +
>> +static u64 cppc_unitless_to_khz(u64 min, u64 max, u64 val)
>> +{
>> + /*
>> + * The incoming val should be min <= val <= max. Our
>> + * job is to convert that to KHz so it can be properly
>> + * reported to user space via cpufreq_policy.
>> + */
>> +
>> + if (!cppc_dmi_khz)
>> + cppc_dmi_khz = cppc_get_dmi_khz();
>> +
>> + return ((val - min) * cppc_dmi_khz) / (max - min);
>
> How pedantic should the kernel be while dealing with this values?
I'm not sure it can be. By definition, the CPPC values define an abstract
range. We are only associating it with a frequency here because those are
the units assumed elsewhere in the kernel, and that user space tools make the
same assumptions. What I'm looking at for the longer term is possibly breaking
those assumptions so that maybe we can be pedantic.
> This 1) can potentially divide by zero (extra care is required to
> perform this in Solar System) and 2) can return 0.
Hrm. I'll double check the path for divide by zero; I thought that was covered
elsewhere along the path but I might have missed it.
A zero in this case would mean the processor is running at its lowest possible
level of performance, and is an artifact of mapping the CPPC abstract value
onto a linear scale from 0 to max KHz. Granted, that may not be exactly the
same as 0 KHz; I'm open to suggestions here. If there's a relatively
straightforward way to get a processor's minimum operating frequency (apart
from completely off), we could eliminate the zero.
> Not sure if there is some benefit for firmware to export such
> values.
Reporting a divide by zero would be bad and should not happen; a value
of zero, though, could be argued. Since we're using a linear scale from
zero to max KHz, it's not unexpected. That being said, though, the only
reason for this patch is so that user space does not report completely
incorrect values; we were seeing MHz values reported by cpupower when
they should have been GHz, for example.
--
ciao,
al
-----------------------------------
Al Stone
Software Engineer
Red Hat, Inc.
ahs3@xxxxxxxxxx
-----------------------------------
--
To unsubscribe from this list: send the line "unsubscribe linux-acpi" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
