Searched refs:selftests (Results 1 – 25 of 36) sorted by relevance
12
3 # selftests: membarrier: membarrier_test_single_thread8 ok 1 selftests: membarrier: membarrier_test_single_thread9 # selftests: membarrier: membarrier_test_multi_thread14 ok 2 selftests: membarrier: membarrier_test_multi_thread
18 -d Log directory. Defaults to tools/testing/selftests/net/rds/rds_logs29 tools/testing/selftests/net/rds/config.sh -g32 tools/testing/selftests/net/rds/config.sh35 vng --build --config tools/testing/selftests/net/config39 "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/.
16 In this mode the tests are indistinguishable from other selftests and17 (for example) can be run under ``virtme-ng`` like the core networking selftests.46 $ cat tools/testing/selftests/drivers/net/net.config92 Build the selftests::94 # make -C tools/testing/selftests/ TARGETS="drivers/net drivers/net/hw"98 # make -C tools/testing/selftests/ TARGETS="drivers/net drivers/net/hw" \109 # selftests: drivers/net: ping.py116 ok 1 selftests: drivers/net: ping.py
24 % make -C tools/testing/selftests/livepatch32 Test kernel modules are built before running the livepatch selftests. The38 To run the livepatch selftests, from the top of the kernel source tree:40 % make -C tools/testing/selftests TARGETS=livepatch run_tests
496 …torture_set "rcutorture" tools/testing/selftests/rcutorture/bin/kvm.sh --allcpus --duration "$dura…502 …torture_set "locktorture" tools/testing/selftests/rcutorture/bin/kvm.sh --torture lock --allcpus -…572 …tools/testing/selftests/rcutorture/bin/srcu_lockdep.sh --datestamp "$ds/results-srcu-lockdep" > $T…649 …torture_set "rcuscale-$prim" tools/testing/selftests/rcutorture/bin/kvm.sh --torture rcuscale --al…677 …torture_set "rcuscale-$prim$torture_suffix" tools/testing/selftests/rcutorture/bin/kvm-again.sh "`…687 …torture_set "rcuscale-kvfree" tools/testing/selftests/rcutorture/bin/kvm.sh --torture rcuscale --a…693 …torture_set "clocksourcewd-1" tools/testing/selftests/rcutorture/bin/kvm.sh --allcpus --duration 4…696 …torture_set "clocksourcewd-2" tools/testing/selftests/rcutorture/bin/kvm.sh --allcpus --duration 4…702 …torture_set "clocksourcewd-3" tools/testing/selftests/rcutorture/bin/kvm.sh --allcpus --duration 4…737 if test "$do_kcsan" = "yes" && test -e tools/testing/selftests/rcutorture/res/$ds[all …]
53 …tools/testing/selftests/rcutorture/bin/kvm.sh --allcpus --duration 5s --configs "SRCU-P" --kconfig…86 …tools/testing/selftests/rcutorture/bin/kvm.sh --allcpus --duration 5s --configs "SRCU-P" --kconfig…
20 PATH=`pwd`/tools/testing/selftests/rcutorture/bin:$PATH; export PATH
10 D=tools/testing/selftests/rcutorture
21 PATH=`pwd`/tools/testing/selftests/rcutorture/bin:$PATH; export PATH
18 if ! test -d tools/testing/selftests/rcutorture/bin
4 General instructions on running selftests can be found in7 __ /Documentation/bpf/bpf_devel_QA.rst#q-how-to-run-bpf-selftests14 automated fashion. The system runs selftests for each patch in a series. Results23 file fragments below ``tools/testing/selftests/bpf/`` (e.g., ``config`` and35 In addition to that, the generic ``tools/testing/selftests/bpf/DENYLIST`` is52 It's now possible to run the selftests using ``tools/testing/selftests/bpf/vmtest.sh``.74 $ tools/testing/selftests/bpf/vmtest.sh -h107 tools/testing/selftests/bpf/vmtest.sh \110 \"$(cat tools/testing/selftests/bpf/DENYLIST.riscv64 \272 Some selftests (e.g. kfunc_call and bpf_tcp_ca) require a LLVM support[all …]
1 # pre-canned list of rather complex selftests/bpf BPF object files to monitor
10 FEATURE-DUMP.selftests
4 tools/testing/selftests/rcutorture/bin/mkinitrd.sh.11 cd tools/testing/selftests/rcutorture
5 $ size tools/testing/selftests/rcutorture/initrd/init7 328 0 8 336 150 tools/testing/selftests/rcutorture/initrd/init15 tools/testing/selftests/rcutorture/initrd17 For example, your tools/testing/selftests/rcutorture/initrd/init might
16 $ make -C tools/testing/selftests TARGETS=arm64 \21 $ make -C tools/testing/selftests TARGETS=arm64 ARM64_SUBTARGETS="tags signal" \
18 CFLAGS += -I$(top_srcdir)/tools/testing/selftests/
40 $0 -- ./tools/testing/selftests/hid/hid_bpf48 O=<kernel_build_path> $0 -- ./tools/testing/selftests/hid/hid_bpf52 KBUILD_OUTPUT=<kernel_build_path> $0 -- ./tools/testing/selftests/hid/hid_bpf58 -b) Run only the build steps for the kernel and the selftests
3 ( cd ../../../..; tools/testing/selftests/rcutorture/bin/kvm.sh --duration 10 --configs TREE01 )
24 $ make -C tools/testing/selftests TARGETS=resctrl33 $ sudo make -C tools/testing/selftests TARGETS=resctrl run_tests44 Build executable file "resctrl_tests" from this directory(tools/testing/selftests/resctrl/):
19 CFLAGS += -I$(top_srcdir)/tools/testing/selftests/
98 selftests: FORCE target126 perf selftests bootconfig spi turbostat usb \
42 By being simplistic these selftests expect to allocate the entire set of source
15 cd tools/testing/selftests/media_tests
Completed in 23 milliseconds