Searched refs:selftests (Results 1 – 25 of 37) sorted by relevance
12
5 The kernel contains a set of "self tests" under the tools/testing/selftests/17 Running the selftests (hotplug tests are run in limited mode)22 $ make -C tools/testing/selftests26 $ make -C tools/testing/selftests run_tests46 Running a subset of selftests54 $ make -C tools/testing/selftests TARGETS=ptrace run_tests72 See the top-level tools/testing/selftests/Makefile for the list of all75 Running the full range hotplug selftests80 $ make -C tools/testing/selftests hotplug84 $ make -C tools/testing/selftests run_hotplug[all …]
37 } selftests[] = { variable45 module_param_named(id, selftests[__idx_##n].enabled, bool, 0400);
239 err = run_selftests(selftests, ARRAY_SIZE(selftests), NULL); in test_drm_helper_init()
118 bool "Enable selftests upon driver load"124 Choose this option to allow the driver to perform selftests upon126 exit the module after running the selftests (i.e. to prevent normal134 bool "Enable broken and dangerous selftests"139 This option enables the execution of selftests that are "dangerous"
161 selftests/i915_random.o \162 selftests/i915_selftest.o \163 selftests/igt_flush_test.o
87 There are tools/testing/selftests using the notifier error injection features90 * tools/testing/selftests/cpu-hotplug/on-off-test.sh91 * tools/testing/selftests/memory-hotplug/on-off-test.sh
356 Run a command "make -C tools/testing/selftests/ run_tests" with injecting slab360 -- make -C tools/testing/selftests/ run_tests366 -- make -C tools/testing/selftests/ run_tests373 -- make -C tools/testing/selftests/ run_tests
33 PATH=`pwd`/tools/testing/selftests/rcutorture/bin:$PATH; export PATH
27 PATH=`pwd`/tools/testing/selftests/rcutorture/bin:$PATH; export PATH
60 CGROUP_HELPERS := ../../tools/testing/selftests/bpf/cgroup_helpers.o61 TRACE_HELPERS := ../../tools/testing/selftests/bpf/trace_helpers.o172 KBUILD_HOSTCFLAGS += -I$(srctree)/tools/testing/selftests/bpf/269 -I$(srctree)/tools/testing/selftests/bpf/ \
79 selftests: FORCE target95 perf selftests spi turbostat usb \
240 Q: samples/bpf preference vs selftests?246 `samples/bpf/`_. The rationale is very simple: kernel selftests are249 The more test cases we add to BPF selftests, the better the coverage251 not that BPF kernel selftests cannot demo how a specific feature can257 into kernel selftests.259 If your sample looks like a test case, then go for BPF kernel selftests418 Q: How to run BPF selftests424 $ cd tools/testing/selftests/bpf/437 In order to run through all BPF selftests, the following command is445 Q: Which BPF kernel selftests version should I run my kernel against?[all …]
9 cd tools/testing/selftests/rcutorture26 cd tools/testing/selftests/rcutorture
20 tools/testing/selftests/vDSO/parse_vdso.c.
15 cd tools/testing/selftests/media_tests
28 tools/testing/selftests/watchdog/watchdog-test.c
18 basic application exists in tools/testing/selftests/watchdog/ named
47 obj-$(CONFIG_DRM_DEBUG_SELFTEST) += selftests/
65 See tools/testing/selftests/filesystems/dnotify_test.c for an example.
62 tools/testing/selftests/x86/protection_keys.c)
133 2. Run several copies of all of the tools/testing/selftests/x86/ tests158 * Failures of the selftests/x86 code. Usually a bug in one of the
59 linux$ make -C tools/testing/selftests TARGETS=android run_tests
371 see tools/testing/selftests/vm/map_hugetlb.c374 see tools/testing/selftests/vm/hugepage-shm.c377 see tools/testing/selftests/vm/hugepage-mmap.c
34 bool "LPAE selftests"53 bool "ARMv7s selftests"
310 However, the tools/testing/selftests/rcutorture/bin/kvm.sh script313 See tools/testing/selftests/rcutorture/doc/initrd.txt for instructions
