| /linux-6.14.4/Documentation/rust/ |
| D | quick-start.rst | 33 Arch Linux provides recent Rust releases and thus it should generally work out
43 recent Rust releases and thus they should generally work out of the box, e.g.::
51 Fedora Linux provides recent Rust releases and thus it should generally work out
61 and thus it should generally work out of the box, e.g.::
71 Nix (unstable channel) provides recent Rust releases and thus it should
84 openSUSE Slowroll and openSUSE Tumbleweed provide recent Rust releases and thus
93 Ubuntu LTS and non-LTS (interim) releases provide recent Rust releases and thus
104 thus ``bindgen`` may need to be built manually (please see below).
154 The components are installed per toolchain, thus upgrading the Rust compiler
231 thus nothing needs to be done. If another profile is being used, the component
[all …]
|
| D | testing.rst | 65 (thus enforcing they are kept in sync with the code they document) and as well
105 code, thus also benefitting from extra linting.
123 Thus, we presently simply print an error to the kernel log if an assertion
135 (currently) and thus is fairly limited in what these tests can test.
|
| /linux-6.14.4/Documentation/locking/ |
| D | locktypes.rst | 126 semaphores have no concept of owners, thus preventing PREEMPT_RT from
137 On non-PREEMPT_RT kernels the implementation is fair, thus preventing
148 implementation, thus changing the fairness:
152 thus starving even high-priority writers. In contrast, because readers
154 have its priority boosted until it releases the lock, thus preventing that
192 PREEMPT_RT kernels map local_lock to a per-CPU spinlock_t, thus changing
219 critical section is tiny, thus avoiding RT-mutex overhead.
303 thus preventing writer starvation.
309 implementation, thus changing semantics:
315 thus starving even high-priority writers. In contrast, because readers
[all …]
|
| /linux-6.14.4/fs/bcachefs/ |
| D | extents_format.h | 11 * represent extents that have been partially overwritten and thus trimmed:
20 * Thus an extent that is not checksummed or compressed will consist only of a
29 * Thus, in addition to the current size of the extent in struct bkey, we need
44 * in a bucket that has become heavily fragmented, and thus is being rewritten
47 * Thus it will only move a subset of the pointers (or in the case of
57 * Thus, a bch_extent consists of bch_extent_crc32s, bch_extent_crc64s, and
|
| /linux-6.14.4/Documentation/networking/device_drivers/ethernet/toshiba/ |
| D | spider_net.rst | 46 marks it full, and advances the GDACTDPA by one. Thus, when there is
55 and advance the tail pointer. Thus, when there is flowing RX traffic,
67 then mark the descr as "empty", ready to receive data. Thus, when there
74 Thus, in an idle system, the GDACTDPA, tail and head pointers will
157 marked xa... which is "empty". Thus, from the OS point of view, there
164 Since its already full, the hardware can do nothing more, and thus has
167 descr 254, since tail was at 255.) Thus, the system is deadlocked,
|
| /linux-6.14.4/Documentation/staging/ |
| D | static-keys.rst | 63 functionality. Thus, it is highly desirable to reduce their impact as much as
85 Thus, by default the 'printk' will not be emitted. And the code generated will
89 out-of-line true branch. Thus, changing branch direction is expensive but
144 Thus, 'static_branch_inc()' means 'make the branch true', and
161 thus a sure deadlock recipe. In order to still allow use of the
272 Thus, the disable jump label case adds a 'mov', 'test' and 'jne' instruction
274 to a 5 byte atomic no-op instruction at boot-time.) Thus, the disabled jump
281 function is 80 bytes long. Thus, we have saved 20% of the instruction
|
| D | crc32.rst | 17 subtract, we just xor. Thus, we tend to get a bit sloppy about
58 32 bits later. Thus, the first 32 cycles of this are pretty boring.
153 takes barely longer than a single table look-up and thus performs almost
164 been completed. Thus, the processor's load/store unit is sometimes idle.
170 on the previous CRC at all. Thus, those 4 table look-ups may commence
179 of a polynomial produces a larger multiple of that polynomial. Thus,
|
| /linux-6.14.4/Documentation/ABI/testing/ |
| D | sysfs-bus-pci-devices-aer_stats | 18 be reported using a single ERR_COR message, thus
39 be reported using a single ERR_FATAL message, thus
69 may be reported using a single ERR_FATAL message, thus
100 device, so these counters include them and are thus cumulative of all the error
|
| /linux-6.14.4/Documentation/devicetree/bindings/regulator/ |
| D | lltc,ltc3676.yaml | 40 steps. The output voltage thus ranges between 0.4125 * (1 + R1/R2) V
42 Regulators LDO1, LDO2, LDO4 have a fixed 0.725 V reference and thus
44 The LDO1 standby regulator can not be disabled and thus should have
65 The LDO1 standby regulator can not be disabled and thus should
|
| D | ltc3589.txt | 21 0.3625 V to 0.75 V in 12.5 mV steps. The output voltage thus ranges between
23 have a fixed 0.8 V reference and thus output 0.8 * (1 + R1/R2) V. The ldo3
27 be disabled and thus should have the regulator-always-on property set.
|
| /linux-6.14.4/Documentation/security/tpm/ |
| D | tpm-security.rst | 45 send arbitrary PCR extends and thus disrupt the measurement system,
123 off version that tampering has occurred. Thus it becomes possible to
136 known (and usually empty). Thus, every HMAC session used by the
138 which thus provides a cryptographic input into the session key
139 derivation. Thus, the kernel creates the null primary key once (as a
184 attestation is done by the TPM owner who thus has access to only the
191 the encrypted parameter and thus the TPM will not be able to perform
|
| /linux-6.14.4/Documentation/hid/ |
| D | hidreport-parsing.rst | 34 function is ``Usage Page``, thus for parsing the value 0x01 in the second byte
38 the HUT. We have a ``Usage Page``, thus we need to refer to HUT
44 and is a ``Local`` item (``10``). Thus, the meaning of the remaining four bits
|
| /linux-6.14.4/Documentation/hwmon/ |
| D | abituguru3.rst | 16 firmware and thus effectively many different revisions of the uGuru.
41 detection to be skipped, and thus the insmod to
43 driver will not load and thus no hwmon device will get
|
| D | abituguru.rst | 20 firmware and thus effectively many different revisions of the uGuru.
56 detection to be skipped, and thus the insmod to
58 driver will not load and thus no hwmon device will get
|
| /linux-6.14.4/Documentation/networking/ |
| D | representors.rst | 29 representors. The PF can thus always communicate freely with the virtual
34 Thus, a representor is both a control plane object (representing the function in
97 Thus, the following should all have representors:
137 thus use some other channel such as devlink.
141 run over the virtual switch and the virtio-blk PF should thus *not* have a
187 that representor netdevice. Thus, if the delivery part of the rule corresponds
192 software) send the packet through the representor (and thus indirectly deliver
|
| /linux-6.14.4/Documentation/virt/kvm/ |
| D | halt-polling.rst | 19 invoked. Thus halt polling is especially useful on workloads with very short
45 Thus this is a per vcpu (or vcore) value.
49 received during the polling interval (and thus schedule is invoked) there are
143 entire block time and thus cpu utilisation will go to 100%.
152 allow that other task to run. Thus this doesn't allow a guest to cause denial of service
|
| /linux-6.14.4/Documentation/devicetree/bindings/clock/ |
| D | dove-divider-clock.txt | 5 the PMU, and thus this node should be a child of the PMU node.
20 Core PLL and Clock Divider Control 1 register. Thus, it will have
|
| /linux-6.14.4/Documentation/sound/hd-audio/ |
| D | notes.rst | 117 Thus, if the second error message appears, try to narrow the probed
140 thus we disabled MSI for them.
192 Thus, if you have a newer machine with a slightly different PCI SSID
206 Thus, the first thing you can do for any brand-new, unsupported and
236 the external amplifier bits. Thus a headphone output has a slightly
278 Thus, before submitting a bug report, make sure that you set up the
297 Most of modern laptops have no analog CD-input connection. Thus, the
327 the controller chip. Thus, even if lspci shows the Nvidia controller,
337 Thus, it'd be better to turn this on always.
439 via sysfs or a patch file, you can disable the jack detection, thus
[all …]
|
| /linux-6.14.4/drivers/pinctrl/aspeed/ |
| D | pinmux-aspeed.c | 36 * outcome: The bitfields can be greater than one bit in size and thus can take
39 * is enabled). Thus we must explicitly test for either condition as required.
80 * neither the enabled nor disabled state. Thus we must explicitly test for
|
| /linux-6.14.4/Documentation/devicetree/bindings/iio/adc/ |
| D | renesas,rcar-gyroadc.yaml | 71 data as it contains four ADCs on the chip and thus for 4-channel
80 thus for 8-channel operation, 8 chips are required.
87 Maxim chip supplies single ADC channel with data, thus for
|
| /linux-6.14.4/Documentation/devicetree/bindings/gpio/ |
| D | nvidia,tegra186-gpio.yaml | 43 control a number of GPIOs. Thus, each GPIO is named according to an
62 ports. Thus, the number of interrupt signals generated by a controller
70 for each generated signal to be routed to a different CPU, thus allowing
73 separate register. Thus, a driver needs to know which status register to
|
| /linux-6.14.4/drivers/of/unittest-data/ |
| D | overlay_bad_add_dup_prop.dtso | 9 * Thus the property "rpm_avail" in each fragment will
22 * memory leak and thus people who use kmemleak will not
|
| /linux-6.14.4/Documentation/arch/x86/x86_64/ |
| D | fred.rst | 57 context upon event delivery and return. Thus it avoids the problem of
65 FRED always restores the full value of %rsp, thus ESPFIX is no longer
80 longer needed when FRED is enabled, thus is disallowed (#UD).
|
| /linux-6.14.4/tools/memory-model/litmus-tests/ |
| D | README | 188 complex due to a desire to have short(er) names. Thus, there is a tool to
224 smp_load_acquire(), so next is "Once". Thus far, we have "Rfi Once".
235 thus far is thus "Rfi Once PodRR Once Fre Once".
240 The full string is thus:
|
| /linux-6.14.4/Documentation/bpf/ |
| D | ringbuf.rst | 119 reference-tracking logic, similar to socket ref-tracking. It is thus
182 already committed. It is thus possible for slow producers to temporarily hold
185 One interesting implementation bit, that significantly simplifies (and thus
190 last data page would be first data page again, and thus the sample will still
198 the record being committed. If not, consumer still has to catch up and thus
|