Changes in config

1e2c4499 - selftests/cpufreq: Don't enable generic lock debugging options

Tue, 06 Jun 2023 14:11:49 +0000

selftests/cpufreq: Don't enable generic lock debugging optionsCurrently the the config fragment for cpufreq enables a lot of genericlock debugging. While these options are useful when testing cpufreqthey aren't actually required to run the tests and are therefore out ofscope for the cpufreq fragement, they are more of a thing that it's goodto enable while doing testing than an actual requirement for cpufreqtesting specifically. Having these debugging options enabled,especially the mutex and spinlock instrumentation, mean that any buildthat includes the cpufreq fragment is both very much larger than astandard defconfig (eg, I'm seeing 35% on x86_64) and also slower atruntime.This is causing real problems for CI systems. In order to avoidbuilding large numbers of kernels they try to group kselftest fragmentstogether, frequently just grouping all the kselftest fragments into asingle block. The increased size is an issue for memory constrainedsystems and is also problematic for systems with fixed storageallocations for kernel images (eg, typical u-boot systems) where itfrequently causes the kernel to overflow the storage space allocated forkernels. The reduced performance isn't too bad with real hardware butcan be disruptive on emulated platforms.In order to avoid these issues remove these generic instrumentationoptions from the cpufreq fragment, bringing the cpufreq fragment intoline with other fragments which generally set requirements for testingrather than nice to haves.Signed-off-by: Mark Brown Acked-by: Viresh Kumar Signed-off-by: Shuah Khan List of files: /linux-6.15/tools/testing/selftests/cpufreq/config

67d6d80d - selftests/cpufreq: Rename DEBUG_PI_LIST to DEBUG_PLIST

Tue, 31 Aug 2021 10:23:16 +0000

selftests/cpufreq: Rename DEBUG_PI_LIST to DEBUG_PLISTDEBUG_PI_LIST was renamed to DEBUG_PLIST since8e18faeac3 ("lib/plist: rename DEBUG_PI_LIST to DEBUG_PLIST")- It's not reasonable to keep the deprecated configs.- configs under kselftests are recommended by corresponding tests.So if some configs are missing, it will impact the testing resultsCC: "Rafael J. Wysocki" CC: Viresh Kumar CC: linux-pm@vger.kernel.orgSigned-off-by: Li Zhijian Acked-by: Viresh Kumar Signed-off-by: Shuah Khan List of files: /linux-6.15/tools/testing/selftests/cpufreq/config

83896c68 - selftests: create cpufreq kconfig fragments

Wed, 26 Apr 2017 10:09:37 +0000

selftests: create cpufreq kconfig fragmentsFor the better test coverage of cpufreq driver code these extraconfigurations are needed. Enable cpufreq governors and stats.Signed-off-by: Naresh Kamboju Acked-by: Viresh Kumar Signed-off-by: Shuah Khan List of files: /linux-6.15/tools/testing/selftests/cpufreq/config