xref: /aosp_15_r20/external/ltp/testcases/kernel/power_management/README (revision 49cdfc7efb34551c7342be41a7384b9c40d7cab7)

################################################################################
##                                                                            ##
## Copyright (c) International Business Machines  Corp., 2007                 ##
##                                                                            ##
## This program is free software;  you can redistribute it and#or modify      ##
## it under the terms of the GNU General Public License as published by       ##
## the Free Software Foundation; either version 2 of the License, or          ##
## (at your option) any later version.                                        ##
##                                                                            ##
## This program is distributed in the hope that it will be useful, but        ##
## WITHOUT ANY WARRANTY; without even the implied warranty of MERCHANTABILITY ##
## or FITNESS FOR A PARTICULAR PURPOSE.  See the GNU General Public License   ##
## for more details.                                                          ##
##                                                                            ##
## You should have received a copy of the GNU General Public License          ##
## along with this program;  if not, write to the Free Software               ##
## Foundation, Inc., 51 Franklin Street, Fifth Floor, Boston, MA 02110-1301 USA    ##
##                                                                            ##
################################################################################

POWER MANAGEMENT TESTS AUTOMATION SUITE
----------------------------------------
The tests requires the Kernel to  be compiled with the following config's

for CPU FREQUENCY tests:

CONFIG_CPU_FREQ
CONFIG_CPU_FREQ_TABLE
CONFIG_CPU_FREQ_DEBUG
CONFIG_CPU_FREQ_STAT
CONFIG_CPU_FREQ_STAT_DETAILS
CONFIG_CPU_FREQ_DEFAULT_GOV_*
CONFIG_CPU_FREQ_GOV_*

for CPU IDLE tests:

CONFIG_CPU_IDLE
CONFIG_CPU_IDLE_GOV_LADDER
CONFIG_CPU_IDLE_GOV_MENU

for SCHED_MC tests:

CONFIG_SCHED_MC

The power management test automation suite helps run the power management functionality
(e.g: cpu frequency, cpu idle etc..) tests and report results.

Test Scripts for CPU FREQUENCY:
change_freq.sh
change_govr.sh
check_cpufreq_sysfs_files.sh

Test Scripts for CPU IDLE:
will be added soon

Test Scripts for SCHED_MC:
test_sched_mc.sh

Common functionality:
pm_include.sh
check_kv_arch.c
pwkm_load_unload.sh

To run your tests you can execute the runpwtests.sh

To run the tests individually :

P.S. As of now the supporting architecture(s) are x86,x86_64

Support of system:
-----------------
If you see some thing like following,

Power Management    1  FAIL  :  Required kernel configuration for SCHED_MC NOT set
or
Power Management    1  FAIL  :  Required kernel configuration for CPU_FREQ NOT set

Then either configuration is not set or the system won't support.

For CPU consolidation verification ebizzy is included in utils directory of LTP.
To run cpu consolidation test user has to provide -w <workload> -l <sched_mc_level>.
Refer to README in LTPROOT/utils/benchmark/ebizzy-0.2 directory for details of ebizzy.

To test CPU consolidation for sched_mc 2 kernbench has to run. Kernbench needs linux kernel source as input in /root directory . For example download from http://www.kernel.org/pub/linux/kernel/v2.6/linux-2.6.29.4.tar.bz2. If Linux kernel source not found kernbench wiil  not execute.
CPU consolidation testcases will not execute if number of CPU's in package is less then 2. If system is hyper threaded but number of CPU is 1 only sched_smt testcases will be excuted. For better coverage of testcases select a system which is at least quad core and then hyper threaded so that you will observe 8 CPU's in each package.

Timer migration interface test will execute on kernel versions 2.6.31 and above. Timer migration functionality verification testcases will be executed only on suitable architecture like quad core or the number of CPU's in each package should be at least 4 and above