| /linux/Documentation/scheduler/ |
| H A D | sched-stats.rst | 24 12 which was in the kernel from 2.6.13-2.6.19 (version 13 never saw a kernel
63 1) # of times sched_yield() was called
69 3) # of times schedule() was called
74 5) # of times try_to_wake_up() was called
75 6) # of times try_to_wake_up() was called to wake up the local cpu
103 1) # of times in this domain sched_balance_rq() was called when the
104 cpu was busy
108 more tasks and failed, when the cpu was busy
109 4) Total imbalance in load in this domain when the cpu was busy
110 5) Total imbalance in utilization in this domain when the cpu was busy
[all …]
|
| H A D | sched-nice-design.rst | 11 Unfortunately that was not that easy to implement under the old
13 support was historically coupled to timeslice length, and timeslice
14 units were driven by the HZ tick, so the smallest timeslice was 1/HZ.
41 changing the ABI to extend priorities was discarded early on.)
48 this was long ago when hardware was weaker and caches were smaller, and
60 coupling to timeslices and granularity it was not really viable.
63 about Linux's nice level support was its asymmetry around the origin
79 depend on the nice level of the parent shell - if it was at nice -10 the
80 CPU split was different than if it was at +5 or +10.
82 A third complaint against Linux's nice level support was that negative
[all …]
|
| /linux/tools/perf/arch/arm64/entry/syscalls/ |
| H A D | syscall_32.tbl | 21 # 7 was sys_waitpid
27 # 13 was sys_time
31 # 17 was sys_break
32 # 18 was sys_stat
36 # 22 was sys_umount
39 # 25 was sys_stime
41 # 27 was sys_alarm
42 # 28 was sys_fstat
44 # 30 was sys_utime
45 # 31 was sys_stty
[all …]
|
| /linux/Documentation/userspace-api/media/v4l/ |
| H A D | hist-v4l2.rst | 10 Soon after the V4L API was added to the kernel it was criticised as too
15 another four years and two stable kernel releases until the new API was
23 1998-08-27: The :c:func:`select()` function was introduced.
27 1998-09-18: The ``VIDIOC_NONCAP`` ioctl was replaced by the otherwise
39 1998-10-02: The ``id`` field was removed from
41 renamed. The :ref:`VIDIOC_QUERYSTD` ioctl was
45 Codec API was released.
50 1998-11-12: The read/write direction of some ioctls was misdefined.
57 with ``V4L2_CID_AUDIO``. The ``V4L2_MAJOR`` define was removed from
58 ``videodev.h`` since it was only used once in the ``videodev`` kernel
[all …]
|
| H A D | vidioc-qbuf.rst | 43 :c:type:`v4l2_buffer` to the same buffer type as was
113 ``EBUSY`` will be returned if the first buffer was queued directly and
138 when the buffer was enqueued. No new file descriptor is created at dequeue time
144 queue. When the ``O_NONBLOCK`` flag was given to the
160 buffer was in the outgoing queue.
165 ``length`` are invalid, or the ``V4L2_BUF_FLAG_REQUEST_FD`` flag was
166 set but the given ``request_fd`` was invalid, or ``m.fd`` was
185 codecs if a buffer with the ``V4L2_BUF_FLAG_LAST`` was already
189 The ``V4L2_BUF_FLAG_REQUEST_FD`` flag was set but the device does not
191 the ``V4L2_BUF_FLAG_REQUEST_FD`` flag was not set but the device requires
[all …]
|
| H A D | vidioc-query-dv-timings.rst | 57 If the timings could not be detected because there was no signal, then
58 ENOLINK is returned. If a signal was detected, but it was unstable and
79 No timings could be detected because no signal was found.
82 The signal was unstable and the hardware could not lock on to it.
|
| /linux/tools/perf/arch/arm/entry/syscalls/ |
| H A D | syscall.tbl | 22 # 7 was sys_waitpid
32 # 17 was sys_break
33 # 18 was sys_stat
43 # 28 was sys_fstat
46 # 31 was sys_stty
47 # 32 was sys_gtty
50 # 35 was sys_ftime
59 # 44 was sys_prof
63 # 48 was sys_signal
68 # 53 was sys_lock
[all …]
|
| /linux/Documentation/ABI/obsolete/ |
| H A D | automount-tracefs-debugfs | 7 The ftrace was first added to the kernel, its interface was placed
11 new interface was created called "tracefs". This was a stand alone
12 file system and was usually mounted in /sys/kernel/tracing.
16 the "tracing" directory of debugfs. The tracefs interface was added
|
| /linux/Documentation/filesystems/ |
| H A D | locks.rst | 18 The old flock(2) emulation in the kernel was swapped for proper BSD
33 Because sendmail was unable to use the old flock() emulation, many sendmail
35 for example. This gave rise to some other subtle problems if sendmail was
50 race and deadlock conditions that the current solution was the only
60 Mandatory locking was prior to this release a general configuration option
61 that was valid for all mounted filesystems. This had a number of inherent
62 dangers, not the least of which was the ability to freeze an NFS server by
65 Such option was dropped in Kernel v5.14.
|
| /linux/Documentation/admin-guide/ |
| H A D | tainted-kernels.rst | 25 why the kernel was tainted is shown after the Process ID ('PID:') and a shortened
35 You'll find a 'Not tainted: ' there if the kernel was not tainted at the
36 time of the event; if it was, then it will print 'Tainted: ' and characters
42 the kernel got tainted earlier because a proprietary Module (``P``) was loaded,
43 a warning occurred (``W``), and an externally-built module was loaded (``O``).
61 * Proprietary module was loaded (#0)
63 * Externally-built ('out-of-tree') module was loaded (#12)
69 You can try to decode the number yourself. That's easy if there was only one
85 0 G/P 1 proprietary module was loaded
86 1 _/F 2 module was force loaded
[all …]
|
| /linux/tools/perf/arch/sh/entry/syscalls/ |
| H A D | syscall.tbl | 27 # 17 was break
41 # 31 was stty
42 # 32 was gtty
45 # 35 was ftime
54 # 44 was prof
63 # 53 was lock
66 # 56 was mpx
68 # 58 was ulimit
69 # 59 was olduname
92 # 82 was select
[all …]
|
| /linux/Documentation/userspace-api/media/cec/ |
| H A D | cec-ioc-receive.rst | 102 - Timestamp in ns of when the last byte of the message was transmitted.
107 - Timestamp in ns of when the last byte of the message was received.
115 filled in by the driver with the length of the reply message if ``reply`` was set.
132 was not 0), then the ``sequence`` field of the reply will be set to the sequence
143 the payload of the reply message if ``timeout`` was set.
263 - The message was transmitted successfully. This is mutually
266 the transmit was eventually successful.
271 - CEC line arbitration was lost, i.e. another transmit started at the
278 - Message was not acknowledged. Note that some hardware cannot tell apart
286 - Low drive was detected on the CEC bus. This indicates that a
[all …]
|
| /linux/Documentation/ABI/removed/ |
| H A D | sysfs-class-rfkill | 9 Description: This file was deprecated because there no longer was a way to
11 This file was scheduled to be removed in 2012, and was removed
|
| /linux/tools/perf/arch/parisc/entry/syscalls/ |
| H A D | syscall.tbl | 115 # 102 was socketcall
143 # 127 was create_module
146 # 130 was get_kernel_syms
154 # 137 was afs_syscall
186 # 167 was query_module
188 # 169 was nfsservctl
216 # 196 was getpmsg
217 # 197 was putpmsg
225 # 203 was attrctl
226 # 204 was acl_get
[all …]
|
| /linux/Documentation/arch/powerpc/ |
| H A D | vcpudispatch_stats.rst | 31 2. number of times this vcpu was dispatched on the same processor as last
33 3. number of times this vcpu was dispatched on a different processor core
35 4. number of times this vcpu was dispatched on a different chip
36 5. number of times this vcpu was dispatches on a different socket/drawer
42 6. number of times this vcpu was dispatched in its home node (chip)
43 7. number of times this vcpu was dispatched in a different node
44 8. number of times this vcpu was dispatched in a node further away (numa
|
| /linux/Documentation/arch/arm/nwfpe/ |
| H A D | nwfpe.rst | 7 The majority of the code was written by me, Scott Bambrough It is
9 where required. It was written quickly, with a goal of implementing a
20 Another choice I made was in the file structure. I have attempted to
33 SoftFloat to the ARM was done by Phil Blundell, based on an earlier
61 SoftFloat was written by John R. Hauser. This work was made possible in
63 1947 Center Street, Berkeley, California 94704. Funding was partially
65 original version of this code was written as part of a project to build
|
| /linux/Documentation/arch/x86/ |
| H A D | amd-debugging.rst | 29 After a suspend cycle you can tell how much time was spent in a hardware sleep
132 So there you have it: the PCI device associated with this GPIO wakeup was ``0000:c2:00.4``.
172 from properly entering s0i3. This was debugged using internal AMD tools
174 when a core was offlined. It was determined that the hardware didn't get
176 CPU from going into the deepest state. The issue was debugged to a missing
183 A big problem that occurred with Rembrandt was that there was graphical
187 This actually was a misalignment for earlier silicon as well, but was not
202 The HPET was being used to program the wakeup source for the system, however
203 this was causing a spurious wakeup after 5 minutes. The correct alarm to use
204 was the ACPI alarm.
[all …]
|
| /linux/Documentation/process/ |
| H A D | generated-content.rst | 41 contribution was not written by a person in the Signed-off-by chain,
42 but was instead created by a tool.
45 development process; if a tool was used to find a problem addressed by
54 - A .c file in the patch was originally generated by a coding
56 - The changelog was generated by handing the patch to a generative AI
58 - The changelog was translated from another language.
78 - If code was largely generated from a single or short set of
94 elaborate on how the tool or model was trained.
101 additional scrutiny in proportion to how much of it was generated.
|
| /linux/Documentation/userspace-api/media/dvb/ |
| H A D | frontend-stat-properties.rst | 39 frontend, but it was not possible to collect it (could be a
64 measurement was not complete yet.
83 measurement was not complete yet.
114 measurement was not complete yet.
128 measurement was taken.
142 measurement was not complete yet.
171 measurement was not complete yet.
185 measurement was taken.
199 measurement was not complete yet.
220 measurement was not complete yet.
[all …]
|
| /linux/Documentation/userspace-api/gpio/ |
| H A D | error-codes.rst | 20 - The device was opened in non-blocking mode and a read can't
31 usage of a resource that was already allocated. The ioctl must not
37 - There was a failure while copying data from/to userspace, probably
47 - Device not found or was removed.
68 - Typically returned when a feature requiring interrupt support was
|
| /linux/Documentation/scsi/ |
| H A D | sym53c500_cs.rst | 8 package, and was written by Tom Corner (tcorner@via.at). A rewrite was
14 All the USE_BIOS code has been ripped out. It was never used, and could
20 The Symbios Logic 53c500 chip was used in the "newer" (circa 1997) version
|
| /linux/tools/testing/selftests/ftrace/ |
| H A D | README | 55 * FAIL: The test failed, but was expected to succeed. The test which exits
59 for example, the test was interrupted
61 or the test was set up incorrectly
64 * UNTESTED: The test was not run, currently just a placeholder.
70 * XFAIL: The test failed, and was expected to fail.
|
| /linux/Documentation/sound/codecs/ |
| H A D | cs35l56.rst | 131 filename qualifier. Support for the l?u? qualifier was added in kernel 6.16.
167 [ 7.947844] cs35l56 sdw:0:0:01fa:3556:01:0: Slave 4 state check1: UNATTACHED, status was 1
174 [10.879235] cs35l56 sdw:0:0:01fa:3556:01:0: Slave 4 state check1: UNATTACHED, status was 1
212 Shows that a .wmfw firmware file was found and downloaded.
215 Shows that a .bin firmware file was found and downloaded.
218 Factory calibration data in EFI was written to the amplifier.
226 Caused by mismatched .wmfw and .bin file, or .bin file was found but
227 .wmfw was not.
231 Caused by mismatched .wmfw and .bin file, or .bin file was found but
232 .wmfw was not.
[all …]
|
| /linux/Documentation/watchdog/ |
| H A D | watchdog-api.rst | 104 printf("The timeout was set to %d seconds\n", timeout);
106 This example might actually print "The timeout was set to 60 seconds"
113 printf("The timeout was is %d seconds\n", timeout);
136 printf("The pretimeout was is %d seconds\n", timeout);
148 printf("The timeout was is %d seconds\n", timeleft);
177 The machine was last rebooted by the watchdog because the thermal limit was
190 External monitoring relay/source 1 was triggered. Controllers intended for
198 External monitoring relay/source 2 was triggered
210 The last reboot was caused by the watchdog card
224 The watchdog saw a keepalive ping since it was last queried.
|
| /linux/Documentation/driver-api/usb/ |
| H A D | error-codes.rst | 73 ``-EPERM`` Submission failed because ``urb->reject`` was set.
75 ``-EHOSTUNREACH`` URB was rejected because the device is suspended.
103 ``-ENOENT`` URB was synchronously unlinked by
121 a driver cannot tell whether there was a
133 completed, and no other error was reported
148 ``-EOVERFLOW`` [#f1]_ The amount of data returned by the endpoint was
155 was set in ``urb->transfer_flags``.
157 ``-ENODEV`` Device was removed. Often preceded by a burst
168 ``-ECONNRESET`` URB was asynchronously unlinked by
|