but (full) in projects: Linux-v5.15 - OpenGrok search results

Project(s)

Full Search
Definition
Symbol
File Path
History
Type

Searched full:but (Results 1 – 25 of 11143) sorted by relevance

12 3 4 5 6 7 8 9 10 >>...446

/Linux-v5.15/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-v5.15/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-v5.15/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.15/Documentation/devicetree/bindings/regulator/
D	regulator.yaml	44 at boot but shouldn't prevent it from being turned off later. 123 protection and value '1' indicates that protection should be enabled but 130 that detection should be enabled but limit setting can be omitted. 134 is assumed still to be functional but approaching limit where it gets 137 be enabled but limit setting can be omitted. 142 protection and value '1' indicates that protection should be enabled but 150 that detection should be enabled but limit setting can be omitted. Limit 155 is assumed still to be functional but approaching limit where it gets 158 be enabled but limit setting can be omitted. Limit is given as microvolt 164 protection and value '1' indicates that protection should be enabled but [all …]
/Linux-v5.15/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-v5.15/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 …]
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.15/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-v5.15/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.15/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"
/Linux-v5.15/lib/
D	Kconfig	129 modules require CRC-CCITT functions, but a module built outside 137 modules require CRC16 functions, but a module built outside 154 modules require CRC ITU-T V.41 functions, but a module built outside 164 modules require CRC32/CRC32c functions, but a module built outside 190 This is the fastest algorithm, but comes with a 8KiB lookup table. 201 This is a bit slower than slice by 8, but has a smaller 4KiB lookup 210 is not particularly fast, but has a small 256 byte lookup table. 217 Calculate checksum one bit at a time. This is VERY slow, but has 228 modules require CRC64 functions, but a module built outside 236 modules require CRC4 functions, but a module built outside [all …]
/Linux-v5.15/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.15/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.15/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 …]
/Linux-v5.15/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.15/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.15/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.15/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.15/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 …]
/Linux-v5.15/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.15/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 52 /* add it to fp. We now have either fp-4 or fp-8, but 73 /* Add it to fp. We now have either fp-8 or fp-16, but 109 /* Add it to fp. We now have either fp-8 or fp-16, but 148 /* Check the lower bound but don't check the upper one. / 175 / add it to fp. We now have either fp-4 or fp-8, but 200 /* add it to fp. We now have either fp-516 or fp-512, but 225 /* Add it to fp. We now have either fp-12 or fp-16, but we don't know 250 /* Add it to fp. We now have either fp-12 or fp-16, but we don't know [all …]
/Linux-v5.15/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.15/Documentation/devicetree/bindings/gpio/
D	gpio-xilinx.txt	`5 input/output/tristate. Both channels share the same global IRQ but 23 - xlnx,all-inputs-2 : as above but for the second channel 24 - xlnx,dout-default-2 : as above but the second channel 25 - xlnx,gpio2-width : as above but for the second channel 26 - xlnx,tri-default-2 : as above but for the second channel`
/Linux-v5.15/Documentation/admin-guide/
D	reporting-issues.rst	38 The issue was fixed there, but you would like to see it resolved in a still 129 approach, but in that development phase it can be an even better idea to 216 above, but failed to reproduce your issue there; at the same time you want to 247 should be enough for most people. But sometimes there are situations where even 251 from top to bottom. But it's mainly meant to skim over and a place to look up 257 demands more than other FLOSS projects. We'd love to make it simpler. But 325 regular Fedora releases, and openSUSE Tumbleweed. But keep in mind, you better 331 or heavily modified vendor kernel to the upstream Linux developers. But note, 332 those often get rejected or ignored, so consider yourself warned. But it's still 364 But its exact brand name (say 'ASUS Red Devil Radeon RX 5700 XT Gaming OC') [all …]
/Linux-v5.15/Documentation/filesystems/
D	hpfs.rst	53 attributes but do not create them. 'rw' - create extended attributes 65 'cat FOO', 'cat Foo', 'cat foo' or 'cat F' but not 'cat f'. Note, that you 71 well. If you create 'a. ...', the file 'a' will be created, but you can still 105 chgrp symlinks but I don't know what is it good for. chmoding symlink results 109 moved ... sometimes it works. But the link is partly stored in directory 122 partition. It marked file name codepage as 850 - good. But when I again booted 126 really what IBM developers wanted? But problems continued. When I created in 135 OK, I could implement complex codepage support to this driver but I think it 156 OS/2 can't access files if the path is longer than about 256 chars but this 177 but vfs doesn't. Something like 'mv file FILE' won't work. [all …]

12 3 4 5 6 7 8 9 10 >>...446