| /Linux-v5.10/tools/perf/pmu-events/arch/x86/ivybridge/ |
| D | memory.json | 42 "PublicDescription": "Loads with latency value being above 4.",
50 "BriefDescription": "Loads with latency value being above 4",
56 "PublicDescription": "Loads with latency value being above 8.",
64 "BriefDescription": "Loads with latency value being above 8",
70 "PublicDescription": "Loads with latency value being above 16.",
78 "BriefDescription": "Loads with latency value being above 16",
84 "PublicDescription": "Loads with latency value being above 32.",
92 "BriefDescription": "Loads with latency value being above 32",
98 "PublicDescription": "Loads with latency value being above 64.",
106 "BriefDescription": "Loads with latency value being above 64",
[all …]
|
| /Linux-v5.10/arch/arm/mach-s3c/ |
| D | gpio-cfg-helpers.h | 57 * @chip: The gpio chip that is being configured.
58 * @off: The offset for the GPIO being configured.
59 * @param: pull: The pull mode being requested.
69 * @chip: The gpio chip that is being configured
70 * @off: The offset for the GPIO being configured
71 * @param: pull: The pull mode being requested
83 * @chip: The gpio chip that is being configured.
84 * @off: The offset for the GPIO being configured.
85 * @param: pull: The pull mode being requested.
134 * @chip: The gpio chip that is being configured.
[all …]
|
| /Linux-v5.10/include/linux/iio/ |
| D | consumer.h | 171 * @chan: The channel being queried.
182 * @chan: The channel being queried.
195 * @chan: The channel being queried.
210 * @chan: The channel being queried.
211 * @val: Value being written.
212 * @val2: Value being written.val2 use depends on attribute type.
222 * @chan: The channel being queried.
223 * @val: Value being written.
224 * @val2: Value being written.Val2 use depends on attribute type.
236 * @chan: The channel being queried.
[all …]
|
| /Linux-v5.10/drivers/iio/dummy/ |
| D | iio_simple_dummy_events.c | 23 * @chan: channel for the event whose state is being queried
24 * @type: type of the event whose state is being queried
25 * @dir: direction of the vent whose state is being queried
43 * @chan: channel for the event whose state is being set
44 * @type: type of the event whose state is being set
45 * @dir: direction of the vent whose state is being set
105 * @chan: channel for the event whose value is being read
106 * @type: type of the event whose value is being read
107 * @dir: direction of the vent whose value is being read
108 * @info: info type of the event whose value is being read
[all …]
|
| /Linux-v5.10/include/linux/ |
| D | wait_bit.h | 56 * @word: the word being waited on, a kernel virtual address
57 * @bit: the bit of the word being waited on
83 * @word: the word being waited on, a kernel virtual address
84 * @bit: the bit of the word being waited on
108 * @word: the word being waited on, a kernel virtual address
109 * @bit: the bit of the word being waited on
135 * @word: the word being waited on, a kernel virtual address
136 * @bit: the bit of the word being waited on
161 * @word: the word being waited on, a kernel virtual address
162 * @bit: the bit of the word being waited on
[all …]
|
| D | llist.h | 18 * if a preemption happens in the middle of the delete operation and on being
33 * operation, with "-" being no lock needed, while "L" being lock is needed.
106 * safely only after being deleted from list, so start with an entry
109 * If being used on entries deleted from lock-less list directly, the
125 * safely only after being deleted from list, so start with an entry
128 * If being used on entries deleted from lock-less list directly, the
143 * safely only after being removed from list, so start with an entry
146 * If being used on entries deleted from lock-less list directly, the
165 * safely only after being removed from list, so start with an entry
168 * If being used on entries deleted from lock-less list directly, the
|
| D | lsm_hooks.h | 18 * Due to this file being licensed under the GPL there is controversy over
53 * when reopend may end up being a completely different file. This
71 * Prepare to install the new security attributes of a process being
81 * process being transformed by an execve operation. The new credentials
129 * pathname of the object being mounted.
130 * @dev_name contains the name for object being mounted.
147 * are being made to those options.
148 * @sb superblock being remounted
223 * being responsible for calling kfree after using them.
313 * is being done for a regular file, then the create hook will be called
[all …]
|
| /Linux-v5.10/Documentation/ABI/testing/ |
| D | configfs-most | 44 collected from the network before being
61 a physical device is being attached to the bus.
99 collected from the network before being
116 a physical device is being attached to the bus.
154 collected from the network before being
171 a physical device is being attached to the bus.
220 collected from the network before being
237 a physical device is being attached to the bus.
|
| /Linux-v5.10/tools/perf/pmu-events/arch/x86/broadwell/ |
| D | frontend.json | 3 … be bound in the front end. It does not determine whether there are uops being delivered to the A…
13 … includes uops that may bypass the IDQ. This also means that uops are not being delivered from the…
23 …"PublicDescription": "This event counts cycles during which uops are being delivered to Instructio…
29 …"BriefDescription": "Cycles when uops are being delivered to Instruction Decode Queue (IDQ) from M…
44 …"PublicDescription": "This event counts cycles during which uops are being delivered to Instructio…
50 …"BriefDescription": "Cycles when uops are being delivered to Instruction Decode Queue (IDQ) from D…
55 …ounts the number of uops initiated by Decode Stream Buffer (DSB) that are being delivered to Instr…
61 …"BriefDescription": "Uops initiated by Decode Stream Buffer (DSB) that are being delivered to Inst…
65 …unts cycles during which uops initiated by Decode Stream Buffer (DSB) are being delivered to Instr…
71 …"BriefDescription": "Cycles when uops initiated by Decode Stream Buffer (DSB) are being delivered …
[all …]
|
| /Linux-v5.10/tools/perf/pmu-events/arch/x86/broadwellde/ |
| D | frontend.json | 8 … be bound in the front end. It does not determine whether there are uops being delivered to the A…
18 … includes uops that may bypass the IDQ. This also means that uops are not being delivered from the…
25 …"BriefDescription": "Cycles when uops are being delivered to Instruction Decode Queue (IDQ) from M…
29 …"PublicDescription": "This event counts cycles during which uops are being delivered to Instructio…
46 …"BriefDescription": "Cycles when uops are being delivered to Instruction Decode Queue (IDQ) from D…
50 …"PublicDescription": "This event counts cycles during which uops are being delivered to Instructio…
57 …"BriefDescription": "Uops initiated by Decode Stream Buffer (DSB) that are being delivered to Inst…
60 …ounts the number of uops initiated by Decode Stream Buffer (DSB) that are being delivered to Instr…
67 …"BriefDescription": "Cycles when uops initiated by Decode Stream Buffer (DSB) are being delivered …
71 …unts cycles during which uops initiated by Decode Stream Buffer (DSB) are being delivered to Instr…
[all …]
|
| D | memory.json | 315 "BriefDescription": "Loads with latency value being above 4",
322 "PublicDescription": "This event counts loads with latency value being above four.",
330 "BriefDescription": "Loads with latency value being above 8",
337 "PublicDescription": "This event counts loads with latency value being above eight.",
345 "BriefDescription": "Loads with latency value being above 16",
352 "PublicDescription": "This event counts loads with latency value being above 16.",
360 "BriefDescription": "Loads with latency value being above 32",
367 "PublicDescription": "This event counts loads with latency value being above 32.",
375 "BriefDescription": "Loads with latency value being above 64",
382 "PublicDescription": "This event counts loads with latency value being above 64.",
[all …]
|
| /Linux-v5.10/tools/perf/pmu-events/arch/x86/broadwellx/ |
| D | frontend.json | 8 … be bound in the front end. It does not determine whether there are uops being delivered to the A…
18 … includes uops that may bypass the IDQ. This also means that uops are not being delivered from the…
25 …"BriefDescription": "Cycles when uops are being delivered to Instruction Decode Queue (IDQ) from M…
29 …"PublicDescription": "This event counts cycles during which uops are being delivered to Instructio…
46 …"BriefDescription": "Cycles when uops are being delivered to Instruction Decode Queue (IDQ) from D…
50 …"PublicDescription": "This event counts cycles during which uops are being delivered to Instructio…
57 …"BriefDescription": "Uops initiated by Decode Stream Buffer (DSB) that are being delivered to Inst…
60 …ounts the number of uops initiated by Decode Stream Buffer (DSB) that are being delivered to Instr…
67 …"BriefDescription": "Cycles when uops initiated by Decode Stream Buffer (DSB) are being delivered …
71 …unts cycles during which uops initiated by Decode Stream Buffer (DSB) are being delivered to Instr…
[all …]
|
| /Linux-v5.10/tools/perf/pmu-events/arch/x86/ivytown/ |
| D | memory.json | 33 "PublicDescription": "Loads with latency value being above 4.",
41 "BriefDescription": "Loads with latency value being above 4",
47 "PublicDescription": "Loads with latency value being above 8.",
55 "BriefDescription": "Loads with latency value being above 8",
61 "PublicDescription": "Loads with latency value being above 16.",
69 "BriefDescription": "Loads with latency value being above 16",
75 "PublicDescription": "Loads with latency value being above 32.",
83 "BriefDescription": "Loads with latency value being above 32",
89 "PublicDescription": "Loads with latency value being above 64.",
97 "BriefDescription": "Loads with latency value being above 64",
[all …]
|
| D | frontend.json | 23 …"PublicDescription": "Cycles when uops are being delivered to Instruction Decode Queue (IDQ) from …
29 …"BriefDescription": "Cycles when uops are being delivered to Instruction Decode Queue (IDQ) from M…
44 …"PublicDescription": "Cycles when uops are being delivered to Instruction Decode Queue (IDQ) from …
50 …"BriefDescription": "Cycles when uops are being delivered to Instruction Decode Queue (IDQ) from D…
61 …"BriefDescription": "Uops initiated by Decode Stream Buffer (DSB) that are being delivered to Inst…
65 …"PublicDescription": "Cycles when uops initiated by Decode Stream Buffer (DSB) are being delivered…
71 …"BriefDescription": "Cycles when uops initiated by Decode Stream Buffer (DSB) are being delivered …
152 …"PublicDescription": "Cycles when uops are being delivered to Instruction Decode Queue (IDQ) while…
158 …"BriefDescription": "Cycles when uops are being delivered to Instruction Decode Queue (IDQ) while …
|
| /Linux-v5.10/crypto/asymmetric_keys/ |
| D | restrict.c | 55 * @dest_keyring: Keyring being linked to.
56 * @type: The type of key being added.
62 * new certificate as being trusted.
160 * one that is being considered for addition to in key_or_keyring_common()
215 * @dest_keyring: Keyring being linked to.
216 * @type: The type of key being added.
222 * certificate, then mark the new certificate as being ok to link.
242 * @dest_keyring: Keyring being linked to.
243 * @type: The type of key being added.
249 * certificate, then mark the new certificate as being ok to link.
|
| /Linux-v5.10/drivers/extcon/ |
| D | devres.c | 54 * @dev: the device owning the extcon device being created
91 * @dev: the device owning the extcon device being created
106 * @dev: the device owning the extcon device being created
142 * @dev: the device owning the extcon device being created
157 * @dev: the device owning the extcon device being created
201 * @dev: the device owning the extcon device being created
218 * @dev: the device owning the extcon device being created
256 * @dev: the device owning the extcon device being created
|
| /Linux-v5.10/drivers/base/power/ |
| D | main.c | 95 * @dev: Device object being initialized.
346 * @state: PM transition of the system being carried out.
377 * @state: PM transition of the system being carried out.
379 * Runtime PM is disabled for @dev while this function is being executed.
411 * @state: PM transition of the system being carried out.
413 * The driver of @dev will not receive interrupts while this function is being
587 * @state: PM transition of the system being carried out.
588 * @async: If true, the device is being resumed asynchronously.
590 * The driver of @dev will not receive interrupts while this function is being
741 * @state: PM transition of the system being carried out.
[all …]
|
| /Linux-v5.10/Documentation/firmware-guide/acpi/ |
| D | method-tracing.rst | 44 are being evaluated::
52 control method is being evaluated::
61 control method is being evaluated for the first time::
110 methods are being evaluated::
118 control method is being evaluated::
127 control method is being evaluated for the first time::
136 specified control method is being evaluated::
145 specified control method is being evaluated for the first time::
|
| /Linux-v5.10/arch/mips/kernel/ |
| D | elf.c | 30 * @single: The program being loaded needs an FPU but it will only issue
33 * @soft: The soft(-float) requirement means that the program being
36 * @fr1: The program being loaded depends on FPU being in FR=1 mode.
37 * @frdefault: The program being loaded depends on the default FPU mode.
39 * @fre: The program being loaded depends on FPU with FRE=1. This mode is
40 * a bridge which uses FR=1 whilst still being able to maintain
242 * will only use single-precision instructions, shown by single being in arch_check_elf()
243 * true but frdefault being false, then we again set the FPU mode to in arch_check_elf()
|
| /Linux-v5.10/tools/perf/Documentation/ |
| D | perf-diff.txt | 251 - A/B being matching hist entry from data/baseline file specified
254 - period_percent being the % of the hist entry period value within
272 - A/B being matching hist entry from data/baseline file specified
275 - period being the hist entry period value
283 - A/B being matching hist entry from data/baseline file specified
286 - period being the hist entry period value
288 - WEIGHT-A/WEIGHT-B being user supplied weights in the the '-c' option
290 - WEIGHT-A being the weight of the data file
291 - WEIGHT-B being the weight of the baseline data file
|
| /Linux-v5.10/Documentation/networking/ |
| D | x25.rst | 16 Packet Layer is concerned, the link layer was being performed by a lower
22 To confuse matters a little, an 802.2 LLC implementation for Linux is being
26 being served by the LLC will be completely separate from LAPB. The LLC
27 implementation is being done as part of another protocol project (SNA) and
|
| /Linux-v5.10/Documentation/process/ |
| D | management-style.rst | 97 the first place, and your decision ended up being a big one after
126 answer may end up being that both teams get so frustrated by the
139 Most people are idiots, and being a manager means you'll have to deal
166 right), the harder it ends up being to apologize afterwards.
175 The option of being unfailingly polite really doesn't exist. Nobody will
245 There's one thing people hate even more than being called "d*ckhead",
246 and that is being called a "d*ckhead" in a sanctimonious voice. The
259 internet, nobody can hear you being subtle". Use a big blunt object to
264 overboard to the point of being ridiculous can drive a point home
265 without making it painful to the recipient, who just thinks you're being
[all …]
|
| /Linux-v5.10/Documentation/admin-guide/ |
| D | kernel-per-CPU-kthreads.rst | 47 kthreads from being created in the first place. (This will
114 from being initiated from tasks that might run on the CPU to
126 from being initiated from tasks that might run on the CPU to
138 from being initiated from tasks that might run on the CPU to
167 chances of being selected to do the load balancing work that
303 kthreads from being created in the first place, and also obviates
307 kthreads from being created in the first place. This approach
317 another way of preventing any callbacks from being queued on the
332 kthreads from being created in the first place. However, please
345 kthreads from being created in the first place.
[all …]
|
| /Linux-v5.10/arch/powerpc/include/asm/ |
| D | barrier.h | 22 * mb() prevents loads and stores being reordered across this point.
23 * rmb() prevents loads being reordered across this point.
24 * wmb() prevents stores being reordered across this point.
60 * This is a barrier which prevents following instructions from being
63 * instructions from being executed until the load has been performed.
|
| /Linux-v5.10/Documentation/dev-tools/kunit/ |
| D | style.rst | 34 the code being tested can't be compiled as a module, in many cases the subsystem
39 Test subsystems should be named after the code being tested, either after the
40 module (wherever possible), or after the directory or files being tested. Test
82 functionality being tested. Test suites can have shared initialisation and
132 function being tested, with a description of the input or codepath being tested.
164 * be listed either alongside the config entries for the driver/subsystem being
|
