Searched full:run (Results 1 – 25 of 743) sorted by relevance
12345678910>>...30
| /Documentation/dev-tools/kunit/ |
| D | run_wrapper.rst | 7 We can either run KUnit tests using kunit_tool or can run tests
8 manually, and then use kunit_tool to parse the results. To run tests
10 As long as we can build the kernel, we can run KUnit.
15 Run command:
19 ./tools/testing/kunit/kunit.py run
33 ./tools/testing/kunit/kunit.py run --timeout=30 --jobs=`nproc --all`
35 - ``--timeout`` sets a maximum amount of time for tests to run.
45 tests we want to run independently, or if we want to use pre-defined
53 ./tools/testing/kunit/kunit.py run --kunitconfig=fs/ext4/.kunitconfig
55 To view kunit_tool flags (optional command-line arguments), run:
[all …]
|
| D | run_manual.rst | 4 Run Tests without kunit_tool
8 with other systems, or run tests on real hardware), we can
18 KUnit tests can run without kunit_tool. This can be useful, if:
21 - Need to run on real hardware (or using an emulator/VM kunit_tool
38 Once we have built our kernel (and/or modules), it is simple to run
39 the tests. If the tests are built-in, they will run automatically on the
43 If the tests are built as modules, they will run when the module is
75 Run Tests After Kernel Has Booted
78 You can use the debugfs filesystem to trigger built-in tests to run after
79 boot. To run the test suite, you can use the following command to write to
[all …]
|
| D | start.rst | 8 teaching how to run existing tests and then how to write a simple test case,
14 build the kernel, you can run KUnit.
20 can run kunit_tool:
24 ./tools/testing/kunit/kunit.py run
28 "The source tree is not clean, please run 'make ARCH=um mrproper'"
59 Selecting which tests to run
64 you can select which tests to run by:
67 - `Filtering tests by name`_ to select specifically which compiled tests to run.
72 If you didn't run ``kunit.py run`` yet, you can generate it by running:
91 options required to run the desired tests, including their dependencies.
[all …]
|
| D | running_tips.rst | 7 Using ``kunit.py run`` ("kunit tool")
18 ( cd "$(git rev-parse --show-toplevel)" && ./tools/testing/kunit/kunit.py run "$@" )
22 Early versions of ``kunit.py`` (before 5.6) didn't work unless run from
28 ``kunit.py run`` accepts an optional glob argument to filter tests. The format
31 Say that we wanted to run the sysctl tests, we could do so via:
36 $ ./tools/testing/kunit/kunit.py run 'sysctl*'
43 $ ./tools/testing/kunit/kunit.py run 'sysctl*.*write*'
55 ``kunit.py run`` (along with ``build``, and ``config``) supports a
56 ``--kunitconfig`` flag. So if you have a set of tests that you want to run on a
64 $ ./tools/testing/kunit/kunit.py run --kunitconfig=lib/kunit/.kunitconfig
[all …]
|
| D | faq.rst | 21 testing frameworks require tests to be written in userspace and run on the
37 In short, yes, you can run KUnit on other architectures, but it might require
73 1. Run ``./tools/testing/kunit/kunit.py run`` with the ``--raw_output``
76 2. Instead of running ``kunit.py run``, try running ``kunit.py config``,
79 can run it manually against ``stdin`` or a file with ``kunit.py parse``.)
85 the host has KASLR enabled. (On older host kernels, you may need to run
89 around, so you can see what config was used after running ``kunit.py run``.
92 re-run kunit_tool.
93 5. Try to run ``make ARCH=um defconfig`` before running ``kunit.py run``. This
|
| /Documentation/dev-tools/ |
| D | kselftest.rst | 7 paths in the kernel. Tests are intended to be run after building, installing
10 Kselftest from mainline can be run on older stable kernels. Running tests
11 from mainline offers the best coverage. Several test rings run mainline
14 able to run that test on an older kernel. Hence, it is important to keep
25 to run the full range of hot-plug tests. In default mode, hot-plug tests run
27 run on a single cpu as opposed to all hotplug capable cpus, and memory
28 hotplug test is run on 2% of hotplug capable memory instead of 10%.
30 kselftest runs as a userspace process. Tests that can be written/run in
32 run in kernel space may wish to use a `Test Module`_.
34 Running the selftests (hotplug tests are run in limited mode)
[all …]
|
| /Documentation/driver-api/dmaengine/ |
| D | dmatest.rst | 43 % modprobe dmatest timeout=2000 iterations=1 channel=dma0chan0 run=1
51 % echo 1 > /sys/module/dmatest/parameters/run
55 dmatest.timeout=2000 dmatest.iterations=1 dmatest.channel=dma0chan0 dmatest.run=1
65 % echo 1 > /sys/module/dmatest/parameters/run
75 begin execution when the run parameter is set to 1.
84 pending thread is started once run is to 1.
90 % cat /sys/module/dmatest/parameters/run
92 To wait for test completion userspace can poll 'run' until it is false, or use
94 initialization to pause until a test run has completed, while reading
102 % modprobe dmatest run=1 iterations=42 wait=1
[all …]
|
| /Documentation/RCU/ |
| D | torture.rst | 13 be loaded to run a torture test. The test periodically outputs
168 powerpc. By default, it will run the series of tests specified by
177 would use up to 43 CPUs to run tests concurrently, which as of v5.4 would
180 the sixteen kernels). The "--dryrun sched" argument will not run tests,
185 Not all changes require that all scenarios be run. For example, a change
186 to Tree SRCU might run only the SRCU-N and SRCU-P scenarios using the
188 Large systems can run multiple copies of the full set of scenarios,
189 for example, a system with 448 hardware threads can run five instances
194 Alternatively, such a system can run 56 concurrent instances of a single
211 Note that --gdb limits you to one scenario per kvm.sh run and requires
[all …]
|
| /Documentation/gpu/ |
| D | vkms.rst | 15 To check if VKMS is loaded, run::
62 The tests need to be run without a compositor, so you need to switch to text
71 Once you are in text only mode, you can run tests using the --device switch
73 to test. IGT_DEVICE can also be used with the run-test.sh script to run the
78 sudo IGT_DEVICE="sys:/sys/devices/platform/vkms" ./scripts/run-tests.sh -t <name of test>
81 we can run the kms_writeback test::
85 sudo IGT_DEVICE="sys:/sys/devices/platform/vkms" ./scripts/run-tests.sh -t kms_writeback
87 You can also run subtests if you do not want to run the entire test::
89 …sudo ./build/tests/kms_flip --run-subtest basic-plain-flip --device "sys:/sys/devices/platform/vkm…
90 …sudo IGT_DEVICE="sys:/sys/devices/platform/vkms" ./build/tests/kms_flip --run-subtest basic-plain-…
|
| /Documentation/scheduler/ |
| D | sched-rt-group.rst | 53 in a given period. We allocate this "run time" for each real-time group which
56 Any time not allocated to a real-time group will be used to run normal priority
57 tasks (SCHED_OTHER). Any allocated run time not used will also be picked up by
63 time dedicated for the graphics. We can then give this group a run time of 0.8
66 This way the graphics group will have a 0.04s period with a 0.032s run time
69 0.00015s. So this group can be scheduled with a period of 0.005s and a run time
104 * A run time of -1 specifies runtime == period, ie. no limit.
112 SCHED_OTHER (non-RT tasks). These defaults were chosen so that a run-away
117 period from /proc/sys/kernel/sched_rt_period_us and a run time of 0. If you
123 not be able to run real-time tasks as any user other than root until you have
[all …]
|
| D | sched-eevdf.rst | 14 runnable tasks with the same priority. To do so, it assigns a virtual run
26 on virtual run time (VRT). This prevents tasks from exploiting the system
28 remains on the run queue but marked for "deferred dequeue," allowing its
|
| D | sched-util-clamp.rst | 23 system run at a certain performance point.
59 can run at. This constraint helps reserve resources for important tasks, like
65 1. The big cores are free to run top-app tasks immediately. top-app
68 2. They don't run on a power hungry core and drain battery even if they
85 On the other hand, a busy task for instance that requires to run at maximum
102 In the SCHED_FIFO/RR case, uclamp gives the option to run RT tasks at any
104 can be useful on general purpose systems that run on battery powered devices.
107 run at a constant frequency to combat undeterministic DVFS rampup delays.
128 and the scheduler needs to select a suitable CPU for it to run on.
131 performance point for a task to run on, it must be able to influence the
[all …]
|
| /Documentation/devicetree/bindings/regulator/ |
| D | rohm,bd71815-regulator.yaml | 54 rohm,dvs-run-voltage:
56 PMIC "RUN" state voltage in uV when PMIC HW states are used. See
58 regulator should be disabled at RUN state.
93 # (RUN /CLEAN according to data-sheet) and non operational states
99 # Bucks 3-5 and ldos 1-5 support setting the RUN state voltage here.
100 # Given RUN voltage is used at all states if regulator is enabled at
106 # for each of the HW states (RUN/SNVS/SUSPEND/LPSR). HW defaults can
|
| /Documentation/networking/devlink/ |
| D | devlink-selftests.rst | 11 The ``devlink-selftests`` command should be run with a mask indicating
25 flash. This particular test helps to run a flash selftest on the device.
38 $ devlink dev selftests run DEV id flash
|
| /Documentation/rust/ |
| D | testing.rst | 24 These tests can be run via KUnit. For example via ``kunit_tool`` (``kunit.py``)
27 ./tools/testing/kunit/kunit.py run --make_options LLVM=1 --arch x86_64 --kconfig_add CONFIG_RUST=y
29 Alternatively, KUnit can run them as kernel built-in at boot. Refer to
63 In userspace, the tests are collected and run via ``rustdoc``. Using the tool
70 run against a built kernel.
124 actually failed. Additionally, doctests are not run for nonpublic functions.
129 Additionally, there are the ``#[test]`` tests. These can be run using the
|
| /Documentation/arch/powerpc/ |
| D | elfnote.rst | 24 Indicate that the powerpc kernel binary knows how to run in an
29 being run on a machine with ultravisor, the kernel will probably crash
34 the kernel from being run if the PowerPC ultravisor capability doesn't exist
|
| /Documentation/admin-guide/hw-vuln/ |
| D | core-scheduling.rst | 37 tasks that are not in the same group never run simultaneously on a core, while
109 in their individual run queues. If a task with same cookie is not available,
116 have tasks on its on runqueue to run, however it will still have to run idle.
127 task. If a sibling does not have a trusted task to run, it will be forced idle
128 by the scheduler (idle thread is scheduled to run).
130 When the highest priority task is selected to run, a reschedule-IPI is sent to
166 Core scheduling tries to guarantee that only trusted tasks run concurrently on a
167 core. But there could be small window of time during which untrusted tasks run
173 Core scheduling selects only trusted tasks to run together. IPI is used to notify
179 starts to run and this is a possibility for data leak.
[all …]
|
| D | vmscape.rst | 38 Kernel tracks when a CPU has run a potentially malicious guest and issues an
39 IBPB before the first exit to userspace after VM-exit. If userspace did not run
45 context switch time, while the userspace VMM can run after a VM-exit without a
86 run a potentially malicious guest and issues an IBPB before the first
|
| /Documentation/trace/coresight/ |
| D | coresight-perf.rst | 17 This would run some test binary (testbinary) until it exits and record
84 When you run perf test, it will do a lot of self tests. Some of those
86 generally would run perf test from the tools/perf directory in the
102 These perf record tests will not run if the tool binaries do not exist
121 that the amount of data collected can vary a lot per run of perf test.
122 If you wish to see how this changes over time, simply run perf test
132 Be aware that some of these tests take quite a while to run, specifically
|
| /Documentation/admin-guide/ |
| D | lockup-watchdogs.rst | 10 details), without giving other tasks a chance to run. The current
20 details), without letting other interrupts have a chance to run.
70 boot argument. If we allowed the watchdog to run by default on
71 the "nohz_full" cores, we would have to run timer ticks to activate
77 to continue to run on the housekeeping (non-tickless) cores means
|
| /Documentation/driver-api/media/drivers/ |
| D | pxa_camera.rst | 45 +-> | QCI: stop | ------------------> | QCI: run | <------------+
55 | | QCI: run | +-----> | QCI: run | <-+ |
56 | | DMA: stop | / | DMA: run | | |
65 +-- | QCI: run | | QCI: run | --+ |
66 | DMA: run | | DMA: run | |
74 | QCI: run | | QCI: stop | --------------+
75 | DMA: run | | DMA: stop |
85 - "DMA: run" means at least 1 DMA channel is still running
|
| /Documentation/translations/zh_CN/admin-guide/mm/ |
| D | ksm.rst | 91 置：首先将接口`run` 设置为2从而对页进行去合并，然后在修改
92 ``merge_across_nodes`` 后再将‘run’又设置为1，以根据新设置来重新合并。
96 run
98 * 设置为1可运行ksmd，例如， ``echo 1 > /sys/kernel/mm/ksm/run`` ，
|
| /Documentation/translations/zh_TW/admin-guide/mm/ |
| D | ksm.rst | 91 置：首先將接口`run` 設置爲2從而對頁進行去合併，然後在修改
92 ``merge_across_nodes`` 後再將‘run’又設置爲1，以根據新設置來重新合併。
96 run
98 * 設置爲1可運行ksmd，例如， ``echo 1 > /sys/kernel/mm/ksm/run`` ，
|
| /Documentation/ABI/testing/ |
| D | sysfs-kernel-mm-ksm | 13 What: /sys/kernel/mm/ksm/run
36 run: write 0 to disable ksm, read 0 while ksm is disabled.
38 - write 1 to run ksm, read 1 while ksm is running.
|
| /Documentation/watchdog/ |
| D | pcwd-watchdog.rst | 13 the WDT card does, only it doesn't require an IRQ to run. Furthermore,
29 to run the program with an "&" to run it in the background!)
|
12345678910>>...30