Searched full:run (Results 1 – 25 of 582) sorted by relevance
12345678910>>...24
| /Documentation/dev-tools/ |
| D | kselftest.rst | 7 paths in the kernel. Tests are intended to be run after building, installing
17 to run the full range of hot-plug tests. In default mode, hot-plug tests run
19 run on a single cpu as opposed to all hotplug capable cpus, and memory
20 hotplug test is run on 2% of hotplug capable memory instead of 10%.
22 kselftest runs as a userspace process. Tests that can be written/run in
24 run in kernel space may wish to use a `Test Module`_.
26 Running the selftests (hotplug tests are run in limited mode)
33 To run the tests::
37 To build and run the tests with a single command, use::
60 The above commands by default run the tests and print full pass/fail report.
[all …]
|
| D | gcov.rst | 23 associated code is never run?)
42 larger and run slower. Also CONFIG_GCOV_PROFILE_ALL may not be supported
103 Kernel modules may contain cleanup code which is only run during
115 At run-time, a user can also choose to discard data for an unloaded
123 box for setups where kernels are built and run on the same machine. In
127 a) gcov is run on the TEST machine
146 b) gcov is run on the BUILD machine
|
| /Documentation/driver-api/dmaengine/ |
| D | dmatest.rst | 33 % modprobe dmatest timeout=2000 iterations=1 channel=dma0chan0 run=1
41 % echo 1 > /sys/module/dmatest/parameters/run
45 dmatest.timeout=2000 dmatest.iterations=1 dmatest.channel=dma0chan0 dmatest.run=1
55 % echo 1 > /sys/module/dmatest/parameters/run
65 begin execution when the run parameter is set to 1.
74 pending thread is started once run is to 1.
80 % cat /sys/module/dmatest/parameters/run
82 To wait for test completion userpace can poll 'run' until it is false, or use
84 initialization to pause until a test run has completed, while reading
92 % modprobe dmatest run=1 iterations=42 wait=1
[all …]
|
| /Documentation/dev-tools/kunit/ |
| D | index.rst | 28 writing unit tests. Tests written against KUnit will run on kernel boot if
51 KUnit tests can be run on most architectures, and most tests are architecture
52 independent. All built-in KUnit tests run on kernel startup. Alternatively,
53 KUnit and KUnit tests can be built as modules and tests will run when the test
58 KUnit can also run tests without needing a virtual machine or actual
64 KUnit is fast. Excluding build time, from invocation to completion KUnit can run
66 deal to some people, but having such fast and easy to run tests fundamentally
78 difficult to write, and require a special setup or special hardware to run,
79 then you wait a lot longer to write tests, and you wait a lot longer to run
82 fast, you run them all the time, every time you make a change, and every time
[all …]
|
| D | kunit-tool.rst | 15 kunit_tool addresses the problem of being able to run tests without needing a
18 compiles the kernel as a standalone Linux executable that can be run like any
38 ./tools/testing/kunit/kunit.py run
44 ./tools/testing/kunit/kunit.py run --timeout=30 --jobs=`nproc --all`
46 - ``--timeout`` sets a maximum amount of time to allow tests to run.
53 For a list of all the flags supported by kunit_tool, you can run:
57 ./tools/testing/kunit/kunit.py run --help
|
| D | faq.rst | 21 tests to be written in userspace and run on the kernel under test; this is true
37 In short, this means that, yes, you can run KUnit on other architectures, but
71 1. Try running ``./tools/testing/kunit/kunit.py run`` with the ``--raw_output``
74 2. Instead of running ``kunit.py run``, try running ``kunit.py config``,
77 can run it manually against stdin or a file with ``kunit.py parse``.)
83 has KASLR enabled. (On older host kernels, you may need to run ``setarch
87 around, so you can see what config was used after running ``kunit.py run``.
90 re-run kunit_tool.
91 5. Try to run ``make ARCH=um defconfig`` before running ``kunit.py run``. This
|
| D | start.rst | 10 the kernel, you can run KUnit.
17 The wrapper can be run with:
21 ./tools/testing/kunit/kunit.py run
28 If you want to run a specific set of tests (rather than those listed in the
67 ./tools/testing/kunit/kunit.py run
70 You may want to run ``make mrproper`` first.
80 followed by a list of tests that are run. All of them should be passing.
108 module will be run when the module is loaded.
114 Build and run your kernel as usual. Test output will be written to the kernel
215 Now you can run the test:
[all …]
|
| D | usage.rst | 204 In the above example the test suite, ``example_test_suite``, would run the test
212 A test case will only be run if it is associated with a test suite.
215 test suite in a special linker section so that it can be run by KUnit either
226 In practice, this is only possible by being able to control what code gets run
462 are instances where being able to run architecture-specific code or test
473 when run under UML may not always do so on real hardware.
475 provide a hermetic environment to run tests; however, it cannot manage state
481 None of these are reasons not to run your KUnit tests on real hardware; they are
493 your kunitconfig, your Kconfig options for the tests you would like to run, and
503 If you wanted to run this test on an x86 VM, you might add the following config
[all …]
|
| /Documentation/scheduler/ |
| D | sched-rt-group.rst | 53 in a given period. We allocate this "run time" for each realtime group which
56 Any time not allocated to a realtime 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
102 * A run time of -1 specifies runtime == period, ie. no limit.
110 SCHED_OTHER (non-RT tasks). These defaults were chosen so that a run-away
115 period from /proc/sys/kernel/sched_rt_period_us and a run time of 0. If you
121 not be able to run realtime tasks as any user other than root until you have
[all …]
|
| /Documentation/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/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 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
230 If a run contains failures, the number of buildtime and runtime failures
[all …]
|
| /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/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/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!)
|
| /Documentation/devicetree/bindings/arm/freescale/ |
| D | fsl,imx7ulp-pm.yaml | 14 the MCU into and out of all stop and run power modes. Specifically, it
20 Standby modes for either Cortex family. Run, Wait, and Stop are the
|
| /Documentation/leds/ |
| D | ledtrig-transient.rst | 36 that are active at the time driver gets suspended, continue to run, without
114 allow user app to set the time once and activate it to run it once for the
123 any, continues to run for the specified time.
126 continues to run for the specified time.
150 echo 1 > activate - start timer = duration to run once
151 echo 1 > activate - start timer = duration to run once
|
| D | leds-lp5521.rst | 23 There are two ways to run LED patterns.
31 disabled, load, run
40 echo "run" > engine3_mode
|
| D | leds-lp55xx.rst | 70 To load and run the pattern, the programming sequence is following.
75 (4) Mode change to run
90 For example, run blinking pattern in engine #1 of LP5521::
98 For example, run blinking pattern in engine #3 of LP55231
134 To run programmed pattern, 'run_engine' attribute should be enabled.
217 Then, mode_1 and mode_2 can be run via through the sysfs::
|
| /Documentation/virt/ |
| D | paravirt_ops.rst | 12 allows a single kernel binary to run on all supported execution environments
17 functionalities in various areas. pv-ops allows for optimizations at run
|
| /Documentation/arm64/ |
| D | perf.rst | 23 The kernel runs at EL2 with VHE and EL1 without. Guest kernels always run
54 The KVM host may run at EL0 (userspace), EL1 (non-VHE kernel) and EL2 (VHE
57 The KVM guest may run at EL0 (userspace) and EL1 (kernel).
|
| /Documentation/devicetree/bindings/regulator/ |
| D | rohm,bd71847-regulator.yaml | 20 Note that if BD71847 starts at RUN state you probably want to use
56 rohm,dvs-run-voltage:
61 PMIC default "RUN" state voltage in uV. See below table for
83 # buck | dvs-run-voltage | dvs-idle-voltage | dvs-suspend-voltage
|
| /Documentation/driver-api/early-userspace/ |
| D | early_userspace_support.rst | 11 run inside the kernel itself.
58 usr/gen_init_cpio utility (run 'usr/gen_init_cpio -h' to get the
134 final root filesystem, based on the root= option and optional init= to run
149 To maintain backwards compatibility, the /init binary will only run if it
151 init/main.c:init() will run prepare_namespace() to mount the final root
|
| /Documentation/admin-guide/media/ |
| D | lmedm04.rst | 17 and run:
30 and run:
46 and run:
|
| /Documentation/power/ |
| D | runtime_pm.rst | 79 the PM core that it is safe to run the ->runtime_suspend(), ->runtime_resume()
107 -EAGAIN, the PM core regards this as a fatal error and will refuse to run
119 should be enabled for all input devices put into low-power states at run time.
135 fatal error and will refuse to run the helper functions described in Section
259 - set if ->runtime_resume() is about to be run while ->runtime_suspend() is
270 power manage the device at run time via the /sys/devices/.../power/control
319 then run pm_runtime_autosuspend(dev) and return its result
372 - increment the device's usage counter, run pm_request_resume(dev) and
376 - increment the device's usage counter, run pm_runtime_resume(dev) and
395 - decrement the device's usage counter; if the result is 0 then run
[all …]
|
12345678910>>...24