but (full) in projects: linux - OpenGrok search results

Project(s)

Full Search
Definition
Symbol
File Path
History
Type

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

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

/linux/tools/perf/pmu-events/arch/x86/amdzen3/
H A 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/tools/perf/pmu-events/arch/x86/amdzen2/
H A 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/Documentation/core-api/
H A 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/Documentation/devicetree/bindings/regulator/
H A D	regulator.yaml	45 at boot but shouldn't prevent it from being turned off later. 129 protection and value '1' indicates that protection should be enabled but 136 that detection should be enabled but limit setting can be omitted. 140 is assumed still to be functional but approaching limit where it gets 143 be enabled but limit setting can be omitted. 148 protection and value '1' indicates that protection should be enabled but 156 that detection should be enabled but limit setting can be omitted. Limit 161 is assumed still to be functional but approaching limit where it gets 164 be enabled but limit setting can be omitted. Limit is given as microvolt 170 protection and value '1' indicates that protection should be enabled but [all …]
/linux/tools/perf/pmu-events/arch/x86/amdzen1/
H A 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/Documentation/bpf/
H A 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/Documentation/process/
H A 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/tools/perf/pmu-events/arch/x86/ivytown/
H A D	uncore-io.json	47 … attempted to acquire either a NCB or NCS credit to transmit into the IIO, but was rejected becaus… 87 …This includes when packets are passing by and when packets are being sunk, but does not include wh… 97 …This includes when packets are passing by and when packets are being sunk, but does not include wh… 107 …This includes when packets are passing by and when packets are being sunk, but does not include wh… 117 …This includes when packets are passing by and when packets are being sunk, but does not include wh… 127 …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… 147 …This includes when packets are passing by and when packets are being sunk, but does not include wh… 157 …This includes when packets are passing by and when packets are being sunk, but does not include wh… 167 …This includes when packets are passing by and when packets are being sunk, but does not include wh… [all …]
H A D	uncore-cache.json	224 …This includes when packets are passing by and when packets are being sunk, but does not include wh… 234 …This includes when packets are passing by and when packets are being sunk, but does not include wh… 244 …This includes when packets are passing by and when packets are being sunk, but does not include wh… 254 …This includes when packets are passing by and when packets are being sunk, but does not include wh… 264 …This includes when packets are passing by and when packets are being sunk, but does not include wh… 274 …This includes when packets are passing by and when packets are being sunk, but does not include wh… 284 …This includes when packets are passing by and when packets are being sunk, but does not include wh… 294 …This includes when packets are passing by and when packets are being sunk, but does not include wh… 304 …This includes when packets are passing by and when packets are being sunk, but does not include wh… 314 …This includes when packets are passing by and when packets are being sunk, but does not include wh… [all …]
/linux/tools/testing/selftests/net/forwarding/
H A 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/tools/perf/pmu-events/arch/x86/silvermont/
H A D	pipeline.json	8 …s unit predicts the target address not only based on the EIP of the branch but also based on the e… 17 …s unit predicts the target address not only based on the EIP of the branch but also based on the e… 27 …s unit predicts the target address not only based on the EIP of the branch but also based on the e… 37 …s unit predicts the target address not only based on the EIP of the branch but also based on the e… 47 …s unit predicts the target address not only based on the EIP of the branch but also based on the e… 57 …s unit predicts the target address not only based on the EIP of the branch but also based on the e… 67 …s unit predicts the target address not only based on the EIP of the branch but also based on the e… 77 …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… 97 …s unit predicts the target address not only based on the EIP of the branch but also based on the e… [all …]
/linux/Documentation/scheduler/
H A D	sched-stats.rst	23 domain. Domains have no particular names in this implementation, but 53 scheduler. We kept it for ABI compatibility, but it is always set to zero. 85 2) # of times in this domain sched_balance_rq() checked but found 95 7) # of times in this domain sched_balance_rq() was called but did 98 cpu was idle but no busier group was found 101 10) # of times in this domain sched_balance_rq() checked but found the 110 15) # of times in this domain sched_balance_rq() was called but did not 113 was busy but no busier group was found 117 18) # of times in this domain sched_balance_rq() checked but found the 126 23) # of times in this domain sched_balance_rq() was called but did not [all …]
/linux/Documentation/filesystems/bcachefs/
H A D	CodingStyle.rst	12 good. But appreciate beauty when you see it - and let people know. 33 expensive - but don't turn everything into a debug mode assertion, so that 47 means that you can run them in only a few places in the checked in version, but 53 the compiler could check. This is something that exists today, but it'll likely 54 still be a few decades before it comes to systems programming languages. But we 91 tool, but always look for more immediate ways to make things visible. When we 130 become product-manager focused. Often time an idea is a good one but needs to 131 wait for its proper time - but you won't know if it's the proper time for an 140 But don't be afraid to tackle projects that require significant rework of 178 Put effort into your documentation, commit messages, and code comments - but [all …]
/linux/tools/memory-model/litmus-tests/
H A 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/lib/
H A D	Kconfig	145 modules require CRC-CCITT functions, but a module built outside 153 modules require CRC16 functions, but a module built outside 179 modules require CRC ITU-T V.41 functions, but a module built outside 189 modules require CRC32/CRC32c functions, but a module built outside 215 This is the fastest algorithm, but comes with a 8KiB lookup table. 226 This is a bit slower than slice by 8, but has a smaller 4KiB lookup 235 is not particularly fast, but has a small 256 byte lookup table. 242 Calculate checksum one bit at a time. This is VERY slow, but has 253 modules require CRC64 functions, but a module built outside 261 modules require CRC4 functions, but a module built outside [all …]
/linux/Documentation/firmware-guide/acpi/
H A 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/tools/perf/pmu-events/arch/x86/broadwellx/
H A D	uncore-io.json	113 …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… 133 …This includes when packets are passing by and when packets are being sunk, but does not include wh… 143 …This includes when packets are passing by and when packets are being sunk, but does not include wh… 153 …This includes when packets are passing by and when packets are being sunk, but does not include wh… 163 …This includes when packets are passing by and when packets are being sunk, but does not include wh… 173 …This includes when packets are passing by and when packets are being sunk, but does not include wh… 203 …This includes when packets are passing by and when packets are being sunk, but does not include wh… 213 …This includes when packets are passing by and when packets are being sunk, but does not include wh… 223 …This includes when packets are passing by and when packets are being sunk, but does not include wh… [all …]
/linux/tools/perf/pmu-events/arch/x86/broadwellde/
H A D	uncore-io.json	113 …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… 133 …This includes when packets are passing by and when packets are being sunk, but does not include wh… 143 …This includes when packets are passing by and when packets are being sunk, but does not include wh… 153 …This includes when packets are passing by and when packets are being sunk, but does not include wh… 163 …This includes when packets are passing by and when packets are being sunk, but does not include wh… 173 …This includes when packets are passing by and when packets are being sunk, but does not include wh… 203 …This includes when packets are passing by and when packets are being sunk, but does not include wh… 213 …This includes when packets are passing by and when packets are being sunk, but does not include wh… 223 …This includes when packets are passing by and when packets are being sunk, but does not include wh… [all …]
/linux/Documentation/admin-guide/mm/
H A 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: 112 * set to 0 to stop ksmd from running but keep merged pages, 114 * set to 2 to stop ksmd and unmerge all pages currently merged, but 142 deduplication factor will be, but the slower the worst case 157 lower latency, but they will make ksmd use more CPU during the 204 how many pages unique but repeatedly checked for merging [all …]
/linux/lib/kunit/
H A D	assert.c	60 KUNIT_SUBTEST_INDENT "Expected %s to be true, but is false\n", in kunit_unary_assert_format() 64 KUNIT_SUBTEST_INDENT "Expected %s to be false, but is true\n", in kunit_unary_assert_format() 81 KUNIT_SUBTEST_INDENT "Expected %s is not null, but is\n", in kunit_ptr_not_err_assert_format() 85 KUNIT_SUBTEST_INDENT "Expected %s is not error, but is: %ld\n", in kunit_ptr_not_err_assert_format() 126 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() 247 KUNIT_SUBTEST_INDENT "Expected %s is not null, but is\n", in kunit_mem_assert_format() 251 KUNIT_SUBTEST_INDENT "Expected %s is not null, but is\n", in kunit_mem_assert_format() 255 KUNIT_SUBTEST_INDENT "Expected %s %s %s, but\n", in kunit_mem_assert_format()
/linux/Documentation/arch/arm64/
H A D	cpu-hotplug.rst	18 Physical systems need to mark a CPU that is ``possible`` but not ``present`` as 24 In the arm64 world CPUs are not a single device but a slice of the system. 29 e.g. New CPUs come with new caches, but the platform's cache topology is 35 structures can describe a redistributor associated with a disabled CPU, but 50 CPU Hotplug as all resources are described as ``present``, but CPUs may be 64 ``enabled`` in the MADT GICC structures, but should have the ``online capable`` 69 CPUs described as ``online capable`` but not ``enabled`` can be set to enabled
/linux/Documentation/driver-api/
H A 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/Documentation/arch/powerpc/
H A 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/tools/testing/selftests/bpf/progs/
H A D	verifier_var_off.c	26 * &skb->pkt_type, but we don't know which \ in variable_offset_ctx_access() 51 /* add it to fp. We now have either fp-4 or fp-8, but\ in stack_read_priv_vs_unpriv() 74 /* add it to fp. We now have either fp-4 or fp-8, but\ in variable_offset_stack_read_uninitialized() 106 * fp-16, but we don't know which \ in stack_write_priv_vs_unpriv() 116 /* Similar to the previous test, but this time also perform a read from the 143 /* Add it to fp. We now have either fp-8 or fp-16, but\ in stack_write_followed_by_read() 185 /* Add it to fp. We now have either fp-8 or fp-16, but\ in stack_write_clobbers_spilled_regs() 219 /* Check the lower bound but don't check the upper one. /\ in variable_offset_stack_access_unbounded() 251 / add it to fp. We now have either fp-4 or fp-8, but\ in access_max_out_of_bound() 266 /* Similar to the test above, but this time check the special case of a [all …]
/linux/Documentation/sound/cards/
H A 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 …]

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