Home
last modified time | relevance | path

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

12345678910>>...50

/kernel/linux/linux-6.6/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 …]
/kernel/linux/linux-5.10/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 …]
/kernel/linux/linux-5.10/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 ---------------
43 the amount of bandwidth (eg. CPU time) being constant. In order to schedule
45 of the CPU time available. Without a minimum guarantee a realtime group can
50 ----------------
52 CPU time is divided by means of specifying how much time can be spent running
53 in a given period. We allocate this "run time" for each realtime group which
[all …]
/kernel/linux/linux-6.6/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 ---------------
43 the amount of bandwidth (eg. CPU time) being constant. In order to schedule
45 of the CPU time available. Without a minimum guarantee a realtime group can
50 ----------------
52 CPU time is divided by means of specifying how much time can be spent running
53 in a given period. We allocate this "run time" for each realtime group which
[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 …]
/kernel/linux/linux-6.6/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 …]
/kernel/linux/linux-5.10/Documentation/dev-tools/kunit/
Dindex.rst1 .. SPDX-License-Identifier: GPL-2.0
4 KUnit - Unit Testing for the Linux Kernel
12 kunit-tool
28 writing unit tests. Tests written against KUnit will run on kernel boot if
29 built-in, or when loaded if built as a module. These tests write out results to
33 :doc:`kunit_tool <kunit-tool>`, which builds a `User Mode Linux
34 <http://user-mode-linux.sourceforge.net>`_ kernel, runs it, and parses the test
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
[all …]
/kernel/linux/linux-6.6/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 …]
/kernel/linux/linux-5.10/tools/testing/kunit/
Dkunit.py2 # SPDX-License-Identifier: GPL-2.0
13 import time
54 request: KunitConfigRequest) -> KunitResult:
57 config_start = time.time()
59 config_end = time.time()
63 config_end - config_start)
66 config_end - config_start)
69 request: KunitBuildRequest) -> KunitResult:
72 build_start = time.time()
77 build_end = time.time()
[all …]
/kernel/linux/linux-5.10/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 …]
/kernel/linux/linux-6.6/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 …]
/kernel/linux/linux-6.6/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 …]
/kernel/linux/linux-6.6/include/uapi/linux/
Dum_timetravel.h21 * struct um_timetravel_msg - UM time travel message
25 * This is the message passed between the host (user-mode Linux instance)
30 * calendar, and then wait for its turn until it can run, etc. Note
41 * @seq: sequence number for the message - shall be reflected in
48 * @time: time in nanoseconds
50 __u64 time; member
54 * enum um_timetravel_ops - Operation codes
59 * this usually doesn't carry any data in the 'time' field
65 * @UM_TIMETRAVEL_START: initialize the connection, the time
72 * @UM_TIMETRAVEL_REQUEST: request to run at the given time
[all …]
/kernel/linux/linux-5.10/include/uapi/linux/
Dum_timetravel.h21 * struct um_timetravel_msg - UM time travel message
25 * This is the message passed between the host (user-mode Linux instance)
30 * calendar, and then wait for its turn until it can run, etc. Note
41 * @seq: sequence number for the message - shall be reflected in
48 * @time: time in nanoseconds
50 __u64 time; member
54 * enum um_timetravel_ops - Operation codes
59 * this usually doesn't carry any data in the 'time' field
65 * @UM_TIMETRAVEL_START: initialize the connection, the time
72 * @UM_TIMETRAVEL_REQUEST: request to run at the given time
[all …]
/kernel/linux/linux-6.6/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 …]
/kernel/linux/linux-5.10/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 …]
/kernel/linux/linux-6.6/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 …]
/kernel/linux/linux-5.10/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 -----------
30 of the workload as it occurred when it was recorded - and can repeat
33 'perf sched map' to print a textual context-switching outline of
35 individual CPUs, and the two-letter shortcuts stand for tasks that
42 perf sched record -- sleep 1
46 time (time between sched-out and next sched-in events for the task), the
[all …]
/kernel/linux/linux-6.6/fs/btrfs/
DKconfig1 # SPDX-License-Identifier: GPL-2.0
24 Btrfs is a general purpose copy-on-write filesystem with extents,
60 after a power-loss or kernel panic event the filesystem is
69 to verify the integrity of (super)-block write requests
70 during the run of a regression test, say N
73 bool "Btrfs will run sanity tests upon loading"
76 This will run some basic sanity tests on the free space cache
87 Enable run-time debugging support for the btrfs filesystem. This may
97 Enable run-time assertion checking. This will result in panics if
107 Enable run-time extent reference verification instrumentation. This
/kernel/linux/linux-5.10/fs/btrfs/
DKconfig1 # SPDX-License-Identifier: GPL-2.0
25 Btrfs is a general purpose copy-on-write filesystem with extents,
59 after a power-loss or kernel panic event the filesystem is
68 to verify the integrity of (super)-block write requests
69 during the run of a regression test, say N
72 bool "Btrfs will run sanity tests upon loading"
75 This will run some basic sanity tests on the free space cache
86 Enable run-time debugging support for the btrfs filesystem. This may
96 Enable run-time assertion checking. This will result in panics if
106 Enable run-time extent reference verification instrumentation. This
/kernel/linux/linux-6.6/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 …]
/kernel/linux/linux-6.6/tools/perf/Documentation/
Dperf-sched.txt1 perf-sched(1)
5 ----
6 perf-sched - Tool to trace/measure scheduler properties (latencies)
9 --------
14 -----------
30 of the workload as it occurred when it was recorded - and can repeat
33 'perf sched map' to print a textual context-switching outline of
35 individual CPUs, and the two-letter shortcuts stand for tasks that
42 perf sched record -- sleep 1
46 time (time between sched-out and next sched-in events for the task), the
[all …]
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 …]
/kernel/linux/linux-5.10/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 …]

12345678910>>...50