Home
last modified time | relevance | path

Searched refs:kselftest (Results 1 – 25 of 39) sorted by relevance

12

/linux-6.12.1/Documentation/translations/zh_TW/dev-tools/
Dtesting-overview.rst19 大多數內核測試都是用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 …]
Dindex.rst41 - kselftest
/linux-6.12.1/Documentation/translations/zh_CN/dev-tools/
Dtesting-overview.rst19 大多数内核测试都是用kselftest或KUnit框架之一编写的。它们都让运行测试
23 kselftest。
25 KUnit和kselftest的区别
50 kselftest（Documentation/dev-tools/kselftest.rst），相对来说，大量用
54 如生成进程之类）。然而，从kselftest直接调用内核函数是不行的。这也就
56 户空间的内核功能才能使用kselftest来测试。为此，有些测试包含了一个伴
60 kselftest也因此非常适合于全部功能的测试，因为这些功能会将接口暴露到
64 比如，一个新的系统调用应该伴随有新的kselftest测试。
107 这些工具倾向于对内核进行整体测试，并且不像kselftest和KUnit一样“传递”。
108 它们可以通过在启用这些工具时运行内核测试以与kselftest或KUnit结合起来：
[all …]
Dindex.rst38 - kselftest
/linux-6.12.1/tools/testing/selftests/
DMakefile177 BUILD := $(abs_objtree)/kselftest
249 TEST_LIST := $(INSTALL_PATH)/kselftest-list.txt
254 mkdir -p $(INSTALL_PATH)/kselftest
255 install -m 744 kselftest/module.sh $(INSTALL_PATH)/kselftest/
256 install -m 744 kselftest/runner.sh $(INSTALL_PATH)/kselftest/
257 install -m 744 kselftest/prefix.pl $(INSTALL_PATH)/kselftest/
258 install -m 744 kselftest/ktap_helpers.sh $(INSTALL_PATH)/kselftest/
259 install -m 744 kselftest/ksft.py $(INSTALL_PATH)/kselftest/
291 TAR_PATH = $(abspath ${INSTALL_PATH}/kselftest-packages/kselftest.tar${FORMAT})
293 @mkdir -p ${INSTALL_PATH}/kselftest-packages/
[all …]
Dgen_kselftest_tar.sh44 install_name=kselftest
51 (cd "$install_work"; tar $copts "$dest"/kselftest${ext} $install_name)
Drun_kselftest.sh8 TESTS="$BASE_DIR"/kselftest-list.txt
16 . ./kselftest/runner.sh
Dlib.mk105 . $(selfdir)/kselftest/runner.sh; \
219 LOCAL_HDRS += $(selfdir)/kselftest_harness.h $(selfdir)/kselftest.h
/linux-6.12.1/Documentation/dev-tools/
Dkselftest.rst12 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
48 $ make kselftest
60 $ make O=/tmp/kselftest kselftest
64 $ export KBUILD_OUTPUT=/tmp/kselftest; make kselftest
75 To run kselftest with summary option enabled ::
77 $ make summary=1 kselftest
91 $ make TARGETS="size timers" kselftest
95 $ make O=/tmp/kselftest TARGETS="size timers" kselftest
[all …]
Dtesting-overview.rst16 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.
113 kselftest or KUnit tests. They can be combined with KUnit or kselftest by
117 Some of these tools integrate with KUnit or kselftest and will
Dindex.rst32 kselftest
/linux-6.12.1/tools/testing/selftests/arm64/
DREADME11 $ make TARGETS=arm64 kselftest-clean
12 $ make TARGETS=arm64 kselftest
25 Documentation/dev-tools/kselftest.rst
/linux-6.12.1/tools/testing/selftests/resctrl/
DREADME15 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-6.12.1/tools/testing/selftests/arm64/fp/
DREADME1 This directory contains a mix of tests integrated with kselftest and
4 kselftest tests
10 Running the non-kselftest tests
/linux-6.12.1/tools/testing/selftests/kselftest/
Drunner.sh32 "$BASE_DIR"/kselftest/prefix.pl
153 source $BASE_DIR/kselftest/runner.sh
/linux-6.12.1/tools/testing/selftests/lib/
Dbitmap.sh3 $(dirname $0)/../kselftest/module.sh "bitmap" test_bitmap
Dprintf.sh4 $(dirname $0)/../kselftest/module.sh "printf" test_printf
Dscanf.sh4 $(dirname $0)/../kselftest/module.sh "scanf" test_scanf
Dprime_numbers.sh4 $(dirname $0)/../kselftest/module.sh "prime numbers" prime_numbers selftest=65536
/linux-6.12.1/tools/testing/selftests/net/packetdrill/
DMakefile6 ../../kselftest/ktap_helpers.sh
/linux-6.12.1/tools/testing/selftests/uevent/
DMakefile11 uevent_filtering: uevent_filtering.c ../kselftest.h ../kselftest_harness.h
/linux-6.12.1/tools/testing/selftests/dt/
Dtest_unprobed_devices.sh18 source "${DIR}"/../kselftest/ktap_helpers.sh
/linux-6.12.1/tools/testing/selftests/power_supply/
Dtest_power_supply_properties.sh13 . "${DIR}"/../kselftest/ktap_helpers.sh
/linux-6.12.1/Documentation/dev-tools/kunit/
Dfaq.rst7 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-6.12.1/tools/testing/selftests/cpufreq/
Dmain.sh11 source "${DIR}"/../kselftest/ktap_helpers.sh

12