/Linux-v6.6/tools/perf/pmu-events/arch/x86/amdzen3/ |
D | other.json | 22 …ch group is valid but does not get dispatched due to a Token Stall. Also counts cycles when the th… 28 …ch group is valid but does not get dispatched due to a Token Stall. Also counts cycles when the th… 34 …ch group is valid but does not get dispatched due to a Token Stall. Also counts cycles when the th… 40 …ch group is valid but does not get dispatched due to a Token Stall. Also counts cycles when the th… 46 …"BriefDescription": "Cycles where a dispatch group is valid but does not get dispatched due to a t… 52 …ch group is valid but does not get dispatched due to a Token Stall. Also counts cycles when the th… 58 …ch group is valid but does not get dispatched due to a Token Stall. Also counts cycles when the th… 64 …ch group is valid but does not get dispatched due to a Token Stall. Also counts cycles when the th… 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… [all …]
|
/Linux-v6.6/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 …]
|
/Linux-v6.6/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-v6.6/Documentation/devicetree/bindings/regulator/ |
D | regulator.yaml | 45 at boot but shouldn't prevent it from being turned off later. 124 protection and value '1' indicates that protection should be enabled but 131 that detection should be enabled but limit setting can be omitted. 135 is assumed still to be functional but approaching limit where it gets 138 be enabled but limit setting can be omitted. 143 protection and value '1' indicates that protection should be enabled but 151 that detection should be enabled but limit setting can be omitted. Limit 156 is assumed still to be functional but approaching limit where it gets 159 be enabled but limit setting can be omitted. Limit is given as microvolt 165 protection and value '1' indicates that protection should be enabled but [all …]
|
/Linux-v6.6/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…
|
/Linux-v6.6/tools/perf/pmu-events/arch/x86/ivytown/ |
D | uncore-io.json | 42 … attempted to acquire either a NCB or NCS credit to transmit into the IIO, but was rejected becaus… 78 …This includes when packets are passing by and when packets are being sunk, but does not include wh… 87 …This includes when packets are passing by and when packets are being sunk, but does not include wh… 96 …This includes when packets are passing by and when packets are being sunk, but does not include wh… 105 …This includes when packets are passing by and when packets are being sunk, but does not include wh… 114 …This includes when packets are passing by and when packets are being sunk, but does not include wh… 123 …This includes when packets are passing by and when packets are being sunk, but does not include wh… 132 …This includes when packets are passing by and when packets are being sunk, but does not include wh… 141 …This includes when packets are passing by and when packets are being sunk, but does not include wh… 150 …This includes when packets are passing by and when packets are being sunk, but does not include wh… [all …]
|
/Linux-v6.6/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 …]
|
/Linux-v6.6/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 …]
|
/Linux-v6.6/Documentation/admin-guide/mm/ |
D | ksm.rst | 14 by sharing the data common between them. But it can be useful to any 26 KSM's merged pages were originally locked into kernel memory, but can now 27 be swapped out just like other user pages (but sharing is broken when they 48 with EAGAIN, but more probably arousing the Out-Of-Memory killer. 77 readable by all but writable only by root: 109 * set to 0 to stop ksmd from running but keep merged pages, 111 * set to 2 to stop ksmd and unmerge all pages currently merged, but 139 deduplication factor will be, but the slower the worst case 154 lower latency, but they will make ksmd use more CPU during the 169 how many pages unique but repeatedly checked for merging [all …]
|
/Linux-v6.6/tools/testing/selftests/net/forwarding/ |
D | bridge_mdb_max.sh | 416 check_err $? "Number of groups was $n0, now is $n1, but $((n0 + 5)) expected" 423 check_err $? "Number of groups was $n0, now is $n2, but should be back to $n0" 505 …check_err $? "Number of groups at VLAN 10 was $n10, now is $n11, but 5 entries added on VLAN 10, $… 508 check_err $? "Number of groups at VLAN 20 was $n20, now is $n21, but no change expected on VLAN 20" 516 check_err $? "Number of groups at VLAN 10 was $n11, now is $n12, but no change expected on VLAN 10" 519 …check_err $? "Number of groups at VLAN 20 was $n21, now is $n22, but 5 entries added on VLAN 20, $… 529 check_err $? "Number of groups at VLAN 10 was $n10, now is $n13, but should be back to $n10" 532 check_err $? "Number of groups at VLAN 20 was $n20, now is $n23, but should be back to $n20" 568 check_err $? "Max groups on $locus should be 0, but $max reported" 574 check_err $? "Max groups expected to be 100, but $max reported" [all …]
|
/Linux-v6.6/lib/ |
D | Kconfig | 136 modules require CRC-CCITT functions, but a module built outside 144 modules require CRC16 functions, but a module built outside 170 modules require CRC ITU-T V.41 functions, but a module built outside 180 modules require CRC32/CRC32c functions, but a module built outside 206 This is the fastest algorithm, but comes with a 8KiB lookup table. 217 This is a bit slower than slice by 8, but has a smaller 4KiB lookup 226 is not particularly fast, but has a small 256 byte lookup table. 233 Calculate checksum one bit at a time. This is VERY slow, but has 244 modules require CRC64 functions, but a module built outside 252 modules require CRC4 functions, but a module built outside [all …]
|
/Linux-v6.6/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… 168 check_err $? "Expected ingress TC($SB_ITC) max occupancy to be $exp_max_occ, but got $max_occ" 173 check_err $? "Expected ingress TC($SB_ITC) max occupancy to be $exp_max_occ, but got $max_occ" 178 check_err $? "Expected egress TC($SB_ITC_IP2ME) max occupancy to be $exp_max_occ, but got $max_occ"
|
/Linux-v6.6/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-v6.6/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() 71 As below, but with rcu_assign_pointer() and an rcu_dereference(). 84 As below, but with the second access of the writer process 88 As below, but without the smp_rmb() and smp_wmb(). 91 As below, but with a release-acquire chain. 94 As below, but with the first access of the writer process 106 but with two processes instead of three.) 114 As above, but without the smp_mb() invocations. 122 As above, but without the smp_mb() invocations. [all …]
|
/Linux-v6.6/tools/perf/pmu-events/arch/x86/silvermont/ |
D | pipeline.json | 7 …s unit predicts the target address not only based on the EIP of the branch but also based on the e… 15 …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… 33 …s unit predicts the target address not only based on the EIP of the branch but also based on the e… 42 …s unit predicts the target address not only based on the EIP of the branch but also based on the e… 51 …s unit predicts the target address not only based on the EIP of the branch but also based on the e… 60 …s unit predicts the target address not only based on the EIP of the branch but also based on the e… 69 …s unit predicts the target address not only based on the EIP of the branch but also based on the e… 78 …s unit predicts the target address not only based on the EIP of the branch but also based on the e… 87 …s unit predicts the target address not only based on the EIP of the branch but also based on the e… [all …]
|
/Linux-v6.6/tools/perf/pmu-events/arch/x86/broadwellx/ |
D | uncore-io.json | 101 …This includes when packets are passing by and when packets are being sunk, but does not include wh… 110 …This includes when packets are passing by and when packets are being sunk, but does not include wh… 119 …This includes when packets are passing by and when packets are being sunk, but does not include wh… 128 …This includes when packets are passing by and when packets are being sunk, but does not include wh… 137 …This includes when packets are passing by and when packets are being sunk, but does not include wh… 146 …This includes when packets are passing by and when packets are being sunk, but does not include wh… 155 …This includes when packets are passing by and when packets are being sunk, but does not include wh… 182 …This includes when packets are passing by and when packets are being sunk, but does not include wh… 191 …This includes when packets are passing by and when packets are being sunk, but does not include wh… 200 …This includes when packets are passing by and when packets are being sunk, but does not include wh… [all …]
|
/Linux-v6.6/tools/perf/pmu-events/arch/x86/broadwellde/ |
D | uncore-io.json | 101 …This includes when packets are passing by and when packets are being sunk, but does not include wh… 110 …This includes when packets are passing by and when packets are being sunk, but does not include wh… 119 …This includes when packets are passing by and when packets are being sunk, but does not include wh… 128 …This includes when packets are passing by and when packets are being sunk, but does not include wh… 137 …This includes when packets are passing by and when packets are being sunk, but does not include wh… 146 …This includes when packets are passing by and when packets are being sunk, but does not include wh… 155 …This includes when packets are passing by and when packets are being sunk, but does not include wh… 182 …This includes when packets are passing by and when packets are being sunk, but does not include wh… 191 …This includes when packets are passing by and when packets are being sunk, but does not include wh… 200 …This includes when packets are passing by and when packets are being sunk, but does not include wh… [all …]
|
/Linux-v6.6/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. 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 …]
|
/Linux-v6.6/tools/perf/pmu-events/arch/x86/icelake/ |
D | uncore-interconnect.json | 11 … that were issued by any core. This event is not supported on ICL products but is supported on RKL… 19 … that were issued by any core. This event is not supported on ICL products but is supported on RKL… 27 …n. Doesn't include prefetches. This event is not supported on ICL products but is supported on RKL… 43 …rent and non-coherent traffic. This event is not supported on ICL products but is supported on RKL… 51 …n. Doesn't include prefetches. This event is not supported on ICL products but is supported on RKL… 67 …s. Doesn't include prefetches. This event is not supported on ICL products but is supported on RKL…
|
/Linux-v6.6/tools/perf/pmu-events/arch/x86/rocketlake/ |
D | uncore-interconnect.json | 11 … that were issued by any core. This event is not supported on ICL products but is supported on RKL… 19 … that were issued by any core. This event is not supported on ICL products but is supported on RKL… 27 …n. Doesn't include prefetches. This event is not supported on ICL products but is supported on RKL… 43 …rent and non-coherent traffic. This event is not supported on ICL products but is supported on RKL… 51 …n. Doesn't include prefetches. This event is not supported on ICL products but is supported on RKL… 67 …s. Doesn't include prefetches. This event is not supported on ICL products but is supported on RKL…
|
/Linux-v6.6/lib/kunit/ |
D | assert.c | 58 KUNIT_SUBTEST_INDENT "Expected %s to be true, but is false\n", in kunit_unary_assert_format() 62 KUNIT_SUBTEST_INDENT "Expected %s to be false, but is true\n", in kunit_unary_assert_format() 79 KUNIT_SUBTEST_INDENT "Expected %s is not null, but is\n", in kunit_ptr_not_err_assert_format() 83 KUNIT_SUBTEST_INDENT "Expected %s is not error, but is: %ld\n", in kunit_ptr_not_err_assert_format() 124 KUNIT_SUBTEST_INDENT "Expected %s %s %s, but\n", in kunit_binary_assert_format() 154 KUNIT_SUBTEST_INDENT "Expected %s %s %s, but\n", in kunit_binary_ptr_assert_format() 194 KUNIT_SUBTEST_INDENT "Expected %s %s %s, but\n", in kunit_binary_str_assert_format() 246 KUNIT_SUBTEST_INDENT "Expected %s is not null, but is\n", in kunit_mem_assert_format() 250 KUNIT_SUBTEST_INDENT "Expected %s is not null, but is\n", in kunit_mem_assert_format() 254 KUNIT_SUBTEST_INDENT "Expected %s %s %s, but\n", in kunit_mem_assert_format()
|
/Linux-v6.6/Documentation/maintainer/ |
D | pull-requests.rst | 11 Mauro Carvalho Chehab. Misrepresentation was unintentional but inevitable, 60 not just make sense to me, but make sense as a historical record 68 (or even bug-fixes, but ones that look scary), explain not just 69 what they do and why they do it, but explain the _timing_. What 80 trivial formatting (the whole indentation and quoting etc), but 83 it right now), but may not make sense in the context of a merge 86 particularly for non-native speakers (but also for native ones 87 ;^). But I may miss some, or even add some. 134 will do this for you with the ``git request-pull`` command, but it needs a 148 can be used here instead as well (but note that some people behind
|
/Linux-v6.6/Documentation/arch/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-v6.6/sound/soc/sof/intel/ |
D | Kconfig | 15 This option is not user-selectable but automagically handled by 23 This option is not user-selectable but automagically handled by 35 This option is not user-selectable but automagically handled by 52 drivers, currently the default but which will be deprecated 290 This option is not user-selectable but automagically handled by 296 This option is not user-selectable but automagically handled by 325 This option is not user-selectable but automagically handled by 333 This option is not user-selectable but automagically handled by 342 This option is not user-selectable but automagically handled by
|
/Linux-v6.6/Documentation/driver-api/ |
D | device-io.rst | 31 memory, but as accesses to a device. Some architectures define devices 32 to be at a fixed address, but most have some method of discovering 34 document does not cover how to receive such an address, but assumes you 154 points to a virtual memory address and can be offset or dereferenced, but in 184 each other, but contain a less expensive barrier operation. A device driver 196 identical behavior, but they can also operate on ``__iomem`` tokens returned 205 These behave in the same way as the ioread32()/iowrite32() family, but with 214 Drivers that use readl()/writel() this way are generally not portable, but 223 on 32-bit architectures but allow two consecutive 32-bit accesses instead. 237 a four-byte __raw_readl() does not get split into individual byte loads, but [all …]
|