Home
last modified time | relevance | path

Searched refs:cases (Results 1 – 25 of 809) sorted by relevance

12345678910>>...33

/linux/tools/testing/selftests/drivers/net/hw/
H A Dcsum.py106 cases = []
108 cases.append(test_builder("rx_tcp", cfg, ipv4, False, "-t"))
109 cases.append(test_builder("rx_tcp_invalid", cfg, ipv4, False, "-t -E"))
111 cases.append(test_builder("rx_udp", cfg, ipv4, False, ""))
112 cases.append(test_builder("rx_udp_invalid", cfg, ipv4, False, "-E"))
114 cases.append(test_builder("tx_udp_csum_offload", cfg, ipv4, True, "-U"))
115 cases.append(test_builder("tx_udp_zero_checksum", cfg, ipv4, True, "-U -Z"))
117 ksft_run(cases=cases, args=(cfg, ))
/linux/tools/testing/selftests/net/lib/py/
H A Dksft.py106 def ksft_run(cases=None, globs=None, case_pfx=None, args=()): argument
107 cases = cases or []
115 cases.append(value)
121 print("1.." + str(len(cases)))
125 for case in cases:
/linux/scripts/coccinelle/misc/
H A Dcond_no_effect.cocci5 // There can be false positives in cases where the positional
7 // is a placeholder for not yet handled cases.
17 // the two known cases are:
38 // All other cases look like bugs or at least lack of documentation
H A Dbadty.cocci4 //# This makes an effort to find cases where the argument to sizeof is wrong
7 //# to the the memory being allocated. There are false positives in cases the
/linux/Documentation/livepatch/
H A Dreliable-stacktrace.rst41 In some cases it is legitimate to omit specific functions from the trace,
42 but all other functions must be reported. These cases are described in
45 Secondly, the reliable stacktrace function must be robust to cases where
47 function should attempt to detect such cases and return a non-zero error
49 an unsafe way. Specific cases are described in further detail below.
55 To ensure that kernel code can be correctly unwound in all cases,
63 In some cases, an unwinder may require metadata to correctly unwind.
115 To ensure that such cases do not result in functions being omitted from a
148 Architectures which cannot identify when it is reliable to unwind such cases
176 unwinder must report these cases as unreliable.
[all …]
/linux/net/bluetooth/
H A DKconfig130 cases are run first thing at module load time. When the Bluetooth
131 subsystem is compiled into the kernel image, then the test cases
135 bool "ECDH test cases"
138 Run test cases for ECDH cryptographic functionality used by the
142 bool "SMP test cases"
145 Run test cases for SMP cryptographic functionality, including both
/linux/tools/testing/selftests/bpf/prog_tests/
H A Dlibbpf_probes.c102 } cases[] = { in test_libbpf_probe_helpers() local
113 size_t case_cnt = ARRAY_SIZE(cases), i; in test_libbpf_probe_helpers()
117 const struct case_def *d = &cases[i]; in test_libbpf_probe_helpers()
/linux/tools/testing/selftests/rcutorture/doc/
H A DTINY_RCU.txt1 This document gives a brief rationale for the TINY_RCU test cases.
19 In common code tested by TREE_RCU test cases.
/linux/Documentation/userspace-api/
H A Dmseal.rst63 - For above error cases, users can expect the given memory range is
66 - There might be other internal errors/cases not listed here, e.g.
68 number of supported VMAs. In those cases, partial updates to the given
69 memory range could happen. However, those cases should be rare.
121 Use cases:
178 to RO memory, which is, in a way, by design. Those cases are not covered
179 by mseal(). If applications want to block such cases, sandbox tools (such as
182 Those cases are:
/linux/Documentation/RCU/
H A Drcuref.rst11 those unusual cases where percpu-ref would consume too much memory,
82 update (write) stream. In such cases, atomic_inc_not_zero() might be
84 use atomic_inc() in such cases.
87 search_and_reference() code path. In such cases, the
139 In cases where delete() can sleep, synchronize_rcu() can be called from
/linux/Documentation/dev-tools/kunit/
H A Dusage.rst196 ``example_suite_init``, then run the test cases ``example_test_foo``,
512 struct sha1_test_case cases[] = {
522 for (i = 0; i < ARRAY_SIZE(cases); ++i) {
523 sha1sum(cases[i].str, out);
524 KUNIT_EXPECT_STREQ_MSG(test, out, cases[i].sha1,
525 "sha1sum(%s)", cases[i].str);
538 field and reuse ``cases``.
558 const struct sha1_test_case cases[] = {
571 KUNIT_ARRAY_PARAM_DESC(sha1, cases, str);
577 // The former `cases[i]` is accessible under test->param_value.
[all …]
H A Dindex.rst28 of test cases called test suites. The tests either run on kernel boot
30 failed test cases in the kernel log. The test results appear in
78 Arrange-Act-Assert. This is a great way to structure test cases and
/linux/Documentation/devicetree/bindings/slimbus/
H A Dslimbus.yaml39 In some cases it may be necessary to describe non-probeable device
40 details such as non-standard ways of powering up a device. In such cases,
54 - Instance ID, can be used for the cases where multiple devices of
/linux/Documentation/power/regulator/
H A Ddesign.rst24 Consumer use cases
36 The consumer API should be structured so that these use cases are
/linux/Documentation/devicetree/bindings/iommu/
H A Diommu.txt44 the specific IOMMU. Below are a few examples of typical use-cases:
51 In such cases the number of cells will usually be 1 as in the next case.
53 in order to enable translation for a given master. In such cases the single
54 address cell corresponds to the master device's ID. In some cases more than
62 Note that these are merely examples and real-world use-cases may use different
85 have a means to turn off translation. But it is invalid in such cases to
/linux/Documentation/process/
H A Ddeprecated.rst63 cases is to refactor the code as suggested below to avoid the open-coded
129 is strscpy(), though care must be given to any cases where the return
144 strscpy(), though care must be given to any cases where the return value
147 errno when it truncates). Any cases still needing NUL-padding should
153 attribute to avoid future compiler warnings. For cases still needing
162 though care must be given to any cases where the return value of strlcpy()
202 The C language allows switch cases to fall through to the next case
222 cases, we have adopted a pseudo-keyword macro "fallthrough" which
242 for these cases. The older style of one-element or zero-length arrays should
350 There are two special cases of replacement where the DECLARE_FLEX_ARRAY()
[all …]
/linux/tools/testing/selftests/tc-testing/creating-testcases/
H A DAddingTestCases.txt1 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
83 in the test cases. tdc will output a series of TAP results for the skipped
/linux/tools/testing/selftests/tc-testing/creating-plugins/
H A DAddingPlugins.txt15 - 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.
/linux/arch/m68k/fpsp040/
H A Dsto_res.S35 cmpib #3,%d0 |check for fp0/fp1 cases
68 cmpib #3,%d0 |check for fp0/fp1 cases
/linux/Documentation/devicetree/bindings/interconnect/
H A Dqcom,bcm-voter.yaml34 In most cases, it's necessary to wait in both the AMC and WAKE sets to
36 cases can ensure sufficient delay by other means, then this can be
/linux/sound/hda/
H A DKconfig41 # A fallback is provided so that the code compiles in all cases.
49 # A fallback is provided so that the code compiles in all cases.
/linux/Documentation/gpu/rfc/
H A Di915_small_bar.rst5 I915_MEMORY_CLASS_DEVICE), but in some cases the final BAR size might still be
6 smaller than the total probed_size. In such cases, only some subset of
/linux/drivers/gpu/drm/xe/tests/
H A Dxe_wa_test.c56 static const struct platform_test_case cases[] = { variable
84 KUNIT_ARRAY_PARAM(platform, cases, platform_desc);
/linux/Documentation/arch/powerpc/
H A Dultravisor.rst312 Use cases
386 Use cases
437 Use cases
483 Use cases
544 Use cases
593 Use cases
638 Use cases
673 Use cases
720 Use cases
770 Use cases
[all …]
/linux/drivers/gpu/drm/ci/
H A Dstatic-checks.yml12 # Other cases default to never

12345678910>>...33