| /Linux-v5.4/sound/soc/sof/intel/ |
| D | Kconfig | 17 This option is not user-selectable but automagically handled by
33 This option is not user-selectable but automagically handled by
39 This option is not user-selectable but automagically handled by
47 This option is not user-selectable but automagically handled by
57 This option is not user-selectable but automagically handled by
74 This option is not user-selectable but automagically handled by
90 This option is not user-selectable but automagically handled by
109 This option is not user-selectable but automagically handled by
124 This option is not user-selectable but automagically handled by
139 This option is not user-selectable but automagically handled by
[all …]
|
| /Linux-v5.4/tools/perf/pmu-events/arch/x86/amdfam17h/ |
| D | other.json | 20 …"PublicDescription": "Cycles where a dispatch group is valid but does not get dispatched due to a …
27 …"PublicDescription": "Cycles where a dispatch group is valid but does not get dispatched due to a …
34 …"PublicDescription": "Cycles where a dispatch group is valid but does not get dispatched due to a …
40 …"BriefDescription": "Cycles where a dispatch group is valid but does not get dispatched due to a t…
41 …"PublicDescription": "Cycles where a dispatch group is valid but does not get dispatched due to a …
48 …"PublicDescription": "Cycles where a dispatch group is valid but does not get dispatched due to a …
55 …"PublicDescription": "Cycles where a dispatch group is valid but does not get dispatched due to a …
62 …"PublicDescription": "Cycles where a dispatch group is valid but does not get dispatched due to a …
|
| /Linux-v5.4/Documentation/core-api/ |
| D | timekeeping.rst | 21 accurately. Starts at system boot time but stops during suspend.
27 Like ktime_get(), but does not stop when suspended. This can be
38 persist across a reboot, like inode times, but should be avoided
47 Like ktime_get_real(), but uses the International Atomic Time (TAI)
55 Like ktime_get(), but runs at the same rate as the hardware
71 Same as the plain ktime_get functions, but returning a u64 number
81 Same above, but returns the time in a 'struct timespec64', split
117 These are quicker than the non-coarse versions, but less accurate,
126 but can't easily use 'jiffies', e.g. for inode timestamps.
128 on most modern machines with a reliable cycle counter, but
[all …]
|
| /Linux-v5.4/Documentation/ioctl/ |
| D | botching-up-ioctls.rst | 13 Which is nice, since there's no more insanity in the form of fake-generic, but
14 actually only used once interfaces. But the clear downside is that there's much
34 platforms don't necessarily align 64-bit values to 64-bit boundaries, but
68 but isn't a complete solution since newer userspace on older kernels won't
77 but garbage. This is also the reason why you must explicitly pad all
136 v4l use by default nowadays. But let userspace know which timestamps are
139 will mismatch if you look close enough, but if performance measuring tools
145 convenient time specification, but it's mostly the standard.
156 always be extended - but users will surely hate you if their neat animations
171 A full-blown drm driver essentially implements a little OS, but specialized to
[all …]
|
| /Linux-v5.4/lib/ |
| D | Kconfig | 103 modules require CRC-CCITT functions, but a module built outside
111 modules require CRC16 functions, but a module built outside
128 modules require CRC ITU-T V.41 functions, but a module built outside
138 modules require CRC32/CRC32c functions, but a module built outside
164 This is the fastest algorithm, but comes with a 8KiB lookup table.
175 This is a bit slower than slice by 8, but has a smaller 4KiB lookup
184 is not particularly fast, but has a small 256 byte lookup table.
191 Calculate checksum one bit at a time. This is VERY slow, but has
202 modules require CRC64 functions, but a module built outside
210 modules require CRC4 functions, but a module built outside
[all …]
|
| /Linux-v5.4/Documentation/admin-guide/mm/ |
| D | ksm.rst | 16 by sharing the data common between them. But it can be useful to any
28 KSM's merged pages were originally locked into kernel memory, but can now
29 be swapped out just like other user pages (but sharing is broken when they
50 with EAGAIN, but more probably arousing the Out-Of-Memory killer.
79 readable by all but writable only by root:
111 * set to 0 to stop ksmd from running but keep merged pages,
113 * set to 2 to stop ksmd and unmerge all pages currently merged, but
141 deduplication factor will be, but the slower the worst case
156 lower latency, but they will make ksmd use more CPU during the
167 how many pages unique but repeatedly checked for merging
[all …]
|
| /Linux-v5.4/Documentation/scheduler/ |
| D | sched-stats.rst | 18 domain. Domains have no particular names in this implementation, but
48 scheduler. We kept it for ABI compatibility, but it is always set to zero.
80 2) # of times in this domain load_balance() checked but found
90 7) # of times in this domain load_balance() was called but did
93 cpu was idle but no busier group was found
96 10) # of times in this domain load_balance() checked but found the
105 15) # of times in this domain load_balance() was called but did not
108 was busy but no busier group was found
112 18) # of times in this domain load_balance() checked but found the
121 23) # of times in this domain load_balance() was called but did not
[all …]
|
| /Linux-v5.4/tools/memory-model/litmus-tests/ |
| D | README | 45 As below, but with store-release replaced with WRITE_ONCE()
63 As above, but with store-release replaced with WRITE_ONCE()
67 As below, but with rcu_assign_pointer() and an rcu_dereference().
80 As below, but with the second access of the writer process
84 As below, but without the smp_rmb() and smp_wmb().
87 As below, but with a release-acquire chain.
90 As below, but with the first access of the writer process
98 but with two processes instead of three.)
106 As above, but without the smp_mb() invocations.
114 As above, but without the smp_mb() invocations.
[all …]
|
| /Linux-v5.4/Documentation/vm/ |
| D | frontswap.rst | 34 from transcendent memory into kernel memory, but will NOT remove the page
90 but-much-faster-than-disk "pseudo-RAM device" and the frontswap (and
108 as in zcache, but then "remotified" to another system's RAM. This
123 virtual machines, but the pages can be compressed and deduplicated to
135 * Sure there may be performance advantages in some situations, but
140 swap device. If CONFIG_FRONTSWAP is enabled but no frontswap "backend"
156 the existing eight bits, but let's worry about that minor optimization
163 backend, such as zcache, must implement policies to carefully (but
187 page. But if the backend does accept a page, the data from the page
212 but this would require fairly drastic changes. Even if it were
[all …]
|
| D | cleancache.rst | 16 to keep around, but can't since there isn't enough memory. So when the
61 An "init_shared_fs", like init_fs, obtains a pool id but tells cleancache
80 coherency. For the former, if two puts are made to the same handle but
133 swap pages) are a great use for this kind of slower-than-RAM-but-much-
147 virtual machines, but the pages can be compressed and deduplicated to
167 compare-to-NULL if config'ed on but no backend claims the ops
169 backend claims the ops functions but a filesystem doesn't enable
175 But for some filesystems (such as btrfs), the VFS hooks are
225 has little value, but in newer multicore machines, especially
253 is not an architectural restriction, but no backends currently
[all …]
|
| /Linux-v5.4/Documentation/firmware-guide/acpi/ |
| D | osi.rst | 24 but where Linux was installed to replace the original OS (Windows or OSX).
27 but many were tested to run with just one specific version of Windows.
35 But Linux isn't actually compatible with Windows, and the Linux community
39 But it is likely that they will all eventually be added.
85 But _OS had fundamental problems. First, the BIOS needed to know the name
115 But two bad things happened. First, the Windows ecosystem used _OSI
116 not as designed, but as a direct replacement for _OS -- identifying
123 Linux had no choice but to also return TRUE to _OSI("Windows 2001")
135 using it in untested BIOS flows. But some OEM's used _OSI("Linux")
145 of over-stating that compatibility; but the alternative has often been
[all …]
|
| /Linux-v5.4/Documentation/filesystems/ |
| D | hpfs.txt | 45 attributes but do not create them. 'rw' - create extended attributes
56 'cat FOO', 'cat Foo', 'cat foo' or 'cat F*' but not 'cat f*'. Note, that you
62 well. If you create 'a. ...', the file 'a' will be created, but you can still
94 chgrp symlinks but I don't know what is it good for. chmoding symlink results
98 moved ... sometimes it works. But the link is partly stored in directory
110 partition. It marked file name codepage as 850 - good. But when I again booted
114 really what IBM developers wanted? But problems continued. When I created in
123 OK, I could implement complex codepage support to this driver but I think it
143 OS/2 can't access files if the path is longer than about 256 chars but this
163 but vfs doesn't. Something like 'mv file FILE' won't work.
[all …]
|
| D | path-lookup.rst | 29 will allow us to review "REF-walk" and "RCU-walk" separately. But we
51 component, but that isn't always accurate: a pathname can lack both
53 generally forbidden in POSIX, but some of those "xxx``at``" system calls
66 not), but it might not even exist: neither the empty pathname nor the
75 ways that would lead to correct results, but not always. In
155 as heavy-handed as in the old "big kernel lock" days, but certainly not
211 but it first tries a more lightweight approach. As seen in
232 from happening, but only to detect when it happens.
254 memory pressure. This uses ``d_lock``, but ``i_rwsem`` plays no role.
318 uses CPU-local memory, but checking if the count is zero is expensive as
[all …]
|
| /Linux-v5.4/tools/perf/pmu-events/arch/x86/silvermont/ |
| D | pipeline.json | 4 …s unit predicts the target address not only based on the EIP of the branch but also based on the e…
14 …s unit predicts the target address not only based on the EIP of the branch but also based on the e…
24 …s unit predicts the target address not only based on the EIP of the branch but also based on the e…
34 …s unit predicts the target address not only based on the EIP of the branch but also based on the e…
44 …s unit predicts the target address not only based on the EIP of the branch but also based on the e…
54 …s unit predicts the target address not only based on the EIP of the branch but also based on the e…
64 …s unit predicts the target address not only based on the EIP of the branch but also based on the e…
74 …s unit predicts the target address not only based on the EIP of the branch but also based on the e…
84 …s unit predicts the target address not only based on the EIP of the branch but also based on the e…
94 …diction occurs when the processor predicts that the branch would be taken, but it is not, or vice-…
[all …]
|
| /Linux-v5.4/Documentation/maintainer/ |
| D | pull-requests.rst | 13 Mauro Carvalho Chehab. Misrepresentation was unintentional but inevitable,
62 not just make sense to me, but make sense as a historical record
70 (or even bug-fixes, but ones that look scary), explain not just
71 what they do and why they do it, but explain the _timing_. What
82 trivial formatting (the whole indentation and quoting etc), but
85 it right now), but may not make sense in the context of a merge
88 particularly for non-native speakers (but also for native ones
89 ;^). But I may miss some, or even add some.
136 will do this for you with the ``git request-pull`` command, but it needs a
150 can be used here instead as well (but note that some people behind
|
| /Linux-v5.4/Documentation/ia64/ |
| D | serial.rst | 32 change, but we registered devices that might not really exist.
54 EFI knows what your console devices are, but it doesn't tell the
57 devices are, but not all firmware supplies it. Also, EFI supports
98 - You specified "console=ttyS0" but Linux changed the device
103 EFI and elilo use both, but Linux defaults to VGA. Remove
107 elilo use all selected devices, but Linux uses only one.
111 - You're connected to an HP MP port[2] but have a non-MP UART
128 Kernel and init script output works fine, but no "login:" prompt:
134 "login:" prompt, but can't login as root:
|
| /Linux-v5.4/Documentation/powerpc/ |
| D | pci_iov_resource_on_powernv.rst | 29 state bits (one for MMIO and one for DMA, they get set together but can be
34 captures things like the details of the error that caused the freeze etc., but
53 memory but accessed in HW by the chip) that provides a direct
91 reserved for MSIs but this is not a problem at this point; we just
106 but that would mean using a completely different address allocation
116 bits which are not conveyed by PowerBus but we don't use this.
146 mechanism to make the freeze state cascade to "companion" PEs but
149 SW. We lose a bit of effectiveness of EEH in that case, but that's
158 sense, but we haven't done it yet.
170 PCI devices, but the BARs in VF config space headers are unusual. For
[all …]
|
| /Linux-v5.4/Documentation/devicetree/bindings/gpio/ |
| D | gpio-xilinx.txt | 5 input/output/tristate. Both channels share the same global IRQ but
22 - xlnx,all-inputs-2 : as above but for the second channel
23 - xlnx,dout-default-2 : as above but the second channel
24 - xlnx,gpio2-width : as above but for the second channel
25 - xlnx,tri-default-2 : as above but for the second channel
|
| /Linux-v5.4/Documentation/sound/cards/ |
| D | hdspm.rst | 33 receiver, only 56 are transmitted/received over the MADI, but
42 over the MADI, but all 32 channels are available for the mixer,
51 over the MADI, but all 16 channels are available for the mixer,
77 result), but if MMAP is used by the application. Therefore it
116 control-panel, but buffer-sizes are controlled with ALSA from
130 !!!! This is a hardware-function but is in conflict with the
151 !!!! This is no pure hardware function but was implemented by
169 card should synchronise better in MADI Mode. But since the
282 Should be "Autosync Rate", but Name used is
369 channels have to be muted on after loading the driver, but was
[all …]
|
| /Linux-v5.4/Documentation/process/ |
| D | volatile-considered-harmful.rst | 40 compiler might think it knows what will be in shared_data, but the
46 necessary. But the compiler would also be prevented from optimizing access
54 by locks, but one also does not want the compiler "optimizing" register
55 accesses within a critical section. But, within the kernel, I/O memory
81 - Inline assembly code which changes memory, but which has no other
86 every time it is referenced, but it can be read without any special
87 locking. So jiffies can be volatile, but the addition of other
|
| /Linux-v5.4/tools/testing/selftests/bpf/verifier/ |
| D | var_off.c | 9 * &skb->pkt_type, but we don't know which
30 /* add it to fp. We now have either fp-4 or fp-8, but
53 /* Check the lower bound but don't check the upper one. */
80 /* add it to fp. We now have either fp-4 or fp-8, but
105 /* add it to fp. We now have either fp-516 or fp-512, but
130 /* Add it to fp. We now have either fp-12 or fp-16, but we don't know
155 /* Add it to fp. We now have either fp-12 or fp-16, but we don't know
182 * which, but either way it points to initialized stack.
211 * which, but either way it points to initialized stack.
236 * which, but either way it points to initialized stack.
|
| /Linux-v5.4/arch/arm/include/uapi/asm/ |
| D | ptrace.h | 69 #define V4_PSR_T_BIT 0x00000020 /* >= V4T, but not V7M */
78 #define PSR_F_BIT 0x00000040 /* >= V4, but not V7M */
79 #define PSR_I_BIT 0x00000080 /* >= V4, but not V7M */
80 #define PSR_A_BIT 0x00000100 /* >= V6, but not V7M */
81 #define PSR_E_BIT 0x00000200 /* >= V6, but not V7M */
82 #define PSR_J_BIT 0x01000000 /* >= V5J, but not V7M */
|
| /Linux-v5.4/fs/cramfs/ |
| D | README | 22 Filename. Not generally null-terminated, but it is
26 confused with breadth-first); i.e. like depth-first but listing all of
28 same order as `ls -AUR' (but without the /^\..*:$/ directory header
97 blocks in uncompressed data consisting entirely of NUL bytes), but by
132 <asm/page.h>. Personally I don't like this option, but it does
157 2. Writer chooses blocksize; kernel adapts but rejects blocksize >
181 cost is greater complexity. Probably not worth it, but I hope someone
187 block size, but that just means adding and parsing a -b option.
|
| /Linux-v5.4/Documentation/ |
| D | hwspinlock.txt | 94 waiting for it to be released, but give up when the timeout elapses.
110 waiting for it to be released, but give up when the timeout elapses.
126 waiting for it to be released, but give up when the timeout elapses.
143 waiting for it to be released, but give up when the timeout elapses.
160 waiting for it to be released, but give up when the timeout elapses.
175 Attempt to lock a previously-assigned hwspinlock, but immediately fail if
192 Attempt to lock a previously-assigned hwspinlock, but immediately fail if
208 Attempt to lock a previously-assigned hwspinlock, but immediately fail if
224 Attempt to lock a previously-assigned hwspinlock, but immediately fail if
239 Attempt to lock a previously-assigned hwspinlock, but immediately fail if
[all …]
|
| /Linux-v5.4/Documentation/devicetree/bindings/ |
| D | ABI.txt | 9 break on an older device tree, but that doesn't mean the binding is
15 new. These guidelines aren't new, but they desperately need to be
26 3) Bindings can be augmented, but the driver shouldn't break when given
27 the old binding. ie. add additional properties, but don't change the
|
