/linux/drivers/thermal/testing/ |
H A D | command.c | 7 * Thermal subsystem testing facility. 12 * It resides in the "thermal-testing" directory under the debugfs root and 14 * representing a thermal testing facility command. 21 * # echo addtz > /sys/kernel/debug/thermal-testing/command 23 * That template will be represented as a subdirectory in the "thermal-testing" 26 * # ls /sys/kernel/debug/thermal-testing/ 32 * # echo tzaddtrip:0 > /sys/kernel/debug/thermal-testing/command 35 * template 0 (represented by the tz0 subdirectory in "thermal-testing"). 37 * # ls /sys/kernel/debug/thermal-testing/tz0 46 * writing to the "init_temp" file in its directory under "thermal-testing", for [all …]
|
/linux/Documentation/dev-tools/kunit/ |
H A D | index.rst | 4 KUnit - Linux Kernel Unit Testing 21 This section details the kernel unit testing framework. 26 KUnit (Kernel unit testing framework) provides a common framework for 33 (C++ unit testing framework). 42 KUnit follows the white-box testing approach. The test has access to 46 In addition, KUnit has kunit_tool, a script (``tools/testing/kunit/kunit.py``) 65 Unit Testing 69 granularity of testing and allows all possible code paths to be tested in the 88 Unit Testing Advantages 91 - Increases testing speed and development in the long run. [all …]
|
H A D | faq.rst | 9 KUnit is a unit testing framework. Autotest, kselftest (and some others) are 14 test should be the finest granularity of testing and should allow all possible 19 There are no testing frameworks currently available for the kernel that do not 21 testing frameworks require tests to be written in userspace and run on the 23 disqualifying any of them from being considered unit testing frameworks. 34 (``tools/testing/kunit/kunit.py``) that might not support some architectures 50 test should be the finest granularity of testing and, as such, allows all 73 1. Run ``./tools/testing/kunit/kunit.py run`` with the ``--raw_output``
|
H A D | architecture.rst | 9 - `In-Kernel Testing Framework`_ 12 In-Kernel Testing Framework 15 The kernel testing library supports KUnit tests written in C using 114 In the event of a failure, the testing flow differs as follows: 159 ``kunit_tool`` is a Python script, found in ``tools/testing/kunit/kunit.py``. It 170 (for example, ``tools/testing/kunit/qemu configs/powerpc.py``) contains 180 ``./tools/testing/kunit/kunit.py config`` and 186 ``build`` argument: ``./tools/testing/kunit/kunit.py build``. 193 argument: ``./tools/testing/kunit/kunit.py exec``.
|
H A D | start.rst | 24 ./tools/testing/kunit/kunit.py run 77 tools/testing/kunit/kunit.py config 99 ./tools/testing/kunit/kunit.py run \ 105 ./tools/testing/kunit/kunit.py run \ 135 ./tools/testing/kunit/kunit.py run "kunit_executor_test" 140 ./tools/testing/kunit/kunit.py run "example.example_simple_test" 146 ./tools/testing/kunit/kunit.py run "*.*64*" 164 option (under Kernel Hacking/Kernel Testing and Coverage in 284 ./tools/testing/kunit/kunit.py run 309 for testing different things), see Documentation/dev-tools/kunit/usage.rst
|
H A D | running_tips.rst | 18 ( cd "$(git rev-parse --show-toplevel)" && ./tools/testing/kunit/kunit.py run "$@" ) 36 $ ./tools/testing/kunit/kunit.py run 'sysctl*' 43 $ ./tools/testing/kunit/kunit.py run 'sysctl*.*write*' 64 $ ./tools/testing/kunit/kunit.py run --kunitconfig=lib/kunit/.kunitconfig 71 $ ./tools/testing/kunit/kunit.py run --kunitconfig=lib/kunit 97 $ ./tools/testing/kunit/kunit.py run --kernel_args=param=42 --kernel_args=param2=false 126 …$ ./tools/testing/kunit/kunit.py run --kunitconfig=.kunit/ --kunitconfig=tools/testing/kunit/confi… 139 $ ./tools/testing/kunit/kunit.py run --make_options=CC=/usr/bin/gcc-6 147 …$ ./tools/testing/kunit/kunit.py run --make_options LLVM=1 --kunitconfig=.kunit/ --kunitconfig=too… 162 the kernel, run the ``./linux`` binary), this section will focus on testing [all …]
|
/linux/tools/testing/selftests/mount_setattr/ |
H A D | mount_setattr_test.c | 380 ASSERT_EQ(mount("testing", "/tmp", "tmpfs", MS_NOATIME | MS_NODEV, in FIXTURE_SETUP() 385 ASSERT_EQ(mount("testing", "/tmp/B", "tmpfs", MS_NOATIME | MS_NODEV, in FIXTURE_SETUP() 394 ASSERT_EQ(mount("testing", "/tmp/B/BB", "tmpfs", MS_NOATIME | MS_NODEV, in FIXTURE_SETUP() 397 ASSERT_EQ(mount("testing", "/mnt", "tmpfs", MS_NOATIME | MS_NODEV, in FIXTURE_SETUP() 402 ASSERT_EQ(mount("testing", "/mnt/A", "tmpfs", MS_NOATIME | MS_NODEV, in FIXTURE_SETUP() 411 ASSERT_EQ(mount("testing", "/mnt/B", "ramfs", in FIXTURE_SETUP() 416 ASSERT_EQ(mount("testing", "/tmp/B/BB", "devpts", in FIXTURE_SETUP() 1005 ASSERT_EQ(mount("testing", "/tmp", "tmpfs", MS_NOATIME | MS_NODEV, in FIXTURE_SETUP() 1012 ASSERT_EQ(mount("testing", "/tmp/B", "tmpfs", MS_NOATIME | MS_NODEV, in FIXTURE_SETUP() 1019 ASSERT_EQ(mount("testing", "/tmp/B/BB", "tmpfs", MS_NOATIME | MS_NODEV, in FIXTURE_SETUP() [all …]
|
/linux/tools/hv/ |
H A D | vmbus_testing | 7 # 1. delay testing 25 # in /drivers/hv/debugfs.c. All fuzz testing 137 # display Testing status of single device 163 # display Testing state of devices 168 print("Testing = ON for: {}" 171 print("Testing = OFF for: {}" 202 # set testing state of device 208 print("Testing = ON for device: {}" 212 print("Testing = OFF for device: {}" 215 # get testing state of device [all …]
|
/linux/tools/testing/selftests/net/rds/ |
H A D | README.txt | 18 -d Log directory. Defaults to tools/testing/selftests/net/rds/rds_logs 29 tools/testing/selftests/net/rds/config.sh -g 32 tools/testing/selftests/net/rds/config.sh 35 vng --build --config tools/testing/selftests/net/config 39 "export PYTHONPATH=tools/testing/selftests/net/; tools/testing/selftests/net/rds/run.sh" 41 An HTML coverage report will be output in tools/testing/selftests/net/rds/rds_logs/coverage/.
|
/linux/tools/testing/selftests/kvm/s390/ |
H A D | cpumodel_subfuncs_test.c | 54 /* Testing Perform Locked Operation (PLO) CPU subfunction's ASM block */ 63 /* Testing Crypto Compute Message Authentication Code (KMAC) CPU subfunction's ASM block */ 74 /* Testing Crypto Cipher Message with Chaining (KMC) CPU subfunction's ASM block */ 85 /* Testing Crypto Cipher Message (KM) CPU subfunction's ASM block */ 96 /* Testing Crypto Compute Intermediate Message Digest (KIMD) CPU subfunction's ASM block */ 107 /* Testing Crypto Compute Last Message Digest (KLMD) CPU subfunction's ASM block */ 118 /* Testing Crypto Cipher Message with Counter (KMCTR) CPU subfunction's ASM block */ 129 /* Testing Crypto Cipher Message with Cipher Feedback (KMF) CPU subfunction's ASM block */ 140 /* Testing Crypto Cipher Message with Output Feedback (KMO) CPU subfunction's ASM block */ 151 /* Testing Crypto Perform Cryptographic Computation (PCC) CPU subfunction's ASM block */ [all …]
|
/linux/Documentation/bpf/ |
H A D | map_sockmap.rst | 348 - `tools/testing/selftests/bpf/progs/test_sockmap_kern.h`_ 349 - `tools/testing/selftests/bpf/progs/sockmap_parse_prog.c`_ 350 - `tools/testing/selftests/bpf/progs/sockmap_verdict_prog.c`_ 351 - `tools/testing/selftests/bpf/progs/test_sockmap_listen.c`_ 352 - `tools/testing/selftests/bpf/progs/test_sockmap_update.c`_ 439 - `tools/testing/selftests/bpf/prog_tests/sockmap_basic.c`_ 440 - `tools/testing/selftests/bpf/test_sockmap.c`_ 441 - `tools/testing/selftests/bpf/test_maps.c`_ 491 … _`tools/testing/selftests/bpf/progs/test_sockmap_kern.h`: https://git.kernel.org/pub/scm/linux/ke… 492 …_`tools/testing/selftests/bpf/progs/sockmap_parse_prog.c`: https://git.kernel.org/pub/scm/linux/ke… [all …]
|
H A D | s390.rst | 2 Testing BPF on s390 29 testing \ 97 testing \ 122 -C tools/testing/selftests \ 124 INSTALL_PATH=$PWD/tools/testing/selftests/kselftest_install \ 162 cd /linux/tools/testing/selftests/kselftest_install 167 cd /linux/tools/testing/selftests/bpf
|
H A D | prog_lsm.rst | 134 `tools/testing/selftests/bpf/progs/lsm.c`_ and the corresponding 135 userspace code in `tools/testing/selftests/bpf/prog_tests/test_lsm.c`_ 140 .. _tools/testing/selftests/bpf/progs/lsm.c: 141 …https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/tree/tools/testing/selftests/bpf/… 142 .. _tools/testing/selftests/bpf/prog_tests/test_lsm.c: 143 …https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/tree/tools/testing/selftests/bpf/…
|
/linux/tools/testing/selftests/rcutorture/bin/ |
H A D | torture.sh | 16 RCUTORTURE="`pwd`/tools/testing/selftests/rcutorture"; export RCUTORTURE 273 # normal rcutorture testing, but no KASAN or KCSAN testing. 421 amcdir="tools/testing/selftests/rcutorture/res/$ds/allmodconfig" 463 rtfdir="tools/testing/selftests/rcutorture/res/$ds/results-rcutasksflavors" 475 tools/testing/selftests/rcutorture/bin/kvm.sh --datestamp "$ds/results-rcutasksflavors/$flavor" --buildonly --configs "TINY01 TREE04" --kconfig "CONFIG_RCU_EXPERT=y CONFIG_RCU_SCALE_TEST=y CONFIG_KPROBES=n CONFIG_RCU_TRACE=n CONFIG_TRACING=n CONFIG_BLK_DEV_IO_TRACE=n CONFIG_UPROBE_EVENTS=n $forceflavor=y $deselectedflavors" --trust-make > $T/$flavor.out 2>&1 497 torture_set "rcutorture" tools/testing/selftests/rcutorture/bin/kvm.sh --allcpus --duration "$duration_rcutorture" --configs "$configs_rcutorture" --trust-make 503 torture_set "locktorture" tools/testing/selftests/rcutorture/bin/kvm.sh --torture lock --allcpus --duration "$duration_locktorture" --configs "$configs_locktorture" --trust-make 511 torture_set "scftorture" tools/testing/selftests/rcutorture/bin/kvm.sh --torture scf --allcpus --duration "$duration_scftorture" --configs "$configs_scftorture" --kconfig "CONFIG_NR_CPUS=$SCALE_ALLOTED_CPUS" --memory ${scfmem}G --trust-make 516 # In both runs, disable testing o [all...] |
/linux/tools/perf/tests/ |
H A D | pmu-events.c | 283 pr_debug2("testing event e1 %s: mismatched name string, %s vs %s\n", in compare_pmu_events() 289 pr_debug2("testing event e1 %s: mismatched compat string, %s vs %s\n", in compare_pmu_events() 295 pr_debug2("testing event e1 %s: mismatched event, %s vs %s\n", in compare_pmu_events() 301 pr_debug2("testing event e1 %s: mismatched desc, %s vs %s\n", in compare_pmu_events() 307 pr_debug2("testing event e1 %s: mismatched topic, %s vs %s\n", in compare_pmu_events() 313 pr_debug2("testing event e1 %s: mismatched long_desc, %s vs %s\n", in compare_pmu_events() 319 pr_debug2("testing event e1 %s: mismatched pmu string, %s vs %s\n", in compare_pmu_events() 325 pr_debug2("testing event e1 %s: mismatched unit, %s vs %s\n", in compare_pmu_events() 331 pr_debug2("testing event e1 %s: mismatched perpkg, %d vs %d\n", in compare_pmu_events() 337 pr_debug2("testing event e1 %s: mismatched deprecated, %d vs %d\n", in compare_pmu_events() [all …]
|
/linux/tools/testing/selftests/powerpc/mm/ |
H A D | exec_prot.c | 172 printf("Testing read on --x, should fault..."); in test() 184 printf("Testing write on --x, should fault..."); in test() 190 printf("Testing exec on ---, should fault..."); in test() 194 printf("Testing exec on r--, should fault..."); in test() 198 printf("Testing exec on -w-, should fault..."); in test() 202 printf("Testing exec on rw-, should fault..."); in test() 206 printf("Testing exec on --x, should succeed..."); in test() 210 printf("Testing exec on r-x, should succeed..."); in test() 214 printf("Testing exec on -wx, should succeed..."); in test() 218 printf("Testing exec on rwx, should succeed..."); in test()
|
/linux/arch/riscv/kernel/tests/ |
H A D | Kconfig.debug | 2 menu "arch/riscv/kernel Testing and Coverage" 8 bool "arch/riscv/kernel runtime Testing" 11 Enable riscv kernel runtime testing. 39 Enable testing for riscv kprobes. Useful for riscv and/or kprobes 47 endmenu # "arch/riscv/kernel runtime Testing"
|
/linux/Documentation/rust/ |
H A D | testing.rst | 3 Testing title 27 ./tools/testing/kunit/kunit.py run --make_options LLVM=1 --arch x86_64 --kconfig_add CONFIG_RUST=y 32 built-in vs. command line testing. 37 Kernel hacking -> Kernel Testing and Coverage -> KUnit - Enable support for unit tests 73 testing facilities. For instance, the kernel log would look like:: 117 require passing context, unlike those for KUnit testing (i.e. 119 documentation do not need to care about which testing framework is used. In 214 Currently, they are mostly used for testing the ``macros`` crate's examples. 219 Kselftests are also available in the ``tools/testing/selftests/rust`` folder. 222 ``tools/testing/selftests/rust/config`` file and can be included with the aid [all …]
|
/linux/kernel/ |
H A D | backtracetest.c | 18 pr_info("Testing a backtrace from process context.\n"); in backtrace_test_normal() 33 pr_info("Testing a backtrace from BH context.\n"); in backtrace_test_bh() 46 pr_info("Testing a saved backtrace.\n"); in backtrace_test_saved() 61 pr_info("====[ backtrace testing ]===========\n"); in backtrace_regression_test() 67 pr_info("====[ end of backtrace testing ]====\n"); in backtrace_regression_test()
|
/linux/tools/testing/selftests/rcutorture/doc/ |
H A D | rcu-test-image.txt | 5 $ size tools/testing/selftests/rcutorture/initrd/init 7 328 0 8 336 150 tools/testing/selftests/rcutorture/initrd/init 10 some aspect of the rcutorture testing. This will require a more fully 15 tools/testing/selftests/rcutorture/initrd 17 For example, your tools/testing/selftests/rcutorture/initrd/init might 19 scripts need starting to properly monitor or control your testing.
|
/linux/tools/perf/tests/shell/ |
H A D | lock_contention.sh | 49 echo "Testing perf lock record and perf lock contention" 62 echo "Testing perf lock contention --use-bpf" 80 echo "Testing perf lock record and perf lock contention at the same time" 94 echo "Testing perf lock contention --threads" 117 echo "Testing perf lock contention --lock-addr" 140 echo "Testing perf lock contention --lock-cgroup" 158 echo "Testing perf lock contention --type-filter (w/ spinlock)" 180 echo "Testing perf lock contention --lock-filter (w/ tasklist_lock)" 212 echo "Testing perf lock contention --callstack-filter (w/ unix_stream)" 240 echo "Testing perf lock contention --callstack-filter with task aggregation" [all …]
|
/linux/tools/testing/selftests/kvm/ |
H A D | kvm_page_table_test.c | 9 * use hugepages to back the guest memory for testing. 25 /* Default size(1GB) of the memory for testing */ 76 * Guest physical memory offset of the testing memory slot. 83 * Guest virtual memory offset of the testing memory slot. 258 /* Align down GPA of the testing memslot */ in pre_init_before_test() 283 /* Do mapping(GVA->GPA) for the testing memory slot */ in pre_init_before_test() 301 pr_info("Testing guest mode: %s\n", vm_guest_mode_string(mode)); in pre_init_before_test() 302 pr_info("Testing memory backing src type: %s\n", in pre_init_before_test() 304 pr_info("Testing memory backing src granularity: 0x%lx\n", in pre_init_before_test() 306 pr_info("Testing memory size(aligned): 0x%lx\n", test_mem_size); in pre_init_before_test() [all …]
|
/linux/lib/ |
H A D | Kconfig.kfence | 19 Note that, KFENCE is not a substitute for explicit testing with tools 76 int "Stress testing of fault handling and error reporting" if EXPERT 82 and allocations/frees. A value of 0 disables stress testing logic. 84 Only for KFENCE testing; set to 0 if you are not a KFENCE developer. 91 Test suite for KFENCE, testing various error detection scenarios with
|
/linux/tools/testing/selftests/bpf/progs/ |
H A D | xdp_redirect_multi_kern.c | 14 /* One map use devmap, another one use devmap_hash for testing */ 82 /* The following 2 progs are for 2nd devmap prog testing */ in xdp_devmap_prog()
|
/linux/tools/testing/selftests/sysctl/ |
H A D | sysctl.sh | 220 echo "== Testing sysctl behavior against ${TARGET} ==" 308 echo -n "Testing that $1 fails as expected ... " 397 echo -n "Testing INT_MAX works ... " 410 echo -n "Testing INT_MAX + 1 will fail as expected ... " 423 echo -n "Testing negative values will work as expected ... " 439 echo -n "Testing array works as expected ... " 451 echo -n "Testing skipping trailing array elements works ... " 468 echo -n "Testing PAGE_SIZE limit on array works ... " 486 echo -n "Testing exceeding PAGE_SIZE limit fails as expected ... " 507 echo -n "Testing UINT_MAX works ... " [all …]
|