| /kernel/linux/linux-4.19/Documentation/devicetree/bindings/devfreq/ |
| D | rk3399_dmc.txt | 73 the ODT on the DRAM side and controller side are
77 the DRAM side driver strength in ohms. Default
81 the DRAM side ODT strength in ohms. Default value
85 the phy side CA line (incluing command line,
90 the PHY side DQ line (including DQS/DQ/DM line)
94 the PHY side ODT strength. Default value is
100 the ODT on the DRAM side and controller side are
104 the DRAM side driver strength in ohms. Default
108 the DRAM side ODT strength in ohms. Default value
112 the PHY side CA line (including command line,
[all …]
|
| /kernel/linux/linux-5.10/Documentation/devicetree/bindings/devfreq/ |
| D | rk3399_dmc.txt | 75 the ODT on the DRAM side and controller side are
79 the DRAM side driver strength in ohms. Default
83 the DRAM side ODT strength in ohms. Default value
87 the phy side CA line (incluing command line,
92 the PHY side DQ line (including DQS/DQ/DM line)
96 the PHY side ODT strength. Default value is
102 the ODT on the DRAM side and controller side are
106 the DRAM side driver strength in ohms. Default
110 the DRAM side ODT strength in ohms. Default value
114 the PHY side CA line (including command line,
[all …]
|
| /kernel/linux/linux-5.10/tools/perf/pmu-events/arch/powerpc/power8/ |
| D | translation.json | 29 …r chip's L2 or L3 on a different Node or Group (Distant), as this chip due to a data side request",
35 …r chip's L2 or L3 on a different Node or Group (Distant), as this chip due to a data side request",
41 …ion": "A Page Table Entry was loaded into the TLB from local core's L2 due to a data side request",
47 …was loaded into the TLB from a location other than the local core's L2 due to a data side request",
53 …TLB from local core's L2 hit without dispatch conflicts on Mepf state. due to a data side request",
59 …le Entry was loaded into the TLB from local core's L2 without conflict due to a data side request",
65 …ion": "A Page Table Entry was loaded into the TLB from local core's L3 due to a data side request",
71 …ry was loaded into the TLB from local core's L3 with dispatch conflict due to a data side request",
77 …TLB from local core's L3 without dispatch conflicts hit on Mepf state. due to a data side request",
83 …le Entry was loaded into the TLB from local core's L3 without conflict due to a data side request",
[all …]
|
| D | marked.json | 365 …s L2 or L3 on a different Node or Group (Distant), as this chip due to a marked data side request",
371 …s L2 or L3 on a different Node or Group (Distant), as this chip due to a marked data side request",
377 …B from another chip's L4 on a different Node or Group (Distant) due to a marked data side request",
383 … from another chip's memory on the same Node or Group (Distant) due to a marked data side request",
389 …A Page Table Entry was loaded into the TLB from local core's L2 due to a marked data side request",
395 …ded into the TLB from a location other than the local core's L2 due to a marked data side request",
401 …m local core's L2 hit without dispatch conflicts on Mepf state. due to a marked data side request",
407 …y was loaded into the TLB from local core's L2 without conflict due to a marked data side request",
413 …A Page Table Entry was loaded into the TLB from local core's L3 due to a marked data side request",
419 …ded into the TLB from a location other than the local core's L3 due to a marked data side request",
[all …]
|
| D | frontend.json | 293 …s L2 or L3 on a different Node or Group (Distant), as this chip due to a instruction side request",
299 …s L2 or L3 on a different Node or Group (Distant), as this chip due to a instruction side request",
305 …B from another chip's L4 on a different Node or Group (Distant) due to a instruction side request",
311 … from another chip's memory on the same Node or Group (Distant) due to a instruction side request",
317 …A Page Table Entry was loaded into the TLB from local core's L2 due to a instruction side request",
323 …ded into the TLB from a location other than the local core's L2 due to a instruction side request",
329 …m local core's L2 hit without dispatch conflicts on Mepf state. due to a instruction side request",
335 …y was loaded into the TLB from local core's L2 without conflict due to a instruction side request",
341 …A Page Table Entry was loaded into the TLB from local core's L3 due to a instruction side request",
347 …ded into the TLB from a location other than the local core's L3 due to a instruction side request",
[all …]
|
| /kernel/linux/linux-4.19/tools/perf/pmu-events/arch/powerpc/power8/ |
| D | translation.json | 29 …r chip's L2 or L3 on a different Node or Group (Distant), as this chip due to a data side request",
35 …r chip's L2 or L3 on a different Node or Group (Distant), as this chip due to a data side request",
41 …ion": "A Page Table Entry was loaded into the TLB from local core's L2 due to a data side request",
47 …as loaded into the TLB from a localtion other than the local core's L2 due to a data side request",
53 …TLB from local core's L2 hit without dispatch conflicts on Mepf state. due to a data side request",
59 …le Entry was loaded into the TLB from local core's L2 without conflict due to a data side request",
65 …ion": "A Page Table Entry was loaded into the TLB from local core's L3 due to a data side request",
71 …ry was loaded into the TLB from local core's L3 with dispatch conflict due to a data side request",
77 …TLB from local core's L3 without dispatch conflicts hit on Mepf state. due to a data side request",
83 …le Entry was loaded into the TLB from local core's L3 without conflict due to a data side request",
[all …]
|
| /kernel/linux/linux-5.10/drivers/char/hw_random/ |
| D | Kconfig | 28 This driver provides kernel-side support for a generic Random
43 This driver provides kernel-side support for the Random Number
56 This driver provides kernel-side support for the Random Number
69 This driver provides kernel-side support for the Random Number
81 This driver provides kernel-side support for the Random Number
93 This driver provides kernel-side support for the Random Number
106 This driver provides kernel-side support for the RNG200
119 This driver provides kernel-side support for the Random Number
132 This driver provides kernel-side support for the Random Number
145 This driver provides kernel-side support for the Random Number
[all …]
|
| /kernel/linux/linux-4.19/drivers/char/hw_random/ |
| D | Kconfig | 27 This driver provides kernel-side support for a generic Random
42 This driver provides kernel-side support for the Random Number
55 This driver provides kernel-side support for the Random Number
68 This driver provides kernel-side support for the Random Number
82 This driver provides kernel-side support for the Random Number
95 This driver provides kernel-side support for the RNG200
108 This driver provides kernel-side support for the Random Number
121 This driver provides kernel-side support for the Random Number
134 This driver provides kernel-side support for the Random Number
147 This driver provides kernel-side support for the Pseudo-Random
[all …]
|
| /kernel/linux/linux-5.10/Documentation/locking/ |
| D | seqlock.rst | 15 read side critical section is even and the same sequence count value is
17 be copied out inside the read side critical section. If the sequence
24 the end of the write side critical section the sequence count becomes
27 A sequence counter write side critical section must never be preempted
28 or interrupted by read side sections. Otherwise the reader will spin for
43 multiple writers. Write side critical sections must thus be serialized
48 write side section. If the read section can be invoked from hardirq or
76 /* ... [[write-side critical section]] ... */
85 /* ... [[read-side critical section]] ... */
95 As discussed at :ref:`seqcount_t`, sequence count write side critical
[all …]
|
| /kernel/linux/linux-4.19/Documentation/usb/ |
| D | gadget_serial.txt | 54 side driver. It runs on a Linux system that has USB device side
63 | Host-Side CDC ACM USB Host |
75 | Device-Side | Gadget | Controller | |
81 On the device-side Linux system, the gadget serial driver looks
84 On the host-side system, the gadget serial device looks like a
89 The host side driver can potentially be any ACM compliant driver
95 With the gadget serial driver and the host side ACM or generic
97 the host and the gadget side systems as if they were connected by a
108 side kernel for "Support for USB Gadgets", for a "USB Peripheral
125 side Linux system. You can add this to the start up scripts, if
[all …]
|
| /kernel/linux/linux-5.10/tools/perf/pmu-events/arch/x86/silvermont/ |
| D | virtual-memory.json | 19 "BriefDescription": "D-side page-walks",
23 …"PublicDescription": "This event counts every cycle when a D-side (walks due to a load) page walk …
29 "BriefDescription": "Duration of D-side page-walks in core cycles"
38 "BriefDescription": "I-side page-walks",
42 …"PublicDescription": "This event counts every cycle when a I-side (walks due to an instruction fet…
48 "BriefDescription": "Duration of I-side page-walks in core cycles"
57 "BriefDescription": "Total page walks that are completed (I-side and D-side)",
67 "BriefDescription": "Total cycles for all the page walks. (I-side and D-side)"
|
| /kernel/linux/linux-4.19/tools/perf/pmu-events/arch/x86/silvermont/ |
| D | virtual-memory.json | 19 "BriefDescription": "D-side page-walks",
23 …"PublicDescription": "This event counts every cycle when a D-side (walks due to a load) page walk …
29 "BriefDescription": "Duration of D-side page-walks in core cycles"
38 "BriefDescription": "I-side page-walks",
42 …"PublicDescription": "This event counts every cycle when a I-side (walks due to an instruction fet…
48 "BriefDescription": "Duration of I-side page-walks in core cycles"
57 "BriefDescription": "Total page walks that are completed (I-side and D-side)",
67 "BriefDescription": "Total cycles for all the page walks. (I-side and D-side)"
|
| /kernel/linux/linux-5.10/Documentation/usb/ |
| D | gadget_serial.rst | 57 side driver. It runs on a Linux system that has USB device side
66 | Host-Side CDC ACM USB Host |
78 | Device-Side | Gadget | Controller | |
84 On the device-side Linux system, the gadget serial driver looks
87 On the host-side system, the gadget serial device looks like a
92 The host side driver can potentially be any ACM compliant driver
98 With the gadget serial driver and the host side ACM or generic
100 the host and the gadget side systems as if they were connected by a
111 side kernel for "Support for USB Gadgets", for a "USB Peripheral
128 side Linux system. You can add this to the start up scripts, if
[all …]
|
| /kernel/linux/linux-4.19/Documentation/RCU/ |
| D | checklist.txt | 14 tool for the job. Yes, RCU does reduce read-side overhead by
15 increasing write-side overhead, which is exactly why normal uses
24 read-side primitives is critically important.
55 2. Do the RCU read-side critical sections make proper use of
59 under your read-side code, which can greatly increase the
64 rcu_read_lock_sched(), or by the appropriate update-side lock.
68 Letting RCU-protected pointers "leak" out of an RCU read-side
72 -before- letting them out of the RCU read-side critical section.
147 perfectly legal (if redundant) for update-side code to
152 of an RCU read-side critical section. See lockdep.txt
[all …]
|
| D | lockdep.txt | 4 aware of when each task enters and leaves any flavor of RCU read-side
27 Check for RCU read-side critical section.
29 Check for RCU-bh read-side critical section.
31 Check for RCU-sched read-side critical section.
33 Check for SRCU read-side critical section.
76 1. An RCU read-side critical section (implicit), or
81 RCU read-side critical sections, in case (2) the ->file_lock prevents
92 complain if this was used in an RCU read-side critical section unless one
101 being in an RCU read-side critical section. In the future, separate
|
| D | whatisRCU.txt | 82 b. Wait for all previous readers to complete their RCU read-side
143 entering an RCU read-side critical section. It is illegal
144 to block while in an RCU read-side critical section, though
146 read-side critical sections. Any RCU-protected data structure
147 accessed during an RCU read-side critical section is guaranteed to
157 exiting an RCU read-side critical section. Note that RCU
158 read-side critical sections may be nested and/or overlapping.
166 read-side critical sections on all CPUs have completed.
168 any subsequent RCU read-side critical sections to complete.
181 read-side critical sections to complete, not necessarily for
[all …]
|
| /kernel/linux/linux-5.10/Documentation/RCU/ |
| D | checklist.rst | 18 tool for the job. Yes, RCU does reduce read-side overhead by
19 increasing write-side overhead, which is exactly why normal uses
28 read-side primitives is critically important.
59 2. Do the RCU read-side critical sections make proper use of
63 under your read-side code, which can greatly increase the
68 rcu_read_lock_sched(), or by the appropriate update-side lock.
72 Letting RCU-protected pointers "leak" out of an RCU read-side
76 -before- letting them out of the RCU read-side critical section.
151 perfectly legal (if redundant) for update-side code to
156 of an RCU read-side critical section. See lockdep.txt
[all …]
|
| D | lockdep.rst | 8 aware of when each task enters and leaves any flavor of RCU read-side
31 Check for RCU read-side critical section.
33 Check for RCU-bh read-side critical section.
35 Check for RCU-sched read-side critical section.
37 Check for SRCU read-side critical section.
80 1. An RCU read-side critical section (implicit), or
85 RCU read-side critical sections, in case (2) the ->file_lock prevents
96 complain if this was used in an RCU read-side critical section unless one
104 traversal primitives check for being called from within an RCU read-side
108 false and they are called from outside any RCU read-side critical section.
[all …]
|
| D | whatisRCU.rst | 94 b. Wait for all previous readers to complete their RCU read-side
157 entering an RCU read-side critical section. It is illegal
158 to block while in an RCU read-side critical section, though
160 read-side critical sections. Any RCU-protected data structure
161 accessed during an RCU read-side critical section is guaranteed to
171 exiting an RCU read-side critical section. Note that RCU
172 read-side critical sections may be nested and/or overlapping.
180 read-side critical sections on all CPUs have completed.
182 any subsequent RCU read-side critical sections to complete.
195 read-side critical sections to complete, not necessarily for
[all …]
|
| /kernel/linux/linux-5.10/tools/perf/pmu-events/arch/x86/knightslanding/ |
| D | virtual-memory.json | 18 …"BriefDescription": "Counts the total D-side page walks that are completed or started. The page wa…
27 …"BriefDescription": "Counts the total number of core cycles for all the D-side page walks. The cyc…
35 "BriefDescription": "Counts the total I-side page walks that are completed.",
39 …"PublicDescription": "This event counts every cycle when an I-side (walks due to an instruction fe…
45 …"BriefDescription": "Counts the total number of core cycles for all the I-side page walks. The cyc…
53 "BriefDescription": "Counts the total page walks that are completed (I-side and D-side)",
|
| /kernel/linux/linux-4.19/tools/perf/pmu-events/arch/x86/knightslanding/ |
| D | virtual-memory.json | 18 …"BriefDescription": "Counts the total D-side page walks that are completed or started. The page wa…
27 …"BriefDescription": "Counts the total number of core cycles for all the D-side page walks. The cyc…
35 "BriefDescription": "Counts the total I-side page walks that are completed.",
39 …"PublicDescription": "This event counts every cycle when an I-side (walks due to an instruction fe…
45 …"BriefDescription": "Counts the total number of core cycles for all the I-side page walks. The cyc…
53 "BriefDescription": "Counts the total page walks that are completed (I-side and D-side)",
|
| /kernel/linux/linux-5.10/include/linux/ |
| D | srcu.h | 70 * srcu_read_lock_held - might we be in SRCU read-side critical section?
74 * read-side critical section. In absence of CONFIG_DEBUG_LOCK_ALLOC,
75 * this assumes we are in an SRCU read-side critical section unless it can
105 * really are in an SRCU read-side critical section.
106 * @c: condition to check for update-side use
108 * If PROVE_RCU is enabled, invoking this outside of an RCU read-side
120 * really are in an SRCU read-side critical section.
123 * is enabled, invoking this outside of an RCU read-side critical
132 * really are in an SRCU read-side critical section.
140 * Enter an SRCU read-side critical section. Note that SRCU read-side
[all …]
|
| /kernel/linux/linux-4.19/Documentation/RCU/Design/Requirements/ |
| D | Requirements.html | 23 which means that RCU's read-side primitives can be exceedingly fast
100 of all pre-existing RCU read-side critical sections.
101 An RCU read-side critical section
105 big RCU read-side critical section.
170 update-side code does run concurrently with readers, whether
219 The RCU read-side critical section in <tt>do_something_dlm()</tt>
242 an RCU read-side critical section must not contain calls to
244 Similarly, an RCU read-side critical section must not
251 it would be good to be able to use RCU to coordinate read-side
463 outermost RCU read-side critical section containing that
[all …]
|
| /kernel/linux/linux-5.10/tools/perf/pmu-events/arch/powerpc/power9/ |
| D | translation.json | 25 …m another chip's memory on the same Node or Group (Distant) due to a data side request. When using…
35 …chip's L2 or L3 on the same Node or Group (Remote), as this chip due to a instruction side request"
60 … or L3 on a different Node or Group (Distant), as this chip due to a data side request. When using…
75 …ared or modified data from another core's L2/L3 on the same chip due to a instruction side request"
100 …e TLB from another chip's L4 on the same Node or Group ( Remote) due to a instruction side request"
145 …from a memory location including L4 from local remote or distant due to a instruction side request"
150 …rom another core's L2/L3 on a different chip (remote or distant) due to a instruction side request"
165 … or L3 on a different Node or Group (Distant), as this chip due to a data side request. When using…
185 …om another chip's L4 on a different Node or Group (Distant) due to a data side request. When using…
210 …chip's L2 or L3 on the same Node or Group (Remote), as this chip due to a instruction side request"
[all …]
|
| /kernel/linux/linux-5.10/Documentation/RCU/Design/Requirements/ |
| D | Requirements.rst | 20 updaters do not block readers, which means that RCU's read-side
74 of all pre-existing RCU read-side critical sections. An RCU read-side
77 RCU treats a nested set as one big RCU read-side critical section.
131 | Second, even when using ``synchronize_rcu()``, the other update-side |
173 The RCU read-side critical section in ``do_something_dlm()`` works with
190 In order to avoid fatal problems such as deadlocks, an RCU read-side
192 Similarly, an RCU read-side critical section must not contain anything
198 be good to be able to use RCU to coordinate read-side access to linked
372 outermost RCU read-side critical section containing that
386 #. Wait for all pre-existing RCU read-side critical sections to complete
[all …]
|