Home
last modified time | relevance | path

Searched refs:testcases (Results 1 – 19 of 19) sorted by relevance

/linux-5.19.10/tools/testing/selftests/arm64/signal/
DMakefile7 SRCS := $(filter-out testcases/testcases.c,$(wildcard testcases/*.c))
27 …ignals.c test_signals_utils.c testcases/testcases.c signals.S $$@.c test_signals.h test_signals_ut…
DREADME20 - 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-5.19.10/tools/testing/selftests/ftrace/
DREADME3 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-5.19.10/Documentation/translations/zh_CN/devicetree/
Dof_unittest.rst35 设备树源文件（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-5.19.10/tools/testing/selftests/tc-testing/
Dtdc_helper.py10 testcases = dict()
13 testcases[category] = list(filter(lambda x: category in x['category'], alltests))
15 return(testcases)
Dtdc.py689 ucat, idlist, testcases, alltests = get_test_cases(args)
/linux-5.19.10/tools/testing/selftests/vm/
Dva_128TBswitch.c42 static struct testcase testcases[] = { variable
285 ret = run_test(testcases, ARRAY_SIZE(testcases)); in main()
/linux-5.19.10/Documentation/devicetree/
Dof_unittest.rst51 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-5.19.10/tools/testing/selftests/powerpc/stringloops/
Dmemcmp.c153 static int testcases(void) in testcases() function
168 return test_harness(testcases, "memcmp"); in main()
/linux-5.19.10/tools/perf/tests/
Dhists_cumulate.c700 test_fn_t testcases[] = { in test__hists_cumulate() local
726 for (i = 0; i < ARRAY_SIZE(testcases); i++) { in test__hists_cumulate()
727 err = testcases[i](evsel, machine); in test__hists_cumulate()
Dhists_output.c586 test_fn_t testcases[] = { in test__hists_output() local
613 for (i = 0; i < ARRAY_SIZE(testcases); i++) { in test__hists_output()
614 err = testcases[i](evsel, machine); in test__hists_output()
/linux-5.19.10/drivers/of/unittest-data/
Dtests-interrupts.dtsi86 * located in testcases.dts instead of in this file so that the
DMakefile2 obj-y += testcases.dtb.o
/linux-5.19.10/Documentation/process/
Dbotching-up-ioctls.rst81 * 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
/linux-5.19.10/Documentation/fault-injection/
Dfault-injection.rst72 for some testcases. Consider setting probability=100 and configure
73 /sys/kernel/debug/fail*/interval for such testcases.
/linux-5.19.10/Documentation/gpu/
Dvkms.rst148 all relevant igt testcases work on vkms. They are good options for internship
Ddrm-uapi.rst97 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
Dtodo.rst319 Might be good to also have some igt testcases for this.
631 including tons of testcases for corner-cases in the modesetting API. It would
/linux-5.19.10/Documentation/locking/
Drobust-futexes.rst215 robust-mutex testcases.