Searched full:was (Results 1 – 25 of 1086) sorted by relevance
12345678910>>...44
| /Documentation/scheduler/ |
| D | sched-stats.rst | 16 12 which was in the kernel from 2.6.13-2.6.19 (version 13 never saw a kernel
48 1) # of times sched_yield() was called
54 3) # of times schedule() was called
59 5) # of times try_to_wake_up() was called
60 6) # of times try_to_wake_up() was called to wake up the local cpu
83 1) # of times in this domain sched_balance_rq() was called when the
84 cpu was idle
86 the load did not require balancing when the cpu was idle
88 more tasks and failed, when the cpu was idle
90 sched_balance_rq() in this domain when the cpu was idle
[all …]
|
| 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 …]
|
| /Documentation/userspace-api/media/v4l/ |
| 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 …]
|
| 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 …]
|
| 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.
|
| /Documentation/ABI/removed/ |
| 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
|
| D | sysfs-selinux-checkreqprot | 7 REMOVAL UPDATE: The SELinux checkreqprot functionality was removed in
13 This was a compatibility mechanism for legacy userspace and
17 at boot was changed starting in Linux v4.4 to 0 (i.e. check the
|
| /Documentation/admin-guide/ |
| 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 …]
|
| /Documentation/filesystems/ |
| 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.
|
| /Documentation/arch/powerpc/ |
| 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
|
| /Documentation/userspace-api/media/cec/ |
| 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 …]
|
| /Documentation/arch/arm/nwfpe/ |
| 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
|
| /Documentation/devicetree/bindings/serial/ |
| D | xlnx,opb-uartlite.yaml | 38 The fixed baud rate that the device was configured for.
43 The fixed number of data bits that the device was configured for.
49 Whether parity checking was enabled when the device was configured.
55 Whether odd parity was configured.
|
| /Documentation/scsi/ |
| 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
|
| /Documentation/userspace-api/gpio/ |
| 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
|
| /Documentation/devicetree/bindings/gnss/ |
| D | sirfstar.yaml | 14 chips, starting from the SiRFstarIII which was a chip that was introduced in
15 2004 and used in a lot of dedicated GPS devices. In 2009 SiRF was acquired
16 by CSR (Cambridge Silicon Radio) and in 2012 the CSR GPS business was
18 was acquired by Qualcomm who still sell some of the SiRF products.
|
| /Documentation/gpu/amdgpu/ |
| D | debugging.rst | 40 Next you have the vmid and pasid. If the vmid is 0, this fault was likely
62 - bit 0: the PTE was not valid
63 - bit 1: the PTE read bit was not set
64 - bit 2: the PTE write bit was not set
65 - bit 3: the PTE execute bit was not set
67 Finally, RW, indicates whether the access was a read (0) or a write (1).
|
| /Documentation/userspace-api/media/dvb/ |
| 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 …]
|
| /Documentation/devicetree/bindings/arm/ |
| D | gemini.yaml | 11 produced by Storlink Semiconductor around 2005. The company was renamed
13 It was derived from earlier products from Storm named SL3316 (Centroid) and
16 Storm Semiconductor was acquired by Cortina Systems in 2008 and the SoC was
17 produced and used for NAS and similar usecases. In 2014 Cortina Systems was
|
| D | arm,realview.yaml | 22 - description: ARM RealView Emulation Baseboard (HBI-0140) was created
28 (HBI-0147) was created as a development board to test ARM TrustZone,
33 (HBI-0159, HBI-0175 and HBI-0176) was created to showcase
39 HBI-0176 and HBI-0175) was the first reference platform for the
44 (HBI-0182 and HBI-0183) was the reference platform for the Cortex-A9
|
| /Documentation/rust/ |
| D | index.rst | 13 The Rust support was merged in v6.1 into mainline in order to help in
14 determining whether Rust as a language was suitable for the kernel, i.e. worth
36 This kernel documentation was built with `Rust code documentation
41 This kernel documentation was not built with Rust code documentation.
|
| /Documentation/i2c/ |
| D | fault-codes.rst | 48 transmit mode: some other master was transmitting different
65 Returned by SMBus adapters when the bus was busy for longer
68 or that the reset was attempted but failed.
72 detected before any I/O operation was started. Use a more
95 an I2C device was temporarily not responding, usually it
108 have verified that functionality was supported before it
124 Returned when a transfer was requested using an adapter
129 time, and was aborted before it completed.
|
| /Documentation/devicetree/bindings/gpu/host1x/ |
| D | nvidia,tegra234-nvdec.yaml | 73 Offset to bootloader manifest from beginning of firmware that was configured by
79 Offset to bootloader code section from beginning of firmware that was configured by
85 Offset to bootloader data section from beginning of firmware that was configured by
91 Offset to operating system manifest from beginning of firmware that was configured by
97 Offset to operating system code section from beginning of firmware that was configured by
103 Offset to operating system data section from beginning of firmware that was configured
|
| /Documentation/firmware-guide/acpi/ |
| D | osi.rst | 24 but where Linux was installed to replace the original OS (Windows or OSX).
56 However this was discovered to be abused by other BIOS vendors to change
62 That was easy. Read on, to find out how to do it wrong.
64 Before _OSI, there was _OS
77 The idea was on a platform tasked with running multiple OS's,
87 _OSI was born to replace _OS.
89 _OS was abandoned, though even today, many BIOS look for
118 This misuse was adopted and continues today.
152 _REV was defined in ACPI 1.0 to return the version of ACPI
158 Unfortunately, _REV was also misused. eg. some BIOS would check
|
| /Documentation/driver-api/usb/ |
| D | persist.rst | 23 device is still attached or perhaps it was removed and a different
33 If the kernel wants to believe that your USB keyboard was unplugged
34 while the system was asleep and a new keyboard was plugged in when the
40 been unplugged while the system was suspended. If you had a mounted
43 root filesystem was located on the device, since your system will
49 was asleep, on many systems during the initial stages of wakeup the
60 has happened; look for lines saying "root hub lost power or was reset".
77 not in the expected state during resume (i.e., if the controller was
91 but a USB device was unplugged and then replugged, or if a USB device
|
12345678910>>...44