[PATCH 00/11] CPU frequency test improvements

Colin Ian King colin.king at canonical.com
Tue May 26 09:39:05 UTC 2015


On 26/05/15 09:56, Colin Ian King wrote:
> On 21/05/15 10:34, Jeremy Kerr wrote:
>> These changes rework the CPU frequency tests, mainly for compatiblity with
>> non-x86 machines.
>>
>> Patches 1-6 factor out the tests into smaller units, so that we can
>> selectively enable or disable functionality that's specific to ACPI-based
>> frequency control, and do a little rework to have a consistent 1 pass/fail
>> per test run.
>>
>> Patch 7 is a simple check for the consistency of frequency changes.
>>
>> Patches 8-10 implement Linux perf support for the test benchmarks, so
>> that we have meaningful results in the benchmark sets, across different
>> platforms.
> 
> The perf feature is an improvement, however, fwts does run on a variety
> of kernels, so perf may not be enabled.  Can we keep the older bogo ops
> code for systems that don't have perf enabled?

My mistake, I just seen that it does this. Nice one :-)

Colin

> 
>>
>> Patch 11 makes the tests a little more usable on large machines.
>>
>> Questions / comments most welcome.
>>
>> Cheers,
>>
>> Jeremy
>>
>> ---
>> Jeremy Kerr (11):
>>       cpu/cpufreq: Don't reparse cpu information
>>       cpu/cpufreq: hz_almost_equal is unused if !FWTS_ARCH_INTEL
>>       cpu/cpufreq: Add a separate cpufreq consistency test
>>       cpu/cpufreq: Add test for duplicate entries in cpufreq tables
>>       cpu/cpufreq: Do bios limit and claimed max checks as separate tests
>>       cpu/cpufreq: Refactor CPU performance tests
>>       cpu/cpufreq: Always check that cpufreq changes have taken
>>       fwts: Use linux perf counters for cpu benchmarking
>>       fwts: Use gettimeofday for cpu benchmark
>>       fwts: scale cpu benchmark results to one second
>>       cpu/cpufreq: Only run performance tests on master threads
>>
>>
> 




More information about the fwts-devel mailing list