Home
last modified time | relevance | path

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

12345678910>>...43

/kernel/linux/linux-4.19/tools/perf/scripts/python/
Dstat-cpi.py2 # SPDX-License-Identifier: GPL-2.0
9 def get_key(time, event, cpu, thread): argument
10 return "%d-%s-%d-%d" % (time, event, cpu, thread)
12 def store_key(time, cpu, thread): argument
13 if (time not in times):
14 times.append(time)
22 def store(time, event, cpu, thread, val, ena, run): argument
23 #print "event %s cpu %d, thread %d, time %d, val %d, ena %d, run %d" % \
24 # (event, cpu, thread, time, val, ena, run)
26 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-4.19/Documentation/scheduler/
Dsched-rt-group.txt1 Real-Time group scheduling
2 --------------------------
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
[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-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-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-4.19/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
50 * struct idle_inject_thread - task on/off switch structure
52 * @should_run: whether or not to run the task (for the smpboot kthread API)
60 * struct idle_inject_device - idle injection data
62 * @idle_duration_ms: duration of CPU idle time to inject
63 * @run_duration_ms: duration of CPU run time to allow
[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-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 …]
DREADME8 pm-graph: suspend/resume/boot timing analysis tools
11 Home Page: https://01.org/pm-graph
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:
18 https://01.org/pm-graph/documentation/getting-started
20 - Config File Format:
21 https://01.org/pm-graph/documentation/3-config-file-format
23 - upstream version in git:
24 https://github.com/intel/pm-graph/
[all …]
/kernel/linux/linux-4.19/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-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-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-4.19/fs/btrfs/
DKconfig1 # SPDX-License-Identifier: GPL-2.0
17 Btrfs is a general purpose copy-on-write filesystem with extents,
51 after a power-loss or kernel panic event the filesystem is
60 to verify the integrity of (super)-block write requests
61 during the run of a regression test, say N
64 bool "Btrfs will run sanity tests upon loading"
67 This will run some basic sanity tests on the free space cache
78 Enable run-time debugging support for the btrfs filesystem. This may
88 Enable run-time assertion checking. This will result in panics if
98 Enable run-time extent reference verification instrumentation. This
/kernel/linux/linux-4.19/Documentation/leds/
Dledtrig-transient.txt7 to be off. The delay_on value specifies the time period an LED should stay
10 gets deactivated. There is no provision for one time activation to implement
19 As a specific example of this use-case, let's look at vibrate feature on
41 that are active at the time driver gets suspended, continue to run, without
61 non-transient state. When driver gets suspended, irrespective of the transient
75 - duration allows setting timer value in msecs. The initial value is 0.
76 - activate allows activating and deactivating the timer specified by
79 - state allows user to specify a transient state to be held for the specified
82 activate - one shot timer activate mechanism.
92 duration - one shot timer value. When activate is set, duration value
[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 …]
/kernel/linux/linux-4.19/Documentation/power/
Druntime_pm.txt3 (C) 2009-2011 Rafael J. Wysocki <rjw@sisk.pl>, Novell Inc.
13 put their PM-related work items. It is strongly recommended that pm_wq be
15 them to be synchronized with system-wide power transitions (suspend to RAM,
47 The ->runtime_suspend(), ->runtime_resume() and ->runtime_idle() callbacks
51 1. PM domain of the device, if the device's PM domain object, dev->pm_domain,
54 2. Device type of the device, if both dev->type and dev->type->pm are present.
56 3. Device class of the device, if both dev->class and dev->class->pm are
59 4. Bus type of the device, if both dev->bus and dev->bus->pm are present.
63 dev->driver->pm directly (if present).
67 and bus type. Moreover, the high-priority one will always take precedence over
[all …]
/kernel/linux/linux-5.10/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 …]
/kernel/linux/linux-4.19/Documentation/
Dlockup-watchdogs.txt10 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 …]
/kernel/linux/linux-5.10/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 …]
/kernel/linux/linux-4.19/tools/power/pm-graph/config/
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 …]
/kernel/linux/linux-5.10/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 …]

12345678910>>...43