Searched refs:kselftest (Results 1 – 25 of 26) sorted by relevance
12
| /linux-5.19.10/Documentation/translations/zh_CN/dev-tools/ |
| D | testing-overview.rst | 19 大多数内核测试都是用kselftest或KUnit框架之一编写的。它们都让运行测试
23 kselftest。
25 KUnit和kselftest的区别
50 kselftest（Documentation/dev-tools/kselftest.rst），相对来说，大量用
54 如生成进程之类）。然而，从kselftest直接调用内核函数是不行的。这也就
56 户空间的内核功能才能使用kselftest来测试。为此，有些测试包含了一个伴
60 kselftest也因此非常适合于全部功能的测试，因为这些功能会将接口暴露到
64 比如，一个新的系统调用应该伴随有新的kselftest测试。
105 这些工具倾向于对内核进行整体测试，并且不像kselftest和KUnit一样“传递”。
106 它们可以通过在启用这些工具时运行内核测试以与kselftest或KUnit结合起来：
[all …]
|
| D | index.rst | 39 - kselftest
|
| /linux-5.19.10/tools/testing/selftests/ |
| D | Makefile | 134 BUILD := $(abs_objtree)/kselftest
228 TEST_LIST := $(INSTALL_PATH)/kselftest-list.txt
233 mkdir -p $(INSTALL_PATH)/kselftest
234 install -m 744 kselftest/module.sh $(INSTALL_PATH)/kselftest/
235 install -m 744 kselftest/runner.sh $(INSTALL_PATH)/kselftest/
236 install -m 744 kselftest/prefix.pl $(INSTALL_PATH)/kselftest/
265 TAR_PATH = $(abspath ${INSTALL_PATH}/kselftest-packages/kselftest.tar${FORMAT})
267 @mkdir -p ${INSTALL_PATH}/kselftest-packages/
268 @tar caf ${TAR_PATH} --exclude=kselftest-packages -C ${INSTALL_PATH} .
|
| D | gen_kselftest_tar.sh | 44 install_name=kselftest
51 (cd "$install_work"; tar $copts "$dest"/kselftest${ext} $install_name)
|
| D | run_kselftest.sh | 8 TESTS="$BASE_DIR"/kselftest-list.txt
16 . ./kselftest/runner.sh
|
| D | lib.mk | 96 . $(selfdir)/kselftest/runner.sh; \
171 LOCAL_HDRS += $(selfdir)/kselftest_harness.h $(selfdir)/kselftest.h
|
| /linux-5.19.10/Documentation/dev-tools/ |
| D | kselftest.rst | 12 kselftest suite on stable releases. The reason is that when a new test
21 https://kselftest.wiki.kernel.org/
30 kselftest runs as a userspace process. Tests that can be written/run in
47 $ make kselftest
59 $ make O=/tmp/kselftest kselftest
63 $ export KBUILD_OUTPUT=/tmp/kselftest; make kselftest
74 To run kselftest with summary option enabled ::
76 $ make summary=1 kselftest
90 $ make TARGETS="size timers" kselftest
94 $ make O=/tmp/kselftest TARGETS="size timers" kselftest
[all …]
|
| D | testing-overview.rst | 16 The bulk of kernel tests are written using either the kselftest or KUnit
22 parts of the kernel — then you'll want to use KUnit or kselftest.
25 The Difference Between KUnit and kselftest
47 kselftest (Documentation/dev-tools/kselftest.rst), on the other hand, is
53 However, it's not possible to call kernel functions directly from kselftest.
55 (e.g. by a syscall, device, filesystem, etc.) can be tested with kselftest. To
60 kselftest is therefore suited well to tests of whole features, as these will
64 For example, all new system calls should be accompanied by kselftest tests.
111 kselftest or KUnit tests. They can be combined with KUnit or kselftest by
115 Some of these tools integrate with KUnit or kselftest and will
|
| D | index.rst | 33 kselftest
|
| D | ktap.rst | 103 to "TODO", above, and is used by some kselftest tests.
308 - The kselftest documentation:
309 Documentation/dev-tools/kselftest.rst
|
| /linux-5.19.10/tools/testing/selftests/arm64/ |
| D | README | 11 $ make TARGETS=arm64 kselftest-clean
12 $ make TARGETS=arm64 kselftest
25 Documentation/dev-tools/kselftest.rst
|
| /linux-5.19.10/tools/testing/selftests/resctrl/ |
| D | README | 15 resctrl_tests can be run with or without kselftest framework.
31 Using kselftest framework will run all supported tests within resctrl_tests:
35 More details about kselftest framework can be found in
36 Documentation/dev-tools/kselftest.rst.
|
| /linux-5.19.10/tools/testing/selftests/arm64/fp/ |
| D | README | 1 This directory contains a mix of tests integrated with kselftest and
4 kselftest tests
10 Running the non-kselftest tests
|
| /linux-5.19.10/tools/testing/selftests/lib/ |
| D | bitmap.sh | 3 $(dirname $0)/../kselftest/module.sh "bitmap" test_bitmap
|
| D | printf.sh | 4 $(dirname $0)/../kselftest/module.sh "printf" test_printf
|
| D | scanf.sh | 4 $(dirname $0)/../kselftest/module.sh "scanf" test_scanf
|
| D | strscpy.sh | 3 $(dirname $0)/../kselftest/module.sh "strscpy*" test_strscpy
|
| D | prime_numbers.sh | 4 $(dirname $0)/../kselftest/module.sh "prime numbers" prime_numbers selftest=65536
|
| /linux-5.19.10/tools/testing/selftests/filesystems/binderfs/ |
| D | Makefile | 6 binderfs_test: binderfs_test.c ../../kselftest.h ../../kselftest_harness.h
|
| /linux-5.19.10/tools/testing/selftests/uevent/ |
| D | Makefile | 11 uevent_filtering: uevent_filtering.c ../kselftest.h ../kselftest_harness.h
|
| /linux-5.19.10/tools/testing/selftests/kselftest/ |
| D | runner.sh | 30 "$BASE_DIR"/kselftest/prefix.pl
|
| /linux-5.19.10/Documentation/dev-tools/kunit/ |
| D | faq.rst | 7 How is this different from Autotest, kselftest, and so on?
9 KUnit is a unit testing framework. Autotest, kselftest (and some others) are
22 kernel under test. This is true for Autotest, kselftest, and some others,
|
| /linux-5.19.10/ |
| D | Makefile | 1352 PHONY += kselftest
1353 kselftest: target
1356 kselftest-%: FORCE
1359 PHONY += kselftest-merge
1360 kselftest-merge:
|
| /linux-5.19.10/Documentation/bpf/ |
| D | bpf_devel_QA.rst | 437 See the kernels selftest `Documentation/dev-tools/kselftest.rst`_
664 .. _Documentation/dev-tools/kselftest.rst:
665 https://www.kernel.org/doc/html/latest/dev-tools/kselftest.html
|
| /linux-5.19.10/Documentation/process/ |
| D | handling-regressions.rst | 552 time, which we then sometimes even add tests for in our kselftest
|
12