Home
last modified time | relevance | path

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

12345678910>>...42

/linux-6.12.1/tools/perf/scripts/python/
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-6.12.1/Documentation/scheduler/
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 …]
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 …]
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 …]
Dsched-bwc.rst7 The SCHED_RT case is covered in Documentation/scheduler/sched-rt-group.rst
14 microseconds of CPU time. That quota is assigned to per-cpu run queues in
17 throttled. Throttled threads will not be able to run again until the next
22 is transferred to cpu-local "silos" on a demand basis. The amount transferred
26 -------------
27 This feature borrows time now against our future underrun, at the cost of
30 Traditional (UP-EDF) bandwidth control is something like:
36 we'd have to run more than a second of program time, and obviously miss
38 never time to catch up, unbounded fail.
52 everything is good. At the same time we have a p(5)p(5) = 0.25% chance
[all …]
/linux-6.12.1/include/uapi/linux/
Dum_timetravel.h1 /* SPDX-License-Identifier: BSD-3-Clause */
3 * Copyright (C) 2019 - 2023 Intel Corporation
10 * struct um_timetravel_msg - UM time travel message
14 * This is the message passed between the host (user-mode Linux instance)
19 * calendar, and then wait for its turn until it can run, etc. Note
30 * @seq: sequence number for the message - shall be reflected in
37 * @time: time in nanoseconds
39 __u64 time; member
46 * enum um_timetravel_shared_mem_fds - fds sent in ACK message for START message
63 * enum um_timetravel_start_ack - ack-time mask for start message
[all …]
/linux-6.12.1/tools/perf/tests/shell/
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-6.12.1/tools/testing/kunit/
Dkunit.py2 # SPDX-License-Identifier: GPL-2.0
15 import time
70 def get_kernel_root_path() -> str:
78 request: KunitConfigRequest) -> KunitResult:
81 config_start = time.time()
83 config_end = time.time()
85 return KunitResult(status, config_end - config_start)
88 request: KunitBuildRequest) -> KunitResult:
91 build_start = time.time()
95 build_end = time.time()
[all …]
/linux-6.12.1/Documentation/RCU/
Dtorture.rst1 .. SPDX-License-Identifier: GPL-2.0
13 be loaded to run a torture test. The test periodically outputs
19 Documentation/admin-guide/kernel-parameters.txt.
26 …rcu-torture:--- Start of test: nreaders=16 nfakewriters=4 stat_interval=30 verbose=0 test_no_idle_…
27 …rcu-torture: rtc: (null) ver: 155441 tfle: 0 rta: 155441 rtaf: 8884 rtf: 155440 rtmbe: 0…
28 rcu-torture: Reader Pipe: 727860534 34213 0 0 0 0 0 0 0 0 0
29 rcu-torture: Reader Batch: 727877838 17003 0 0 0 0 0 0 0 0 0
30 …rcu-torture: Free-Block Circulation: 155440 155440 155440 155440 155440 155440 155440 155440 1554…
31 …rcu-torture:--- End of test: SUCCESS: nreaders=16 nfakewriters=4 stat_interval=30 verbose=0 test_n…
37 be evident. ;-)
[all …]
/linux-6.12.1/drivers/powercap/
Didle_inject.c1 // SPDX-License-Identifier: GPL-2.0
8 * states for a specified fraction of time over a specified period.
13 * All of the kthreads used for idle injection are created at init time.
19 * The idle + run duration is specified via separate helpers and that allows
34 * It is up to the user of this framework to provide a lock for higher-level
51 * struct idle_inject_thread - task on/off switch structure
53 * @should_run: whether or not to run the task (for the smpboot kthread API)
61 * struct idle_inject_device - idle injection data
63 * @idle_duration_us: duration of CPU idle time to inject
64 * @run_duration_us: duration of CPU run time to allow
[all …]
/linux-6.12.1/tools/power/pm-graph/
Dsleepgraph.83 sleepgraph \- Suspend/Resume timing analysis
11 in optimizing their linux stack's suspend/resume time. Using a kernel
16 taking the most time in suspend/resume.
21 Generates output files in subdirectory: suspend-yymmdd-HHMMSS
27 \fB-h\fR
30 \fB-v\fR
33 \fB-verbose\fR
36 \fB-config \fIfile\fR
39 \fB-m \fImode\fR
42 \fB-o \fIname\fR
[all …]
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-6.12.1/arch/mips/kvm/
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-6.12.1/fs/btrfs/
DKconfig1 # SPDX-License-Identifier: GPL-2.0
24 Btrfs is a general purpose copy-on-write filesystem with extents,
52 bool "Btrfs will run sanity tests upon loading"
55 This will run some basic sanity tests on the free space cache
66 Enable run-time debugging support for the btrfs filesystem. This may
76 Enable run-time assertion checking. This will result in panics if
86 Enable run-time extent reference verification instrumentation. This
/linux-6.12.1/arch/s390/kvm/
Ddiag.c1 // SPDX-License-Identifier: GPL-2.0
14 #include <asm/virtio-ccw.h>
15 #include "kvm-s390.h"
17 #include "trace-s390.h"
25 start = vcpu->run->s.regs.gprs[(vcpu->arch.sie_block->ipa & 0xf0) >> 4]; in diag_release_pages()
26 end = vcpu->run->s.regs.gprs[vcpu->arch.sie_block->ipa & 0xf] + PAGE_SIZE; in diag_release_pages()
27 vcpu->stat.instruction_diagnose_10++; in diag_release_pages()
40 gmap_discard(vcpu->arch.gmap, start, end); in diag_release_pages()
48 gmap_discard(vcpu->arch.gmap, start, prefix); in diag_release_pages()
50 gmap_discard(vcpu->arch.gmap, 0, PAGE_SIZE); in diag_release_pages()
[all …]
/linux-6.12.1/tools/perf/Documentation/
Dperf-script.txt1 perf-script(1)
5 ----
6 perf-script - Read perf.data (created by perf record) and display trace output
9 --------
12 'perf script' [<options>] record <script> [<record-options>] <command>
13 'perf script' [<options>] report <script> [script-args]
14 'perf script' [<options>] <script> <required-script-args> [<record-options>] <command>
15 'perf script' [<options>] <top-script> [script-args]
18 -----------
26 You can also run a set of pre-canned scripts that aggregate and
[all …]
Dperf-sched.txt1 perf-sched(1)
5 ----
6 perf-sched - Tool to trace/measure scheduler properties (latencies)
9 --------
14 -----------
24 perf sched record -- sleep 1
27 …--------------------------------------------------------------------------------------------------…
29 …--------------------------------------------------------------------------------------------------…
32 …kworker/1:2-xfs:4649 | 0.012 ms | 1 | avg: 0.008 ms | max: 0.008 ms | max start: …
33 …kworker/3:1-xfs:388 | 0.011 ms | 1 | avg: 0.006 ms | max: 0.006 ms | max start: …
[all …]
/linux-6.12.1/tools/testing/selftests/kvm/
Ddirty_log_perf_test.c1 // SPDX-License-Identifier: GPL-2.0
13 #include <time.h>
31 * The test can still run even if hardware does not support GICv3, as it in arch_setup_vm()
55 /* How many host loops to run by default (one KVM_GET_DIRTY_LOG for each loop)*/
70 struct kvm_vcpu *vcpu = vcpu_args->vcpu; in vcpu_worker()
71 int vcpu_idx = vcpu_args->vcpu_idx; in vcpu_worker()
73 struct kvm_run *run; in vcpu_worker() local
80 run = vcpu->run; in vcpu_worker()
92 exit_reason_str(run->exit_reason)); in vcpu_worker()
100 pages_count += vcpu_args->pages; in vcpu_worker()
[all …]
/linux-6.12.1/tools/testing/memblock/
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 -v
45 For the full list of options from command line, see `./main --help`.
62 |-- asm ------------------,
[all …]
/linux-6.12.1/Documentation/admin-guide/
Dlockup-watchdogs.rst10 details), without giving other tasks a chance to run. The current
14 "softlockup_panic" (see "Documentation/admin-guide/kernel-parameters.rst" for
20 details), without letting other interrupts have a chance to run.
24 'hardlockup_panic', a compile time knob, "BOOTPARAM_HARDLOCKUP_PANIC",
26 (see "Documentation/admin-guide/kernel-parameters.rst" for details).
31 of time.
43 (compile-time initialized to 10 and configurable through sysctl of the
45 does not receive any hrtimer interrupt during that time the
51 timestamp every time it is scheduled. If that timestamp is not updated
64 event. The right value for a particular environment is a trade-off
[all …]
/linux-6.12.1/Documentation/power/
Druntime_pm.rst5 (C) 2009-2011 Rafael J. Wysocki <rjw@sisk.pl>, Novell Inc.
18 put their PM-related work items. It is strongly recommended that pm_wq be
20 them to be synchronized with system-wide power transitions (suspend to RAM,
53 The ->runtime_suspend(), ->runtime_resume() and ->runtime_idle() callbacks
57 1. PM domain of the device, if the device's PM domain object, dev->pm_domain,
60 2. Device type of the device, if both dev->type and dev->type->pm are present.
62 3. Device class of the device, if both dev->class and dev->class->pm are
65 4. Bus type of the device, if both dev->bus and dev->bus->pm are present.
69 dev->driver->pm directly (if present).
73 and bus type. Moreover, the high-priority one will always take precedence over
[all …]
/linux-6.12.1/Documentation/leds/
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-6.12.1/tools/testing/ktest/
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-sometimes
71 # MIN_CONFIG = /home/test/config-most-times
78 # ktest will fail to execute, and no tests will run.
[all …]
/linux-6.12.1/Documentation/admin-guide/pm/
Dcpuidle.rst1 .. SPDX-License-Identifier: GPL-2.0
8 CPU Idle Time Management
27 CPU idle time management is an energy-efficiency feature concerned about using
31 ------------
33 CPU idle time management operates on CPUs as seen by the *CPU scheduler* (that
37 software as individual single-core processors. In other words, a CPU is an
43 program) at a time, it is a CPU. In that case, if the hardware is asked to
46 Second, if the processor is multi-core, each core in it is able to follow at
47 least one program at a time. The cores need not be entirely independent of each
48 other (for example, they may share caches), but still most of the time they
[all …]
/linux-6.12.1/rust/kernel/
Dbuild_assert.rs1 // SPDX-License-Identifier: GPL-2.0
3 //! Build-time assert.
16 /// fn foo(a: usize) -> usize {
20 /// assert_eq!(foo(usize::MAX - 1), usize::MAX); // OK.
33 /// Asserts that a boolean expression is `true` at compile time.
48 /// static_assert!(1 > 1); // Compile-time error
49 /// build_assert!(1 > 1); // Build-time error
50 /// assert!(1 > 1); // Run-time error
59 /// build_assert!(N > 1); // Build-time check
60 /// assert!(N > 1); // Run-time check
[all …]

12345678910>>...42