| /linux-6.6.21/tools/testing/selftests/arm64/signal/ |
| D | Makefile | 7 SRCS := $(filter-out testcases/testcases.c,$(wildcard testcases/*.c))
25 COMMON_SOURCES := test_signals.c test_signals_utils.c testcases/testcases.c \
27 COMMON_HEADERS := test_signals.h test_signals_utils.h testcases/testcases.h
|
| D | README | 20 - New tests can be simply defined in testcases/ dir providing a proper struct
39 unrelated SEGV bugs in the testcases, it becomes extremely tricky to
|
| /linux-6.6.21/tools/testing/selftests/x86/ |
| D | lam.c | 71 struct testcases { struct
77 int (*test_func)(struct testcases *test); argument
260 int handle_max_bits(struct testcases *test) in handle_max_bits()
279 static int handle_malloc(struct testcases *test) in handle_malloc()
311 static int handle_mmap(struct testcases *test) in handle_mmap()
347 static int handle_syscall(struct testcases *test) in handle_syscall()
634 int handle_uring(struct testcases *test) in handle_uring()
652 static int fork_test(struct testcases *test) in fork_test()
672 static int handle_execve(struct testcases *test) in handle_execve()
708 static int handle_inheritance(struct testcases *test) in handle_inheritance()
[all …]
|
| /linux-6.6.21/tools/testing/selftests/ftrace/ |
| D | README | 3 This is a collection of testcases for ftrace tracing feature in the Linux
7 Running the ftrace testcases
11 To run all testcases:
15 To run specific testcases:
19 Or you can also run testcases under given directory:
23 Contributing new testcases
36 * You can add a directory for your testcases under test.d/ if needed.
|
| /linux-6.6.21/Documentation/translations/zh_CN/devicetree/ |
| D | of_unittest.rst | 35 设备树源文件（drivers/of/unittest-data/testcases.dts）包含执行drivers/of/unittest.c
36 中自动化单元测试所需的测试数据。目前，以下设备树源包含文件（.dtsi）被包含在testcases.dt中::
48 用于将DT源文件（testcases.dts）编译成二进制blob（testcases.dtb），也被称为扁平化的DT。
50 之后，使用以下规则将上述二进制blob包装成一个汇编文件（testcases.dtb.S）::
55 汇编文件被编译成一个对象文件（testcases.dtb.o），并被链接到内核镜像中。
|
| /linux-6.6.21/tools/testing/selftests/tc-testing/ |
| D | tdc_helper.py | 10 testcases = dict()
13 testcases[category] = list(filter(lambda x: category in x['category'], alltests))
15 return(testcases)
|
| D | tdc.py | 813 ucat, idlist, testcases, alltests = get_test_cases(args)
|
| /linux-6.6.21/tools/testing/selftests/mm/ |
| D | va_high_addr_switch.c | 62 static struct testcase testcases[] = { variable
308 ret = run_test(testcases, ARRAY_SIZE(testcases)); in main()
|
| /linux-6.6.21/Documentation/devicetree/ |
| D | of_unittest.rst | 51 The Device Tree Source file (drivers/of/unittest-data/testcases.dts) contains
54 (.dtsi) are included in testcases.dts::
67 is used to compile the DT source file (testcases.dts) into a binary blob
68 (testcases.dtb), also referred as flattened DT.
71 assembly file (testcases.dtb.S)::
76 The assembly file is compiled into an object file (testcases.dtb.o), and is
|
| /linux-6.6.21/tools/testing/selftests/powerpc/stringloops/ |
| D | memcmp.c | 153 static int testcases(void) in testcases() function
168 return test_harness(testcases, "memcmp"); in main()
|
| /linux-6.6.21/tools/perf/tests/ |
| D | hists_cumulate.c | 713 test_fn_t testcases[] = { in test__hists_cumulate() local
739 for (i = 0; i < ARRAY_SIZE(testcases); i++) { in test__hists_cumulate()
740 err = testcases[i](evsel, machine); in test__hists_cumulate()
|
| D | hists_output.c | 599 test_fn_t testcases[] = { in test__hists_output() local
626 for (i = 0; i < ARRAY_SIZE(testcases); i++) { in test__hists_output()
627 err = testcases[i](evsel, machine); in test__hists_output()
|
| /linux-6.6.21/drivers/of/unittest-data/ |
| D | tests-interrupts.dtsi | 87 * located in testcases.dts instead of in this file so that the
|
| D | Makefile | 2 obj-y += testcases.dtbo.o
|
| /linux-6.6.21/Documentation/process/ |
| D | botching-up-ioctls.rst | 81 * Have simple testcases for all of the above.
99 * Have simple testcases for every input validation failure case in your ioctl.
122 * Have testcases for the really tricky corner cases in your error recovery code
163 * Have testcases for corner-cases, especially whether the return values for
|
| D | maintainer-kvm-x86.rst | 277 but dedicated KVM tests are preferred in all cases. Negative testcases in
|
| /linux-6.6.21/Documentation/fault-injection/ |
| D | fault-injection.rst | 80 for some testcases. Consider setting probability=100 and configure
81 /sys/kernel/debug/fail*/interval for such testcases.
|
| /linux-6.6.21/Documentation/gpu/ |
| D | vkms.rst | 132 all relevant igt testcases work on vkms. They are good options for internship
|
| D | drm-uapi.rst | 97 userspace project. For e.g. mesa this means piglit testcases and review on the
371 should have driver-agnostic testcases in IGT for that feature, if such a test
|
| D | todo.rst | 320 Might be good to also have some igt testcases for this.
634 including tons of testcases for corner-cases in the modesetting API. It would
|
| /linux-6.6.21/Documentation/bpf/ |
| D | cpumasks.rst | 384 selftest testcases to the cpumask selftest suite.
|
| /linux-6.6.21/Documentation/locking/ |
| D | robust-futexes.rst | 215 robust-mutex testcases.
|