Searched refs:testcases (Results 1 – 18 of 18) sorted by relevance
| /linux/tools/testing/selftests/arm64/signal/ |
| A D | Makefile | 7 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…
|
| A 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/tools/testing/selftests/ftrace/ |
| A 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/tools/testing/selftests/tc-testing/ |
| A D | tdc_helper.py | 10 testcases = dict()
13 testcases[category] = list(filter(lambda x: category in x['category'], alltests))
15 return(testcases)
|
| A D | tdc.py | 689 ucat, idlist, testcases, alltests = get_test_cases(args)
|
| /linux/tools/testing/selftests/vm/ |
| A D | va_128TBswitch.c | 42 static struct testcase testcases[] = { variable
285 ret = run_test(testcases, ARRAY_SIZE(testcases)); in main()
|
| /linux/Documentation/devicetree/ |
| A D | of_unittest.rst | 30 The Device Tree Source file (drivers/of/unittest-data/testcases.dts) contains
33 (.dtsi) are included in testcases.dts::
46 is used to compile the DT source file (testcases.dts) into a binary blob
47 (testcases.dtb), also referred as flattened DT.
50 assembly file (testcases.dtb.S)::
55 The assembly file is compiled into an object file (testcases.dtb.o), and is
|
| /linux/tools/testing/selftests/powerpc/stringloops/ |
| A D | memcmp.c | 153 static int testcases(void) in testcases() function
168 return test_harness(testcases, "memcmp"); in main()
|
| /linux/tools/perf/tests/ |
| A D | hists_cumulate.c | 700 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()
|
| A D | hists_output.c | 586 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/drivers/of/unittest-data/ |
| A D | Makefile | 2 obj-y += testcases.dtb.o
|
| A D | tests-interrupts.dtsi | 86 * located in testcases.dts instead of in this file so that the
|
| /linux/Documentation/process/ |
| A 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
|
| /linux/Documentation/fault-injection/ |
| A D | fault-injection.rst | 72 for some testcases. Consider setting probability=100 and configure
73 /sys/kernel/debug/fail*/interval for such testcases.
|
| /linux/Documentation/gpu/ |
| A D | vkms.rst | 150 all relevant igt testcases work on vkms. They are good options for internship
|
| A D | drm-uapi.rst | 97 userspace project. For e.g. mesa this means piglit testcases and review on the
369 should have driver-agnostic testcases in IGT for that feature, if such a test
|
| A D | todo.rst | 308 Might be good to also have some igt testcases for this.
597 including tons of testcases for corner-cases in the modesetting API. It would
|
| /linux/Documentation/locking/ |
| A D | robust-futexes.rst | 215 robust-mutex testcases.
|
Completed in 27 milliseconds