| /kernel/linux/linux-5.10/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
73 deprecated but not before all userspace firmware/topology/UCM files
82 This option is not user-selectable but automagically handled by
96 deprecated but not before all userspace firmware/topology/UCM files
106 This option is not user-selectable but automagically handled by
125 This option is not user-selectable but automagically handled by
[all …]
|
| /kernel/linux/linux-5.10/tools/perf/pmu-events/arch/x86/amdzen2/ |
| D | other.json | 28 …"BriefDescription": "Cycles where a dispatch group is valid but does not get dispatched due to a t…
34 …"BriefDescription": "Cycles where a dispatch group is valid but does not get dispatched due to a t…
40 …"BriefDescription": "Cycles where a dispatch group is valid but does not get dispatched due to a t…
46 …"BriefDescription": "Cycles where a dispatch group is valid but does not get dispatched due to a t…
52 …"BriefDescription": "Cycles where a dispatch group is valid but does not get dispatched due to a t…
58 …"BriefDescription": "Cycles where a dispatch group is valid but does not get dispatched due to a t…
64 …"BriefDescription": "Cycles where a dispatch group is valid but does not get dispatched due to a t…
70 …"BriefDescription": "Cycles where a dispatch group is valid but does not get dispatched due to a t…
76 …"BriefDescription": "Cycles where a dispatch group is valid but does not get dispatched due to a t…
82 …"BriefDescription": "Cycles where a dispatch group is valid but does not get dispatched due to a t…
[all …]
|
| /kernel/linux/linux-4.19/tools/memory-model/litmus-tests/ |
| D | README | 43 As below, but with store-release replaced with WRITE_ONCE()
61 As above, but with store-release replaced with WRITE_ONCE()
65 As below, but with rcu_assign_pointer() and an rcu_dereference().
78 As below, but with the second access of the writer process
82 As below, but without the smp_rmb() and smp_wmb().
85 As below, but with a release-acquire chain.
88 As below, but with the first access of the writer process
96 but with two processes instead of three.)
104 As above, but without the smp_mb() invocations.
112 As above, but without the smp_mb() invocations.
[all …]
|
| /kernel/linux/linux-5.10/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 …]
|
| /kernel/linux/linux-4.19/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
113 These are quicker than the non-coarse versions, but less accurate,
122 but can't easily use 'jiffies', e.g. for inode timestamps.
124 on most modern machines with a reliable cycle counter, but
[all …]
|
| /kernel/linux/linux-5.10/tools/perf/pmu-events/arch/x86/amdzen1/ |
| D | other.json | 17 …"BriefDescription": "Cycles where a dispatch group is valid but does not get dispatched due to a t…
23 …"BriefDescription": "Cycles where a dispatch group is valid but does not get dispatched due to a t…
29 …"BriefDescription": "Cycles where a dispatch group is valid but does not get dispatched due to a t…
35 …"BriefDescription": "Cycles where a dispatch group is valid but does not get dispatched due to a t…
41 …"BriefDescription": "Cycles where a dispatch group is valid but does not get dispatched due to a t…
47 …"BriefDescription": "Cycles where a dispatch group is valid but does not get dispatched due to a t…
53 …"BriefDescription": "Cycles where a dispatch group is valid but does not get dispatched due to a t…
|
| /kernel/linux/linux-4.19/lib/ |
| D | Kconfig | 78 modules require CRC-CCITT functions, but a module built outside
86 modules require CRC16 functions, but a module built outside
103 modules require CRC ITU-T V.41 functions, but a module built outside
113 modules require CRC32/CRC32c functions, but a module built outside
139 This is the fastest algorithm, but comes with a 8KiB lookup table.
150 This is a bit slower than slice by 8, but has a smaller 4KiB lookup
159 is not particularly fast, but has a small 256 byte lookup table.
166 Calculate checksum one bit at a time. This is VERY slow, but has
177 modules require CRC64 functions, but a module built outside
185 modules require CRC4 functions, but a module built outside
[all …]
|
| /kernel/linux/linux-4.19/Documentation/ioctl/ |
| D | botching-up-ioctls.txt | 12 Which is nice, since there's no more insanity in the form of fake-generic, but
13 actually only used once interfaces. But the clear downside is that there's much
33 platforms don't necessarily align 64-bit values to 64-bit boundaries, but
67 but isn't a complete solution since newer userspace on older kernels won't
76 but garbage. This is also the reason why you must explicitly pad all
135 v4l use by default nowadays. But let userspace know which timestamps are
138 will mismatch if you look close enough, but if performance measuring tools
144 convenient time specification, but it's mostly the standard.
155 always be extended - but users will surely hate you if their neat animations
170 A full-blown drm driver essentially implements a little OS, but specialized to
[all …]
|
| /kernel/linux/linux-5.10/Documentation/bpf/ |
| D | ringbuf.rst | 22 These two problems are independent, but perf buffer fails to satisfy both.
26 counting, but given the first one requires an MPSC buffer, the same solution
33 type ``BPF_MAP_TYPE_RINGBUF``. Two other alternatives considered, but
37 ``BPF_MAP_TYPE_RINGBUF`` could represent an array of ring buffers, but not
39 with existing perf buffer use in BPF, but would fail if application needed more
51 themselves with, new syntax in libbpf, etc. But then would really provide no
53 doesn't support lookup/update/delete operations, but so doesn't few other map
66 with hashed task's tgid being a look up key to preserve order, but reduce
81 - but still the ability to do busy polling for new data to achieve the
93 discarded. Discard is similar to commit, but makes consumer ignore the
[all …]
|
| /kernel/linux/linux-5.10/Documentation/process/ |
| 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 …]
|
| /kernel/linux/linux-4.19/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 …]
|
| /kernel/linux/linux-5.10/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 …]
|
| /kernel/linux/linux-4.19/Documentation/scheduler/ |
| D | sched-stats.txt | 14 domain. Domains have no particular names in this implementation, but
42 scheduler. We kept it for ABI compatibility, but it is always set to zero.
72 2) # of times in this domain load_balance() checked but found
82 7) # of times in this domain load_balance() was called but did
85 cpu was idle but no busier group was found
89 10) # of times in this domain load_balance() checked but found the
98 15) # of times in this domain load_balance() was called but did not
101 was busy but no busier group was found
105 18) # of times in this domain load_balance() checked but found the
114 23) # of times in this domain load_balance() was called but did not
[all …]
|
| /kernel/linux/linux-5.10/tools/testing/selftests/drivers/net/mlxsw/ |
| D | sharedbuffer.sh | 113 check_err $? "Expected iPool($SB_POOL_ING) max occupancy to be $exp_max_occ, but got $max_occ"
118 check_err $? "Expected iPool($SB_POOL_ING) max occupancy to be $exp_max_occ, but got $max_occ"
123 check_err $? "Expected ePool($SB_POOL_EGR_CPU) max occupancy to be $exp_max_occ, but got $max_occ"
141 check_err $? "Expected ingress TC($SB_ITC) max occupancy to be $exp_max_occ, but got $max_occ"
146 check_err $? "Expected ingress TC($SB_ITC) max occupancy to be $exp_max_occ, but got $max_occ"
151 …check_err $? "Expected egress TC($SB_ITC_CPU_IP) max occupancy to be $exp_max_occ, but got $max_oc…
172 check_err $? "Expected ingress TC($SB_ITC) max occupancy to be $exp_max_occ, but got $max_occ"
177 check_err $? "Expected ingress TC($SB_ITC) max occupancy to be $exp_max_occ, but got $max_occ"
182 check_err $? "Expected egress TC($SB_ITC_IP2ME) max occupancy to be $exp_max_occ, but got $max_occ"
|
| /kernel/linux/linux-5.10/lib/ |
| D | Kconfig | 109 modules require CRC-CCITT functions, but a module built outside
117 modules require CRC16 functions, but a module built outside
134 modules require CRC ITU-T V.41 functions, but a module built outside
144 modules require CRC32/CRC32c functions, but a module built outside
170 This is the fastest algorithm, but comes with a 8KiB lookup table.
181 This is a bit slower than slice by 8, but has a smaller 4KiB lookup
190 is not particularly fast, but has a small 256 byte lookup table.
197 Calculate checksum one bit at a time. This is VERY slow, but has
208 modules require CRC64 functions, but a module built outside
216 modules require CRC4 functions, but a module built outside
[all …]
|
| /kernel/linux/linux-5.10/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 …]
|
| /kernel/linux/linux-5.10/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 …]
|
| /kernel/linux/linux-4.19/Documentation/ia64/ |
| D | serial.txt | 27 change, but we registered devices that might not really exist.
45 EFI knows what your console devices are, but it doesn't tell the
48 devices are, but not all firmware supplies it. Also, EFI supports
87 - You specified "console=ttyS0" but Linux changed the device
92 EFI and elilo use both, but Linux defaults to VGA. Remove
96 elilo use all selected devices, but Linux uses only one.
100 - You're connected to an HP MP port[2] but have a non-MP UART
117 Kernel and init script output works fine, but no "login:" prompt:
123 "login:" prompt, but can't login as root:
|
| /kernel/linux/linux-4.19/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 …]
|
| /kernel/linux/linux-5.10/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 …]
|
| /kernel/linux/linux-4.19/Documentation/acpi/ |
| D | osi.txt | 21 but where Linux was installed to replace the original OS (Windows or OSX).
24 but many were tested to run with just one specific version of Windows.
32 But Linux isn't actually compatible with Windows, and the Linux community
36 But it is likely that they will all eventually be added.
82 But _OS had fundamental problems. First, the BIOS needed to know the name
112 But two bad things happened. First, the Windows ecosystem used _OSI
113 not as designed, but as a direct replacement for _OS -- identifying
120 Linux had no choice but to also return TRUE to _OSI("Windows 2001")
132 using it in untested BIOS flows. But some OEM's used _OSI("Linux")
142 of over-stating that compatibility; but the alternative has often been
[all …]
|
| /kernel/linux/linux-5.10/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 …]
|
| /kernel/linux/linux-5.10/lib/kunit/ |
| D | assert.c | 57 KUNIT_SUBTEST_INDENT "Expected %s to be true, but is false\n", in kunit_unary_assert_format()
61 KUNIT_SUBTEST_INDENT "Expected %s to be false, but is true\n", in kunit_unary_assert_format()
76 KUNIT_SUBTEST_INDENT "Expected %s is not null, but is\n", in kunit_ptr_not_err_assert_format()
80 KUNIT_SUBTEST_INDENT "Expected %s is not error, but is: %ld\n", in kunit_ptr_not_err_assert_format()
96 KUNIT_SUBTEST_INDENT "Expected %s %s %s, but\n", in kunit_binary_assert_format()
118 KUNIT_SUBTEST_INDENT "Expected %s %s %s, but\n", in kunit_binary_ptr_assert_format()
140 KUNIT_SUBTEST_INDENT "Expected %s %s %s, but\n", in kunit_binary_str_assert_format()
|
| /kernel/linux/linux-4.19/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 …]
|
| /kernel/linux/linux-4.19/Documentation/powerpc/ |
| D | pci_iov_resource_on_powernv.txt | 21 state bits (one for MMIO and one for DMA, they get set together but can be
26 captures things like the details of the error that caused the freeze etc., but
44 memory but accessed in HW by the chip) that provides a direct
82 reserved for MSIs but this is not a problem at this point; we just
97 but that would mean using a completely different address allocation
107 bits which are not conveyed by PowerBus but we don't use this.
137 mechanism to make the freeze state cascade to "companion" PEs but
140 SW. We lose a bit of effectiveness of EEH in that case, but that's
149 sense, but we haven't done it yet.
160 PCI devices, but the BARs in VF config space headers are unusual. For
[all …]
|