Searched refs:cases (Results 1 – 25 of 39) sorted by relevance
12
| /tools/testing/selftests/rcutorture/doc/ |
| D | TINY_RCU.txt | 1 This document gives a brief rationale for the TINY_RCU test cases.
19 In common code tested by TREE_RCU test cases.
|
| D | initrd.txt | 3 very long sleep() call. In both cases, this creation is done by
|
| D | TREE_RCU-kconfig.txt | 2 cases, a group that includes PREEMPT_RCU.
|
| /tools/testing/selftests/tc-testing/ |
| D | README | 59 cases. To disable execution within the namespace, pass the -N option
77 future). A test suite has one or more test cases in it.
106 executed as part of the test. More will be added as test cases require.
111 The NAMES values are used to substitute into the commands in the test cases.
131 Execute test cases that use a physical device, where
137 select which test cases: files plus directories; filtered by categories
150 Execute the specified test cases with specified IDs
153 select action to perform on selected test cases
155 -l, --list List all test cases, or those only within the
157 -s, --show Display the selected test cases
[all …]
|
| /tools/testing/kunit/ |
| D | kunit_json.py | 35 for case in test_suite.cases:
|
| D | kunit_parser.py | 23 self.cases = [] # type: List[TestCase]
26 return 'TestSuite(' + str(self.status) + ',' + self.name + ',' + str(self.cases) + ')'
278 max_test_case_status = bubble_up_errors(x.status for x in test_suite.cases)
298 test_suite.cases.append(test_case)
389 for test_case in test_suite.cases:
|
| /tools/testing/selftests/tc-testing/creating-plugins/ |
| D | AddingPlugins.txt | 15 - adding commands to be run before and/or after the test cases
16 - adding commands to be run before and/or after the execute phase of the test cases
59 the TAP output for the extra test cases.
|
| /tools/testing/selftests/tc-testing/creating-testcases/ |
| D | AddingTestCases.txt | 1 tdc - Adding test cases for tdc
10 template.json for the required JSON format for test cases.
18 If you wish to store your custom test cases elsewhere, be sure to run
81 in the test cases. tdc will output a series of TAP results for the skipped
|
| /tools/testing/selftests/ftrace/ |
| D | README | 5 shell scripts for testing. Feel free to add new test cases.
38 * The test cases should run on dash (busybox shell) for testing on
|
| /tools/testing/selftests/arm64/signal/ |
| D | README | 24 - Signals' test-cases hereafter defined belong currently to two
56 In both cases test results are expected in terms of:
|
| /tools/memory-model/litmus-tests/ |
| D | Z6.0+pooncerelease+poacquirerelease+fencembonceonce.litmus | 13 * full barrier for each non-rf link. (Exceptions include some cases
|
| /tools/memory-model/Documentation/ |
| D | glossary.txt | 21 "p->a". In rare cases, optimizing compilers can destroy address
70 name suggests. And in a great many cases, a pair of CPUs is all
71 that is required. In other cases, the notion of pairing must be
100 especially true in cases where the dependency is carried through
|
| D | simple.txt | 121 by the percpu_counter infrastructure. In many cases, there are already
146 For more sophisticated use cases, LKMM can guide you, including use
147 cases involving combining sequence locking with other synchronization
223 WRITE_ONCE() can safely be used in some cases. These primitives provide
265 More complex use cases
|
| D | recipes.txt | 6 The first section covers simple special cases, the second section
11 Simple special cases
14 This section presents two simple special cases, the first being where
293 to understand their use cases. The general approach is shown below:
|
| /tools/testing/ktest/examples/ |
| D | README | 7 and commented to show more generic use cases that are more helpful for
|
| /tools/thermal/tmon/ |
| D | README | 18 thermal conditions are often exception cases that hard to reach in
|
| /tools/testing/selftests/futex/ |
| D | README | 8 odd corner cases, regression tests, and abject abuse and misuse.
|
| /tools/perf/Documentation/ |
| D | perf-c2c.txt | 118 Disabled by default. In common cases with call stack overflows,
120 output. But this approach is not full proof. There can be cases
|
| D | perf-top.txt | 228 in such cases.
337 Disabled by default. In common cases with call stack overflows,
339 output. But this approach is not full proof. There can be cases
|
| D | perf-script.txt | 207 cases e.g. "jcc (x)" for a condition branch within a transaction.
488 Disabled by default. In common cases with call stack overflows,
490 output. But this approach is not full proof. There can be cases
|
| D | perf-kvm.txt | 158 in such cases.
|
| D | perf-trace.txt | 185 only at exit time or when a syscall is interrupted, i.e. in those cases this
223 because the file may be huge. A time out is needed in such cases.
|
| /tools/build/ |
| D | Build.include | 55 # PHONY targets skipped in both cases.
|
| /tools/memory-model/ |
| D | lock.cat | 101 * We rely on the memory model to rule out cases where spin_is_locked()
|
| /tools/testing/selftests/filesystems/fuse/ |
| D | fuse_test.c | 2275 const struct test_case cases[] = { in main() local
2315 bool run_test[ARRAY_SIZE(cases)]; in main()
2317 for (int i = 0; i < ARRAY_SIZE(cases); ++i) in main()
2320 if (parse_options(argc, argv, run_test, ARRAY_SIZE(cases))) in main()
2352 run_one_test(mount_dir, &cases[i]); in main()
|
12