Home
last modified time | relevance | path

Searched refs:tests (Results 1 – 25 of 375) sorted by relevance

12345678910>>...15

/Linux-v5.15/tools/testing/selftests/bpf/prog_tests/
Dglobal_data.c18 } tests[] = { in test_global_data_number() local
32 for (i = 0; i < sizeof(tests) / sizeof(tests[0]); i++) { in test_global_data_number()
33 err = bpf_map_lookup_elem(map_fd, &tests[i].key, &num); in test_global_data_number()
34 CHECK(err || num != tests[i].num, tests[i].name, in test_global_data_number()
36 err, num, tests[i].num); in test_global_data_number()
53 } tests[] = { in test_global_data_string() local
61 for (i = 0; i < sizeof(tests) / sizeof(tests[0]); i++) { in test_global_data_string()
62 err = bpf_map_lookup_elem(map_fd, &tests[i].key, str); in test_global_data_string()
63 CHECK(err || memcmp(str, tests[i].str, sizeof(str)), in test_global_data_string()
64 tests[i].name, "err %d result \'%s\' expected \'%s\'\n", in test_global_data_string()
[all …]
Dobj_name.c10 } tests[] = { in test_obj_name() local
23 for (i = 0; i < sizeof(tests) / sizeof(tests[0]); i++) { in test_obj_name()
24 size_t name_len = strlen(tests[i].name) + 1; in test_obj_name()
37 memcpy(attr.prog_name, tests[i].name, ncopy); in test_obj_name()
40 CHECK((tests[i].success && fd < 0) || in test_obj_name()
41 (!tests[i].success && fd >= 0) || in test_obj_name()
42 (!tests[i].success && errno != tests[i].expected_errno), in test_obj_name()
45 fd, tests[i].success, errno, tests[i].expected_errno); in test_obj_name()
59 memcpy(attr.map_name, tests[i].name, ncopy); in test_obj_name()
61 CHECK((tests[i].success && fd < 0) || in test_obj_name()
[all …]
Dflow_dissector.c107 struct test tests[] = { variable
486 for (i = 0; i < ARRAY_SIZE(tests); i++) { in run_tests_skb_less()
492 __u32 key = (__u32)(tests[i].keys.sport) << 16 | in run_tests_skb_less()
493 tests[i].keys.dport; in run_tests_skb_less()
499 if (tests[i].flags != eth_get_headlen_flags) in run_tests_skb_less()
502 err = tx_tap(tap_fd, &tests[i].pkt, sizeof(tests[i].pkt)); in run_tests_skb_less()
506 CHECK_ATTR(err, tests[i].name, "bpf_map_lookup_elem %d\n", err); in run_tests_skb_less()
508 CHECK_ATTR(err, tests[i].name, "skb-less err %d\n", err); in run_tests_skb_less()
509 CHECK_FLOW_KEYS(tests[i].name, flow_keys, tests[i].keys); in run_tests_skb_less()
512 CHECK_ATTR(err, tests[i].name, "bpf_map_delete_elem %d\n", err); in run_tests_skb_less()
[all …]
/Linux-v5.15/fs/btrfs/
DMakefile41 btrfs-$(CONFIG_BTRFS_FS_RUN_SANITY_TESTS) += tests/free-space-tests.o \
42 tests/extent-buffer-tests.o tests/btrfs-tests.o \
43 tests/extent-io-tests.o tests/inode-tests.o tests/qgroup-tests.o \
44 tests/free-space-tree-tests.o tests/extent-map-tests.o
/Linux-v5.15/drivers/of/unittest-data/
Dtestcases_common.dtsi14 #include "tests-phandle.dtsi"
15 #include "tests-interrupts.dtsi"
16 #include "tests-match.dtsi"
17 #include "tests-address.dtsi"
18 #include "tests-platform.dtsi"
19 #include "tests-overlay.dtsi"
/Linux-v5.15/Documentation/dev-tools/kunit/
Dindex.rst27 infrastructure for running tests, and much more.
30 writing unit tests. Tests written against KUnit will run on kernel boot if
31 built-in, or when loaded if built as a module. These tests write out results to
34 To make running these tests (and reading the results) easier, KUnit offers
37 results. This provides a quick way of running KUnit tests during development,
51 KUnit provides a common framework for unit tests within the kernel.
53 KUnit tests can be run on most architectures, and most tests are architecture
54 independent. All built-in KUnit tests run on kernel startup. Alternatively,
55 KUnit and KUnit tests can be built as modules and tests will run when the test
60 KUnit can also run tests without needing a virtual machine or actual
[all …]
Drunning_tips.rst25 Running a subset of tests
28 ``kunit.py run`` accepts an optional glob argument to filter tests. Currently
31 Say that we wanted to run the sysctl tests, we could do so via:
38 We're paying the cost of building more tests than we need this way, but it's
42 However, if we wanted to define a set of tests in a less ad hoc way, the next
45 Defining a set of tests
49 ``--kunitconfig`` flag. So if you have a set of tests that you want to run on a
53 E.g. kunit has one for its tests:
75 files to make it possible to have a top-level config run tests from all
80 automagically, but tests could theoretically depend on incompatible
[all …]
Dstyle.rst7 To make finding, writing, and using KUnit tests as simple as possible, it's
9 below. While it's possible to write KUnit tests which do not follow these rules,
10 they may break some tooling, may conflict with other tests, and may not be run
15 1. Porting tests to KUnit which are already known with an existing name, or
16 2. Writing tests which would cause serious problems if automatically run (e.g.,
23 In order to make tests as easy to find as possible, they're grouped into suites
24 and subsystems. A test suite is a group of tests which test a related area of
36 MAINTAINERS file. If unsure, follow the conventions set by tests in similar
45 unless you are actually testing other tests or the kunit framework itself.
75 provides a simple, consistent way for humans to find and run tests. This
[all …]
Dstart.rst12 Running tests with the KUnit Wrapper
14 Included with KUnit is a simple Python wrapper which runs tests under User Mode
28 If you want to run a specific set of tests (rather than those listed in the
32 options required by the tests.
48 ``.kunitconfig`` are set in the kernel ``.config`` before running the tests.
59 Running the tests (KUnit Wrapper)
80 followed by a list of tests that are run. All of them should be passing.
86 Running tests without the KUnit Wrapper
95 tests may reduce the stability or security of the system.
104 menuconfig). From there, you can enable any KUnit tests you want: they usually
[all …]
/Linux-v5.15/net/mptcp/
Dcrypto_test.c15 static struct test_case tests[] = { variable
41 for (i = 0; i < ARRAY_SIZE(tests); ++i) { in mptcp_crypto_test_basic()
43 key1 = be64_to_cpu(*((__be64 *)&tests[i].key[0])); in mptcp_crypto_test_basic()
44 key2 = be64_to_cpu(*((__be64 *)&tests[i].key[8])); in mptcp_crypto_test_basic()
45 nonce1 = be32_to_cpu(*((__be32 *)&tests[i].msg[0])); in mptcp_crypto_test_basic()
46 nonce2 = be32_to_cpu(*((__be32 *)&tests[i].msg[4])); in mptcp_crypto_test_basic()
56 KUNIT_EXPECT_STREQ(test, &hmac_hex[0], tests[i].result); in mptcp_crypto_test_basic()
/Linux-v5.15/tools/perf/tests/
DBuild69 $(OUTPUT)tests/llvm-src-base.c: tests/bpf-script-example.c tests/Build
71 $(Q)echo '#include <tests/llvm.h>' > $@
76 $(OUTPUT)tests/llvm-src-kbuild.c: tests/bpf-script-test-kbuild.c tests/Build
78 $(Q)echo '#include <tests/llvm.h>' > $@
83 $(OUTPUT)tests/llvm-src-prologue.c: tests/bpf-script-test-prologue.c tests/Build
85 $(Q)echo '#include <tests/llvm.h>' > $@
90 $(OUTPUT)tests/llvm-src-relocation.c: tests/bpf-script-test-relocation.c tests/Build
92 $(Q)echo '#include <tests/llvm.h>' > $@
/Linux-v5.15/Documentation/dev-tools/
Dkselftest.rst5 The kernel contains a set of "self tests" under the tools/testing/selftests/
6 directory. These are intended to be small tests to exercise individual code
11 write new tests using the framework on Kselftest wiki:
15 On some systems, hot-plug tests could hang forever waiting for cpu and
17 to run the full range of hot-plug tests. In default mode, hot-plug tests run
26 Running the selftests (hotplug tests are run in limited mode)
29 To build the tests::
33 To run the tests::
37 To build and run the tests with a single command, use::
41 Note that some tests will require root privileges.
[all …]
Dtesting-overview.rst16 The bulk of kernel tests are written using either the kselftest or KUnit
17 frameworks. These both provide infrastructure to help make running tests and
18 groups of tests easier, as well as providing helpers to aid in writing new
19 tests.
32 KUnit tests therefore are best written against small, self-contained parts
40 This also makes KUnit tests very fast to build and run, allowing them to be
48 largely implemented in userspace, and tests are normal userspace scripts or
51 This makes it easier to write more complicated tests, or tests which need to
56 work around this, some tests include a companion kernel module which exposes
60 kselftest is therefore suited well to tests of whole features, as these will
[all …]
/Linux-v5.15/tools/perf/Documentation/
Dperf-test.txt6 perf-test - Runs sanity tests.
15 This command does assorted sanity tests, initially through linked routines but
16 also will look for a directory with more tests in the form of scripts.
18 To get a list of available tests use 'perf test list', specifying a test name
19 fragment will show all tests that have it.
21 To run just specific tests, inform test name fragments or the numbers obtained
36 Do not fork child for each test, run all tests within single process.
/Linux-v5.15/tools/lib/perf/tests/
DBuild1 tests-y += main.o
2 tests-y += test-evsel.o
3 tests-y += test-evlist.o
4 tests-y += test-cpumap.o
5 tests-y += test-threadmap.o
/Linux-v5.15/drivers/net/ethernet/sfc/falcon/
Dselftest.c96 static int ef4_test_phy_alive(struct ef4_nic *efx, struct ef4_self_tests *tests) in ef4_test_phy_alive() argument
102 tests->phy_alive = rc ? -1 : 1; in ef4_test_phy_alive()
108 static int ef4_test_nvram(struct ef4_nic *efx, struct ef4_self_tests *tests) in ef4_test_nvram() argument
117 tests->nvram = rc ? -1 : 1; in ef4_test_nvram()
131 struct ef4_self_tests *tests) in ef4_test_interrupts() argument
138 tests->interrupt = -1; in ef4_test_interrupts()
144 tests->interrupt = 0; in ef4_test_interrupts()
167 tests->interrupt = 1; in ef4_test_interrupts()
173 struct ef4_self_tests *tests) in ef4_test_eventq_irq() argument
221 tests->eventq_dma[channel->channel] = dma_seen ? 1 : -1; in ef4_test_eventq_irq()
[all …]
/Linux-v5.15/drivers/net/ethernet/sfc/
Dselftest.c99 static int efx_test_phy_alive(struct efx_nic *efx, struct efx_self_tests *tests) in efx_test_phy_alive() argument
104 tests->phy_alive = rc ? -1 : 1; in efx_test_phy_alive()
109 static int efx_test_nvram(struct efx_nic *efx, struct efx_self_tests *tests) in efx_test_nvram() argument
118 tests->nvram = rc ? -1 : 1; in efx_test_nvram()
132 struct efx_self_tests *tests) in efx_test_interrupts() argument
139 tests->interrupt = -1; in efx_test_interrupts()
145 tests->interrupt = 0; in efx_test_interrupts()
168 tests->interrupt = 1; in efx_test_interrupts()
174 struct efx_self_tests *tests) in efx_test_eventq_irq() argument
222 tests->eventq_dma[channel->channel] = dma_seen ? 1 : -1; in efx_test_eventq_irq()
[all …]
/Linux-v5.15/tools/memory-model/scripts/
DREADME10 Run all litmus tests in the litmus-tests directory, checking
16 Run all litmus tests in the https://github.com/paulmckrcu/litmus
23 Run all litmus tests having .litmus.out files from previous
33 Compare output from two different runs of the same litmus tests,
34 with the absolute pathnames of the tests to run provided one
40 Run all litmus tests having no more than the specified number
53 For all new or updated litmus tests having no more than the
64 Run the litmus tests whose absolute pathnames are provided one
/Linux-v5.15/lib/kunit/
DKconfig6 tristate "KUnit - Enable support for unit tests"
9 Enables support for kernel unit tests (KUnit), a lightweight unit
10 testing and mocking framework for the Linux kernel. These tests are
31 Enables the unit tests for the KUnit test framework. These tests test
32 the KUnit test framework itself; the tests are both written using
49 tristate "All KUnit tests with satisfied dependencies"
51 Enables all KUnit tests, if they can be enabled.
52 KUnit tests run during boot and output the results to the debug log
57 For more information on KUnit and unit tests in general please refer
/Linux-v5.15/tools/testing/vsock/
DREADME3 These tests exercise net/vmw_vsock/ host<->guest sockets for VMware, KVM, and
6 The following tests are available:
12 to running tests:
14 1. Build the kernel, make headers_install, and build these tests.
15 2. Install the kernel and tests on the host.
16 3. Install the kernel and tests inside the guest.
/Linux-v5.15/crypto/async_tx/
Draid6test.c152 static int test(int disks, int *tests) in test() argument
184 (*tests)++; in test()
195 int tests = 0; in raid6_test() local
209 err += test(4, &tests); in raid6_test()
211 err += test(5, &tests); in raid6_test()
216 err += test(11, &tests); in raid6_test()
217 err += test(12, &tests); in raid6_test()
225 err += test(24, &tests); in raid6_test()
227 err += test(NDISKS, &tests); in raid6_test()
231 tests, err, err == 1 ? "" : "s"); in raid6_test()
/Linux-v5.15/tools/memory-model/
DREADME12 the state space of small litmus tests.
66 explore the state space of small litmus tests. Documentation describing
68 tests is available in tools/memory-model/Documentation/litmus-tests.txt.
70 Example litmus tests may be found in the Linux-kernel source tree:
72 tools/memory-model/litmus-tests/
73 Documentation/litmus-tests/
75 Several thousand more example litmus tests are available here:
81 Documentation describing litmus tests and now to use them may be found
84 tools/memory-model/Documentation/litmus-tests.txt
92 $ herd7 -conf linux-kernel.cfg litmus-tests/SB+fencembonceonces.litmus
[all …]
/Linux-v5.15/tools/testing/kunit/test_data/
Dtest_skip_all_tests.log5 ok 1 - string_stream_test_empty_on_creation # SKIP all tests skipped
6 ok 2 - string_stream_test_not_empty_after_add # SKIP all tests skipped
7 ok 3 - string_stream_test_get_string # SKIP all tests skipped
12 ok 1 - example_simple_test # SKIP all tests skipped
/Linux-v5.15/tools/lib/perf/
DMakefile141 …*.o *~ *.a *.so *.so.$(VERSION) *.so.$(LIBPERF_VERSION) .*.d .*.cmd tests/*.o LIBPERF-CFLAGS $(LIB…
144 TESTS_IN = tests-in.o
146 TESTS_STATIC = $(OUTPUT)tests-static
147 TESTS_SHARED = $(OUTPUT)tests-shared
150 $(Q)$(MAKE) $(build)=tests
158 make-tests: libs $(TESTS_SHARED) $(TESTS_STATIC)
160 tests: make-tests target
211 .PHONY: all install clean tests FORCE
/Linux-v5.15/tools/testing/selftests/arm64/signal/
DREADME15 executable is used for each test since many tests complete successfully
20 - New tests can be simply defined in testcases/ dir providing a proper struct
27 - 'mangle_' tests: a real signal (SIGUSR1) is raised and used as a trigger
31 - 'fake_sigreturn_' tests: a brand new custom artificial sigframe structure
33 real signal return. This kind of tests does not use a trigger usually and
36 - Most of these tests are successfully passing if the process gets killed by
38 kind of tests it is extremely easy in fact to end-up injecting other
40 be really sure that the tests are really addressing what they are meant
51 - a sanity mechanism to be used in 'fake_sigreturn_'-alike tests: enabled by

12345678910>>...15