Searched full:because (Results 1 – 25 of 875) sorted by relevance
12345678910>>...35
| /Documentation/ABI/testing/ |
| D | sysfs-bus-event_source-devices-hv_gpci | 110 * "-EIO" : Can't retrieve system information because of invalid buffer length/invalid address
111 or because of some hardware error. Refer to getPerfCountInfo documentation for
142 * "-EIO" : Can't retrieve system information because of invalid buffer length/invalid address
143 or because of some hardware error. Refer to getPerfCountInfo documentation for
174 * "-EIO" : Can't retrieve system information because of invalid buffer length/invalid address
175 or because of some hardware error. Refer to getPerfCountInfo documentation for
206 * "-EIO" : Can't retrieve system information because of invalid buffer length/invalid address
207 or because of some hardware error. Refer to getPerfCountInfo documentation for
238 * "-EIO" : Can't retrieve system information because of invalid buffer length/invalid address
239 or because of some hardware error. Refer to getPerfCountInfo documentation for
|
| /Documentation/networking/devlink/ |
| D | devlink-trap.rst | 100 * ``control``: Trapped packets were trapped by the device because these are
136 - Traps incoming packets that the device decided to drop because of a
171 - Traps packets that the device decided to drop because they could not be
175 - Traps packets that the device decided to drop because they need to
179 - Traps packets that the device decided to drop because they need to be
184 - Traps packets that the device decided to drop because they need to be
189 - Traps packets that the device decided to drop because they need to be
193 - Traps packets that the device decided to drop because they need to be
197 - Traps packets that the device decided to drop because they need to be
202 - Traps packets that the device decided to drop because they need to be
[all …]
|
| /Documentation/devicetree/bindings/powerpc/fsl/ |
| D | msi-pic.txt | 17 region must be added because different MSI group has different MSIIR1 offset.
30 MPIC v4.3 does not support this property because the 32 interrupts of an
89 because of hardware limitations of the Peripheral Access Management Unit
96 Because PCI devices must be able to DMA to memory, the primary window must
102 means they cannot be located at just any address. Because of these
|
| /Documentation/locking/ |
| D | spinlocks.rst | 40 before, because you have to make sure the spinlocks correctly protect the
102 but partly **because** they are safe they are also fairly slow. They are slower
103 than they'd need to be, because they do have to disable interrupts
131 interrupt happens on the same CPU that already holds the lock, because the
132 lock will obviously never be released (because the interrupt is waiting
138 on other CPU's, because an interrupt on another CPU doesn't interrupt the
|
| D | locktypes.rst | 125 PREEMPT_RT does not change the semaphore implementation because counting
150 Because an rw_semaphore writer cannot grant its priority to multiple
152 thus starving even high-priority writers. In contrast, because readers
274 to RUNNING, but that does not work here because the task must remain
313 - Because an rwlock_t writer cannot grant its priority to multiple
315 thus starving even high-priority writers. In contrast, because readers
338 On a PREEMPT_RT kernel this code sequence breaks because local_lock_irq()
372 because local_lock_irqsave() does not disable interrupts due to the
412 On PREEMPT_RT kernel this code sequence breaks because RT-mutex requires a
429 not allow to acquire p->lock because get_cpu_ptr() implicitly disables
[all …]
|
| /Documentation/admin-guide/ |
| D | edid.rst | 11 either correctly working because all components follow the standards -
12 or the computer is unusable, because the screen remains dark after
|
| D | serial-console.rst | 58 for other reasons. For example, because of a typo or because
68 ``/dev/console`` gets associated with ``tty0``. It is because kernel
70 because of the default behavior when no console device is specified,
121 console for the first time, because otherwise init will probably
|
| /Documentation/kbuild/ |
| D | Kconfig.select-break | 12 # symbols. Because of this use of select should be used with caution. An
16 # However, when A is set, C can be set as well because Kconfig does not
|
| /Documentation/driver-api/md/ |
| D | raid5-ppl.rst | 8 in degraded state, there is no way to recalculate parity, because one of the
12 be incorrect. Such condition is known as the RAID5 Write Hole. Because of
23 the array. Because of this, using write-intent bitmap and PPL together is not
|
| /Documentation/mm/ |
| D | active_mm.rst | 18 Cc'd to linux-kernel, because I don't write explanations all that often,
69 lazy users. That is often a short-lived state, because once that thread
71 released because "mm_count" becomes zero.
89 because it slightly changes the interfaces to accommodate the alpha (who
|
| D | page_tables.rst | 50 would be very sparse, because large portions of the virtual memory usually
52 address space does not waste valuable page table memory, because it will suffice
96 The **entry** part of the name is a bit confusing because while in Linux 1.0
178 happen because the CPU is trying to access memory that the current task is not
179 permitted to, or because the data is not present into physical memory.
193 and "Copy-on-Write" because these subjects are out of scope as they belong to
196 Swapping differentiates itself from the other mentioned techniques because it's
204 because they avoid the need for complex page table lookups at the expenses of
280 Several code path make use of the latter two functions because they need to
|
| /Documentation/userspace-api/media/v4l/ |
| D | vidioc-query-dv-timings.rst | 57 If the timings could not be detected because there was no signal, then
61 (e.g. because the pixelclock is out of range of the hardware
79 No timings could be detected because no signal was found.
|
| D | selection-api-vs-crop-api.rst | 14 because the described operation is actually the composing. The
26 because they are not portable (endianness), and do not work for
|
| /Documentation/networking/ |
| D | checksum-offloads.rst | 38 Because csum_offset cannot be negative, this ensures that the previous value of
53 software. This is OK because when we build the IP header, we obviously have it
56 The requirements for GSO are more complicated, because when segmenting an
88 to the complement of the sum of the pseudo header, because everything else gets
89 'cancelled out' by the checksum field. This is because the sum was
|
| /Documentation/i2c/ |
| D | gpio-fault-injection.rst | 26 because the bus master under test will not be able to clock. It should detect
39 succeed because SDA is still pinned low until you manually release it again
61 transmitted. Because the device will ACK its presence, this results in SDA
74 because it acknowledges data. However, there are two differences compared to
103 There doesn't need to be a device at this address because arbitration lost
|
| D | ten-bit-addresses.rst | 20 * Not all bus drivers support 10-bit addresses. Some don't because the
22 support for example), some don't because nobody bothered adding the
|
| /Documentation/devicetree/bindings/bus/ |
| D | fsl,spba-bus.yaml | 17 "simple-bus" because the SDMA controller uses this compatible flag to
19 the SDMA can access. There are no special clocks for the bus, because
|
| /Documentation/scheduler/ |
| D | sched-nice-design.rst | 12 scheduler, (otherwise we'd have done it long ago) because nice level
45 we felt to be a bit excessive. Excessive _not_ because it's too small of
46 a CPU utilization, but because it causes too frequent (once per
51 So for HZ=1000 we changed nice +19 to 5msecs, because that felt like the
|
| /Documentation/filesystems/bcachefs/ |
| D | CodingStyle.rst | 67 issue is that we don't know where the issue is because we can't see what's
76 Pretty printers are wonderful, because they compose and you can use them
141 existing code. Sometimes these can be the best projects, because they can lead
160 often go astray - doing something because it seems like it'll be useful often
175 time is being wasted because your tools are bad or too slow - don't accept it,
184 need to exist because the code was so straightforward as to be obvious;
|
| /Documentation/trace/rv/ |
| D | monitor_wip.rst | 30 The wakeup event always takes place with preemption disabled because
31 of the scheduler synchronization. However, because the preempt_count
|
| /Documentation/admin-guide/device-mapper/ |
| D | vdo-design.rst | 16 Because deduplication rates fall drastically as the block size increases, a
38 than most other targets. Furthermore, because vdo must operate on small
55 operations, because vdo guarantees that no other thread will alter those
87 because it is too costly to update the index when a block is over-written
92 have the same name. In practice, this is extremely unlikely, but because
94 constructed. Because of these inaccuracies, vdo treats the locations in the
152 Because we expect the hashes to be randomly distributed, the size of the
153 deltas follows an exponential distribution. Because of this distribution,
157 table, but it is slightly more expensive to look up entries, because a
167 than that, the index will not be able to find it because the records of the
[all …]
|
| /Documentation/userspace-api/media/dvb/ |
| D | legacy_dvb_decoder_api.rst | 31 Querying capabilities are rarely used because they are already known.
40 Because of that fact the only supported data formats are ISO/IEC 13818-1
|
| /Documentation/arch/x86/ |
| D | usb-legacy-support.rst | 24 system crashes, because the SMM BIOS is not expecting to be in PAE mode.
28 because the SMM BIOS isn't expecting the CPU to be in 64-bit mode. The
|
| /Documentation/dev-tools/ |
| D | sparse.rst | 29 there because sparse will complain about casting to/from a bitwise type,
30 but in this case we really _do_ want to force the conversion). And because
51 This is because "bitwise" (as the name implies) was designed for making
|
| /Documentation/bpf/ |
| D | bpf_prog_run.rst | 86 because the program execution is not happening in driver context, an
106 batch at a time, except when a packet is dropped (by return code or because
109 (because the XDP program returns ``XDP_PASS``, or because it ends up being
|
12345678910>>...35