Searched refs:selftests (Results 1 – 25 of 87) sorted by relevance
1234
7 The ``devlink-selftests`` API allows executing selftests on the device.11 The ``devlink-selftests`` command should be run with a mask indicating33 # Query selftests supported on the devlink device34 $ devlink dev selftests show DEV35 # Query selftests supported on all devlink devices36 $ devlink dev selftests show37 # Executes selftests on the device38 $ devlink dev selftests run DEV id flash
5 The kernel contains a set of "self tests" under the tools/testing/selftests/34 Running the selftests (hotplug tests are run in limited mode)39 $ make -C tools/testing/selftests43 $ make -C tools/testing/selftests run_tests54 kernel src. This is applicable to "Running a subset of selftests" section72 to "Running a subset of selftests" section below.78 Running a subset of selftests86 $ make -C tools/testing/selftests TARGETS=ptrace run_tests105 $ make -C tools/testing/selftests SKIP_TARGETS=ptrace run_tests116 See the top-level tools/testing/selftests/Makefile for the list of all[all …]
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
350 …torture_set "rcutorture" tools/testing/selftests/rcutorture/bin/kvm.sh --allcpus --duration "$dura…356 …torture_set "locktorture" tools/testing/selftests/rcutorture/bin/kvm.sh --torture lock --allcpus -…362 …torture_set "scftorture" tools/testing/selftests/rcutorture/bin/kvm.sh --torture scf --allcpus --d…369 …torture_set "rcurttorture" tools/testing/selftests/rcutorture/bin/kvm.sh --allcpus --duration "$du…373 …torture_set "rcurttorture-exp" tools/testing/selftests/rcutorture/bin/kvm.sh --allcpus --duration …397 …torture_set "rcuscale-$prim" tools/testing/selftests/rcutorture/bin/kvm.sh --torture rcuscale --al…403 …torture_set "rcuscale-kvfree" tools/testing/selftests/rcutorture/bin/kvm.sh --torture rcuscale --a…409 …torture_set "clocksourcewd-1" tools/testing/selftests/rcutorture/bin/kvm.sh --allcpus --duration 4…412 …torture_set "clocksourcewd-2" tools/testing/selftests/rcutorture/bin/kvm.sh --allcpus --duration 4…418 …torture_set "clocksourcewd-3" tools/testing/selftests/rcutorture/bin/kvm.sh --allcpus --duration 4…[all …]
20 PATH=`pwd`/tools/testing/selftests/rcutorture/bin:$PATH; export PATH
326 gem/selftests/i915_gem_client_blt.o \327 gem/selftests/igt_gem_utils.o \328 selftests/intel_scheduler_helpers.o \329 selftests/i915_random.o \330 selftests/i915_selftest.o \331 selftests/igt_atomic.o \332 selftests/igt_flush_test.o \333 selftests/igt_live_test.o \334 selftests/igt_mmap.o \335 selftests/igt_reset.o \[all …]
170 bool "Enable selftests upon driver load"178 Choose this option to allow the driver to perform selftests upon180 exit the module after running the selftests (i.e. to prevent normal188 bool "Enable broken and dangerous selftests"193 This option enables the execution of selftests that are "dangerous"
26 } selftests[] = { variable34 module_param_named(id, selftests[__idx_##n].enabled, bool, 0400);155 return run_selftests(selftests, ARRAY_SIZE(selftests)); in st_init()
4 General instructions on running selftests can be found in7 __ /Documentation/bpf/bpf_devel_QA.rst#q-how-to-run-bpf-selftests13 It's now possible to run the selftests using ``tools/testing/selftests/bpf/vmtest.sh``.19 bpf selftests, runs them (by default ``tools/testing/selftests/bpf/test_progs``) and33 $ tools/testing/selftests/bpf/vmtest.sh -h35 In case of linker errors when running selftests, try using static linking:171 A set of selftests use BPF target-specific built-ins, which might require192 Certain selftests, e.g. core_reloc, require support for the floating-point201 Some selftests (e.g. kfunc_call and bpf_tcp_ca) require a LLVM support204 Without it, the error from compiling bpf selftests looks like:
1 # pre-canned list of rather complex selftests/bpf BPF object files to monitor
134 `tools/testing/selftests/bpf/progs/lsm.c`_ and the corresponding135 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/…
122 -C tools/testing/selftests \124 INSTALL_PATH=$PWD/tools/testing/selftests/kselftest_install \162 cd /linux/tools/testing/selftests/kselftest_install167 cd /linux/tools/testing/selftests/bpf
235 Q: samples/bpf preference vs selftests?241 ``samples/bpf/``. The rationale is very simple: kernel selftests are244 The more test cases we add to BPF selftests, the better the coverage246 not that BPF kernel selftests cannot demo how a specific feature can252 into kernel selftests.254 If your sample looks like a test case, then go for BPF kernel selftests413 Q: How to run BPF selftests419 $ cd tools/testing/selftests/bpf/432 In order to run through all BPF selftests, the following command is442 tools/testing/selftests/bpf as closely as possible.[all …]
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" \
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/):
91 There are tools/testing/selftests using the notifier error injection features94 * tools/testing/selftests/cpu-hotplug/cpu-on-off-test.sh95 * tools/testing/selftests/memory-hotplug/mem-on-off-test.sh
72 .. note:: pkey_set()是RDPKRU和WRPKRU指令的一个封装器。在tools/testing/selftests/x86/protection_keys.c中可以找到一个实现实…73 tools/testing/selftests/x86/protection_keys.c.
29 To run the livepatch selftests, from the top of the kernel source tree:31 % make -C tools/testing/selftests TARGETS=livepatch run_tests
3 ( cd ../../../..; tools/testing/selftests/rcutorture/bin/kvm.sh --duration 10 --configs TREE01 )
64 support can be found here: `tools/testing/selftests/landlock/`_.100 .. _tools/testing/selftests/landlock/:101 …https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/tree/tools/testing/selftests/land…
79 bool "Run FIPS selftests on the X.509+PKCS7 signature verification"81 This option causes some selftests to be run on the signature
67 CGROUP_HELPERS := ../../tools/testing/selftests/bpf/cgroup_helpers.o68 TRACE_HELPERS := ../../tools/testing/selftests/bpf/trace_helpers.o198 TPROGS_CFLAGS += -I$(srctree)/tools/testing/selftests/bpf/347 -I$(src)/../../tools/testing/selftests/bpf436 -I$(obj) -I$(srctree)/tools/testing/selftests/bpf/ \