Home
last modified time | relevance | path

Searched +full:run +full:- +full:time (Results 1 – 25 of 1023) sorted by relevance

12345678910>>...41

/linux/tools/perf/scripts/python/
H A Dstat-cpi.py1 # SPDX-License-Identifier: GPL-2.0
10 def get_key(time, event, cpu, thread): argument
11 return "%d-%s-%d-%d" % (time, event, cpu, thread)
13 def store_key(time, cpu, thread): argument
14 if (time not in times):
15 times.append(time)
23 def store(time, event, cpu, thread, val, ena, run): argument
24 #print("event %s cpu %d, thread %d, time %d, val %d, ena %d, run %d" %
25 # (event, cpu, thread, time, val, ena, run))
27 store_key(time, cpu, thread)
[all …]
/linux/Documentation/scheduler/
H A Dsched-rt-group.rst2 Real-Time group scheduling
12 2.1 System-wide settings
28 resolution, or the time it takes to handle the budget refresh itself.
33 are real-time processes).
40 ---------------
42 Real-time scheduling is all about determinism, a group has to be able to rely on
43 the amount of bandwidth (eg. CPU time) being constant. In order to schedule
44 multiple groups of real-time tasks, each group must be assigned a fixed portion
45 of the CPU time available. Without a minimum guarantee a real-time group can
50 ----------------
[all …]
H A Dsched-util-clamp.rst1 .. SPDX-License-Identifier: GPL-2.0
23 system run at a certain performance point.
57 foreground, top-app, etc. Util clamp can be used to constrain how much
59 can run at. This constraint helps reserve resources for important tasks, like
60 the ones belonging to the currently active app (top-app group). Beside this
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
88 mobile devices where frames will drop due to slow response time to select the
89 higher frequency required for the tasks to finish their work in time. Setting
[all …]
H A Dsched-eevdf.rst9 of EEVDF proposed by Peter Zijlstra in 2023 [2-4]. More information
11 Documentation/scheduler/sched-design-CFS.rst.
13 Similarly to CFS, EEVDF aims to distribute CPU time equally among all
14 runnable tasks with the same priority. To do so, it assigns a virtual run
15 time to each task, creating a "lag" value that can be used to determine
16 whether a task has received its fair share of CPU time. In this way, a task
17 with a positive lag is owed CPU time, while a negative lag means the task
21 allows latency-sensitive tasks with shorter time slices to be prioritized,
25 tasks; but at the time of writing EEVDF uses a "decaying" mechanism based
26 on virtual run time (VRT). This prevents tasks from exploiting the system
[all …]
/linux/tools/perf/tests/shell/
H A Ddaemon.sh3 # SPDX-License-Identifier: GPL-2.0
55 local run=$3
82 if [ "${run}" != "${line_run}" ]; then
83 echo "FAILED: wrong run"
118 line=`perf daemon --config ${config} -x: | head -1`
123 trap - SIGINT SIGTERM
126 perf daemon stop --config ${config}
129 tail --pid=${pid} -f /dev/null
137 perf daemon start --config ${config}
146 state=`perf daemon ping --config ${config} --session ${session} | awk '{ print $1 }'`
[all …]
/linux/arch/mips/kvm/
H A Demulate.c23 #include <asm/cpu-info.h>
45 struct kvm_vcpu_arch *arch = &vcpu->arch; in kvm_compute_return_epc()
52 return -EINVAL; in kvm_compute_return_epc()
65 arch->gprs[insn.r_format.rd] = epc + 8; in kvm_compute_return_epc()
68 nextpc = arch->gprs[insn.r_format.rs]; in kvm_compute_return_epc()
71 return -EINVAL; in kvm_compute_return_epc()
84 if ((long)arch->gprs[insn.i_format.rs] < 0) in kvm_compute_return_epc()
93 if ((long)arch->gprs[insn.i_format.rs] >= 0) in kvm_compute_return_epc()
102 arch->gprs[31] = epc + 8; in kvm_compute_return_epc()
103 if ((long)arch->gprs[insn.i_format.rs] < 0) in kvm_compute_return_epc()
[all …]
/linux/Documentation/dev-tools/kunit/
H A Drun_manual.rst1 .. SPDX-License-Identifier: GPL-2.0
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:
20 - We have an existing kernel configuration to test.
21 - Need to run on real hardware (or using an emulator/VM kunit_tool
23 - Wish to integrate with some existing testing systems.
38 KUnit can be enabled or disabled at boot time, and this behavior is
42 verify that kunit.enable=1 at boot time.
44 Once we have built our kernel (and/or modules), it is simple to run
[all …]
H A Dstart.rst1 .. SPDX-License-Identifier: GPL-2.0
8 teaching how to run existing tests and then how to write a simple test case,
9 and covers common problems users face when using KUnit for the first time.
14 build the kernel, you can run KUnit.
20 can run kunit_tool:
22 .. code-block:: bash
24 ./tools/testing/kunit/kunit.py run
28 "The source tree is not clean, please run 'make ARCH=um mrproper'"
32 through the argument ``--build_dir``. Hence, before starting an
33 out-of-tree build, the source tree must be clean.
[all …]
/linux/tools/perf/Documentation/
H A Dperf-script.txt1 perf-script(1)
5 ----
6 perf-script - Read perf.data (created by perf record) and display trace output
9 ---
[all...]
/linux/tools/testing/selftests/kvm/
H A Ddirty_log_perf_test.c1 // SPDX-License-Identifier: GPL-2.0
13 #include <time.h>
23 /* How many host loops to run by default (one KVM_GET_DIRTY_LOG for each loop)*/
38 struct kvm_vcpu *vcpu = vcpu_args->vcpu; in vcpu_worker()
39 int vcpu_idx = vcpu_args->vcpu_idx; in vcpu_worker()
41 struct kvm_run *run; in vcpu_worker() local
48 run = vcpu->run; in vcpu_worker()
60 exit_reason_str(run->exit_reason)); in vcpu_worker()
68 pages_count += vcpu_args->pages; in vcpu_worker()
70 pr_debug("vCPU %d iteration %d dirty memory time: %ld.%.9lds\n", in vcpu_worker()
[all …]
/linux/tools/power/pm-graph/
H A DREADME8 pm-graph: suspend/resume/boot timing analysis tools
11 …Home Page: https://www.intel.com/content/www/us/en/developer/topic-technology/open/pm-graph/overvi…
13 Report bugs/issues at bugzilla.kernel.org Tools/pm-graph
14 - https://bugzilla.kernel.org/buglist.cgi?component=pm-graph&product=Tools
17 - Getting Started:
20 - Feature Summary:
21 https://www.intel.com/content/www/us/en/developer/topic-technology/open/pm-graph/features.html
23 - upstream version in git:
24 git clone https://github.com/intel/pm-graph/
27 - Overview
[all …]
/linux/tools/testing/memblock/
H A DREADME8 Memblock is a boot time memory allocator[1] that manages memory regions before
17 allocation functionalities of memblock. The main data structure of the boot time
18 memory allocator is initialized at the build time, so the checks here reuse its
22 As this project uses the actual memblock code and has to run in user space,
32 To run the tests, build the main target and run it:
36 A successful run produces no output. It is possible to control the behavior
38 append the `-v` options when you run the tests:
40 $ ./main -
[all...]
/linux/Documentation/leds/
H A Dledtrig-transient.rst8 to be off. The delay_on value specifies the time period an LED should stay
11 gets deactivated. There is no provision for one time activation to implement
36 that are active at the time driver gets suspended, continue to run, without
56 non-transient state. When driver gets suspended, irrespective of the transient
71 - duration allows setting timer value in msecs. The initial value is 0.
72 - activate allows activating and deactivating the timer specified by
75 - state allows user to specify a transient state to be held for the specified
79 - one shot timer activate mechanism.
90 - one shot timer value. When activate is set, duration value
96 - transient state to be held. It has two values 0 or 1. 0 maps
[all …]
/linux/tools/testing/ktest/
H A Dsample.conf5 # ktest.pl is run from. By default, ktest.pl will look for a file
45 # only enabling the ones you want to use for a current test run.
54 # MIN_CONFIG = /home/test/config-test1
57 # MIN_CONFIG = /home/test/config-default
61 # The above will run the first test with MIN_CONFIG set to
62 # /home/test/config-test-1. Then 10 tests will be executed
63 # with MIN_CONFIG with /home/test/config-default.
68 # MIN_CONFIG = /home/test/config-use-sometime
[all...]
/linux/rust/kernel/
H A Dbuild_assert.rs1 // SPDX-License-Identifier: GPL-2.0
3 //! Various assertions that happen during build-time.
5 //! There are three types of build-time assertions that you can use:
6 //! - [`static_assert!`]
7 //! - [`const_assert!`]
8 //! - [`build_asser
[all...]
/linux/Documentation/dev-tools/
H A Dpropeller.rst1 .. SPDX-License-Identifier: GPL-2.0
8 compiler. Propeller is a profile-guided optimization (PGO) method used
24 "build-afdo - train-afdo - build-propeller - trai
[all...]
/linux/tools/docs/
H A Dtest_doc_build.py2 # SPDX-License-Identifier: GPL-2.0
17 import time
47 (8, 2, 3) # Latest version - covers rolling distros
68 "sphinxcontrib-applehelp": "1.0.2",
69 "sphinxcontrib-devhelp": "1.0.2",
70 "sphinxcontrib-htmlhelp": "1.0.3",
71 "sphinxcontrib-jsmath": "1.0.1",
72 "sphinxcontrib-qthelp": "1.0.3",
73 "sphinxcontrib-serializinghtml": "1.1.4",
89 "sphinxcontrib-applehelp": "1.0.4",
[all …]
/linux/tools/testing/selftests/hid/tests/
H A Dbase.py2 # SPDX-License-Identifier: GPL-2.0
3 # -*- coding: utf-8 -*-
14 import time
172 # KernelModule("playstation", "hid-playstation")
175 # List of in kernel HID-BPF object files to load
177 # Any existing pre-loaded HID-BPF module will be removed
180 # 'HidBpf("xppen-ArtistPro16Gen2.bpf.o", True)'
238 sysfs_path = Path("/sys/module") / kernel_module.replace("-", "_")
240 ret = subprocess.run(["/usr/sbin/modprobe", kernel_module])
253 # this function will only work when run in the kernel tree
[all …]
/linux/tools/power/cpupower/bench/
H A DREADME-BENCH1 This is cpufreq-bench, a microbenchmark for the cpufreq framework.
7 - Identify worst case performance loss when doing dynamic frequency
9 - Identify average reaction time of a governor to CPU load changes
10 - (Stress) Testing whether a cpufreq low level driver or governor works
12 - Identify cpufreq related performance regressions between kernels
13 - Possibly Real time priority testing? -> what happens if there are
15 - ...
18 - Power saving related regressions (In fact as better the performance
21 - Real world (workloads)
27 cpufreq-bench helps to test the condition of a given cpufreq governor.
[all …]
/linux/tools/testing/selftests/kvm/x86/
H A Dsync_regs_test.c1 // SPDX-License-Identifier: GPL-2.0-only
48 TEST_ASSERT(left->reg == right->reg, \ in compare_regs()
51 left->reg, right->reg) in compare_regs()
92 struct kvm_run *run = (struct kvm_run *)arg; in race_events_inj_pen() local
93 struct kvm_vcpu_events *events = &run in race_events_inj_pen()
115 struct kvm_run *run = (struct kvm_run *)arg; race_events_exc() local
137 struct kvm_run *run = (struct kvm_run *)arg; race_sregs_cr4() local
161 struct kvm_run *run; race_sync_regs() local
210 struct kvm_run *run = vcpu->run; KVM_ONE_VCPU_TEST() local
231 struct kvm_run *run = vcpu->run; KVM_ONE_VCPU_TEST() local
252 struct kvm_run *run = vcpu->run; KVM_ONE_VCPU_TEST() local
275 struct kvm_run *run = vcpu->run; KVM_ONE_VCPU_TEST() local
313 struct kvm_run *run = vcpu->run; KVM_ONE_VCPU_TEST() local
330 struct kvm_run *run = vcpu->run; KVM_ONE_VCPU_TEST() local
361 struct kvm_run *run = vcpu->run; KVM_ONE_VCPU_TEST() local
[all...]
/linux/Documentation/driver-api/dmaengine/
H A Ddmatest.rst16 test multiple channels at the same time, and it can start multiple threads
21 capability of the following: DMA_MEMCPY (memory-to-memory), DMA_MEMSET
22 (const-to-memory or memory-to-memory, when emulated), DMA_XOR, DMA_PQ.
28 Part 1 - How to build the test module
33 Device Drivers -> DMA Engine support -> DMA Test client
38 Part 2 - When dmatest is built as a module
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
57 Example of multi-channel test usage (new in the 5.0 kernel)::
[all …]
/linux/drivers/ras/
H A DKconfig1 # SPDX-License-Identifier: GPL-2.0-only
8 and help them stay available for long periods of time without
12 produce correct outputs up to some given time. Reliability is
17 time, i.e. the amount of time a device is actually operating as the
18 percentage of total time it should be operating.
21 which a system can be repaired or maintained; if the time to repair
28 be functioning correctly. For example, a server may run forever and
46 Memory will be retired during boot time and run time depending on
47 platform-specific policies.
/linux/tools/power/pm-graph/config/
H A Dexample.cfg7 # and kprobes. It is run like this
9 # sudo ./sleepgraph.py -config config/example.cfg
14 # ---- General Options ----
25 # output folder for html, ftrace, and dmesg. Use {date} and {time} for current values
26 output-dir: suspend-{hostname}-{date}-{time}
45 # run sync before the test, minimizes sys_sync call time (default: false)
49 # Enable/disable runtime suspend for all devices, restore all after test (default: no-action)
53 # Switch the display on/off for the test using xset (default: no-action)
57 # Print the status of the test run in the given file (default: no-action)
64 # ---- Advanced Options ----
[all …]
/linux/Documentation/networking/
H A Dsnmp_counter.rst17 .. _RFC1213 ipInReceives: https://tools.ietf.org/html/rfc1213#page-26
30 .. _RFC1213 ipInDelivers: https://tools.ietf.org/html/rfc1213#page-28
41 .. _RFC1213 ipOutRequests: https://tools.ietf.org/html/rfc1213#page-28
60 .. _Explicit Congestion Notification: https://tools.ietf.org/html/rfc3168#page-6
73 .. _RFC1213 ipInHdrErrors: https://tools.ietf.org/html/rfc1213#page-27
81 .. _RFC1213 ipInAddrErrors: https://tools.ietf.org/html/rfc1213#page-27
98 .. _RFC1213 ipInUnknownProtos: https://tools.ietf.org/html/rfc1213#page-27
111 .. _RFC1213 ipInDiscards: https://tools.ietf.org/html/rfc1213#page-28
118 .. _RFC1213 ipOutDiscards: https://tools.ietf.org/html/rfc1213#page-28
125 .. _RFC1213 ipOutNoRoutes: https://tools.ietf.org/html/rfc1213#page-29
[all …]
/linux/Documentation/sound/designs/
H A Dseq-oss.rst15 What this does - it provides the emulation of the OSS sequencer, access
17 The most of applications using OSS can run if the appropriate ALSA
51 You can run two or more applications simultaneously (even for OSS
53 However, each MIDI device is exclusive - that is, if a MIDI device
57 * Real-time event processing:
59 The events can be processed in real time without using out of bound
60 ioctl. To switch to real-time mode, send ABSTIME 0 event. The followed
61 events will be processed in real-time without queued. To switch off the
62 real-time mode, send RELTIME 0 event.
67 ``/proc/asound/seq/oss`` at any time. In the later version,
[all …]

12345678910>>...41