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

Project(s)

Full Search
Definition
Symbol
File Path
History
Type

Searched full:that (Results 1 – 25 of 11798) sorted by relevance

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

/linux/include/media/
H A D	v4l2-ioctl.h	25 * @vidioc_querycap: pointer to the function that implements 27 * @vidioc_enum_fmt_vid_cap: pointer to the function that implements 30 * @vidioc_enum_fmt_vid_overlay: pointer to the function that implements 33 * @vidioc_enum_fmt_vid_out: pointer to the function that implements 36 * @vidioc_enum_fmt_sdr_cap: pointer to the function that implements 39 * @vidioc_enum_fmt_sdr_out: pointer to the function that implements 42 * @vidioc_enum_fmt_meta_cap: pointer to the function that implements 45 * @vidioc_enum_fmt_meta_out: pointer to the function that implements 48 * @vidioc_g_fmt_vid_cap: pointer to the function that implements 51 * @vidioc_g_fmt_vid_overlay: pointer to the function that implements [all …]
/linux/Documentation/filesystems/xfs/
H A D	xfs-delayed-logging-design.rst	10 This document describes the design and algorithms that the XFS journalling 11 subsystem is based on. This document describes the design and algorithms that 12 the XFS journalling subsystem is based on so that readers may familiarize 36 chained together by intents, ensuring that journal recovery can restart and 37 finish an operation that was only partially done when the system stopped 47 particularly important in the scope of this document. It suffices to know that 50 performed. The logging subsystem only cares that certain specific rules are 59 transactions. Permanent transaction reservations can take reservations that span 64 place. This means that permanent transactions can be used for one-shot 79 space that was taken at the transaction allocation time. [all …]
/linux/tools/perf/pmu-events/arch/x86/goldmont/
H A D	cache.json	7 …on which likely indicates back pressure from L2Q. It also counts requests that would have gone dir… 24 …"PublicDescription": "Counts cycles that fetch is stalled due to an outstanding ICache miss. That … 33 …"PublicDescription": "Counts the number of demand and prefetch transactions that the L2 XQ rejects… 41 …"PublicDescription": "Counts memory requests originating from the core that miss in the L2 cache.", 50 …"PublicDescription": "Counts memory requests originating from the core that reference a cache line… 55 "BriefDescription": "Loads retired that came from DRAM (Precise event capable)", 72 …that when the load address was checked by other caching agents (typically another processor) in th… 77 "BriefDescription": "Load uops retired that hit L1 data cache (Precise event capable)", 83 "PublicDescription": "Counts load uops retired that hit the L1 data cache.", 88 "BriefDescription": "Load uops retired that missed L1 data cache (Precise event capable)", [all …]
/linux/Documentation/process/
H A D	management-style.rst	14 to do with reality. It started as a lark, but that doesn't mean that it 27 making it painfully obvious to the questioner that we don't have a clue 37 Everybody thinks managers make decisions, and that decision-making is 39 manager must be to make it. That's very deep and obvious, but it's not 47 competent to make that decision for them. 51 Namely that you are in the wrong job, and that they should be managing 60 It helps to realize that the key difference between a big decision and a 62 can be made small by just always making sure that if you were wrong (and 67 And people will even see that as true leadership (cough bullshit 71 things that can't be undone. Don't get ushered into a corner from which [all …]
H A D	6.Followthrough.rst	8 patches. One of the biggest mistakes that even experienced kernel 9 developers can make is to conclude that their work is now done. In truth, 13 It is a rare patch which is so good at its first posting that there is no 16 code. You, as the author of that code, will be expected to work with the 17 kernel community to ensure that your code is up to the kernel's quality 32 value and why you went to the trouble of writing it. But that value 36 to substantial rewrites - come from the understanding that Linux will 49 be working on the kernel years from now, but they understand that their 57 the same. Sometimes this means that the clever hack in your driver 61 What all of this comes down to is that, when reviewers send you comments, [all …]
/linux/drivers/gpu/drm/xe/
H A D	xe_gt_sriov_pf_control_types.h	16 * @XE_GT_SRIOV_STATE_WIP: indicates that some operations are in progress. 17 * @XE_GT_SRIOV_STATE_FLR_WIP: indicates that a VF FLR is in progress. 18 * @XE_GT_SRIOV_STATE_FLR_SEND_START: indicates that the PF wants to send a FLR START command. 19 * @XE_GT_SRIOV_STATE_FLR_WAIT_GUC: indicates that the PF awaits for a response from the GuC. 20 * @XE_GT_SRIOV_STATE_FLR_GUC_DONE: indicates that the PF has received a response from the GuC. 21 * @XE_GT_SRIOV_STATE_FLR_RESET_CONFIG: indicates that the PF needs to clear VF's resources. 22 * @XE_GT_SRIOV_STATE_FLR_RESET_DATA: indicates that the PF needs to clear VF's data. 23 * @XE_GT_SRIOV_STATE_FLR_RESET_MMIO: indicates that the PF needs to reset VF's registers. 24 * @XE_GT_SRIOV_STATE_FLR_SEND_FINISH: indicates that the PF wants to send a FLR FINISH message. 25 * @XE_GT_SRIOV_STATE_FLR_FAILED: indicates that VF FLR sequence failed. [all …]
/linux/Documentation/filesystems/
H A D	path-lookup.rst	22 exploration is needed to discover, is that it is complex. There are 23 many rules, special cases, and implementation alternatives that all 26 tool that we will make extensive use of is "divide and conquer". For 41 of elements: "slashes" that are sequences of one or more "``/``" 42 characters, and "components" that are sequences of one or more 43 non-"``/``" characters. These form two kinds of paths. Those that 52 component, but that isn't always accurate: a pathname can lack both 62 it must identify a directory that already exists, otherwise an error 68 pathname that is just slashes have a final component. If it does 75 tempting to consider that to have an empty final component. In many [all …]
H A D	directory-locking.rst	12 that "inode pointer" order in the following. 37 * check that the source is not a directory 40 5. rename that is _not_ cross-directory. Locking rules: 47 * take the locks that need to be taken (exclusive), in inode pointer order 48 if need to take both (that can happen only when both source and target 51 allowed only with RENAME_EXCHANGE, and that won't be removing the target). 60 * verify that the source is not a descendent of the target and 65 The rules above obviously guarantee that all directories that are going 78 that's not a problem, but there is a nasty twist - what should we do 79 when one growing tree reaches the root of another? That can happen in [all …]
/linux/tools/perf/pmu-events/arch/arm64/fujitsu/a64fx/
H A D	other.json	9 …"PublicDescription": "This event counts every cycle that no operation was committed because the ol… 12 …"BriefDescription": "This event counts every cycle that no operation was committed because the old… 15 …"PublicDescription": "This event counts every cycle that no instruction was committed because the … 18 …"BriefDescription": "This event counts every cycle that no instruction was committed because the o… 21 …"PublicDescription": "This event counts every cycle that no instruction was committed because the … 24 …"BriefDescription": "This event counts every cycle that no instruction was committed because the o… 27 …"PublicDescription": "This event counts every cycle that no instruction was committed because the … 30 …"BriefDescription": "This event counts every cycle that no instruction was committed because the o… 33 …"PublicDescription": "This event counts every cycle that no instruction was committed because the … 36 …"BriefDescription": "This event counts every cycle that no instruction was committed because the o… [all …]
/linux/tools/perf/pmu-events/arch/x86/graniterapids/
H A D	uncore-cache.json	22 …"BriefDescription": "Counts transactions that looked into the multi-socket cacheline Directory sta… 32 …"BriefDescription": "Counts transactions that looked into the multi-socket cacheline Directory st… 158 …Note the non-standard filtering equation. This event will count requests that lookup the cache mu… 224 …Note the non-standard filtering equation. This event will count requests that lookup the cache mu… 246 …Note the non-standard filtering equation. This event will count requests that lookup the cache mu… 268 …Note the non-standard filtering equation. This event will count requests that lookup the cache mu… 279 …Note the non-standard filtering equation. This event will count requests that lookup the cache mu… 301 …Note the non-standard filtering equation. This event will count requests that lookup the cache mu… 334 …Note the non-standard filtering equation. This event will count requests that lookup the cache mu… 356 …Note the non-standard filtering equation. This event will count requests that lookup the cache mu… [all …]
/linux/tools/memory-model/Documentation/
H A D	glossary.txt	9 dependency" extends from that load extending to the later access. 20 address dependency extends from that rcu_dereference() to that 27 Acquire: With respect to a lock, acquiring that lock, for example, 29 a special operation that includes a load and which orders that 30 load before later memory references running on that same CPU. 36 to that same variable, (in other words, the acquire load "reads 37 from" the release store), then all operations preceding that 38 store "happen before" any operations following that load acquire. 56 a "control dependency" extends from that load to that store. 71 that is required. In other cases, the notion of pairing must be [all …]
/linux/tools/perf/pmu-events/arch/x86/grandridge/
H A D	uncore-cache.json	106 …Note the non-standard filtering equation. This event will count requests that lookup the cache mu… 172 …Note the non-standard filtering equation. This event will count requests that lookup the cache mu… 194 …Note the non-standard filtering equation. This event will count requests that lookup the cache mu… 216 …Note the non-standard filtering equation. This event will count requests that lookup the cache mu… 227 …Note the non-standard filtering equation. This event will count requests that lookup the cache mu… 249 …Note the non-standard filtering equation. This event will count requests that lookup the cache mu… 309 …escription": "Counts the number of lines that were victimized on a fill. This can be filtered by … 320 … IA traffic : Counts the number of lines that were victimized on a fill. This can be filtered by … 330 … IO traffic : Counts the number of lines that were victimized on a fill. This can be filtered by … 340 …escription": "Counts the number of lines that were victimized on a fill. This can be filtered by … [all …]
/linux/LICENSES/preferred/
H A D	LGPL-2.1	45 price. Our General Public Licenses are designed to make sure that you have 47 service if you wish); that you receive source code or can get it if you 48 want it; that you can change the software and use pieces of it in new free 49 programs; and that you are informed that you can do these things. 51 To protect your rights, we need to make restrictions that forbid 57 a fee, you must give the recipients all the rights that we gave you. You 58 must make sure that they, too, receive or can get the source code. If you 60 the recipients, so that they can relink them with the library after making 68 To protect each distributor, we want to make it very clear that there is no 70 else and passed on, the recipients should know that what they have is not [all …]
H A D	LGPL-2.0	39 General Public Licenses are designed to make sure that you have the freedom 41 wish), that you receive source code or can get it if you want it, that you 42 can change the software or use pieces of it in new free programs; and that 45 To protect your rights, we need to make restrictions that forbid anyone to 51 a fee, you must give the recipients all the rights that we gave you. You 52 must make sure that they, too, receive or can get the source code. If you 54 the recipients so that they can relink them with the library, after making 62 Also, for each distributor's protection, we want to make certain that 63 everyone understands that there is no warranty for this free library. If 65 recipients to know that what they have is not the original version, so that [all …]
/linux/tools/perf/pmu-events/arch/x86/knightslanding/
H A D	memory.json	11 …"BriefDescription": "Counts Demand code reads and prefetch code read requests that accounts for r… 21 …"BriefDescription": "Counts Demand code reads and prefetch code read requests that accounts for d… 31 …"BriefDescription": "Counts Demand code reads and prefetch code read requests that accounts for d… 41 …"BriefDescription": "Counts Demand code reads and prefetch code read requests that accounts for r… 51 …"BriefDescription": "Counts Demand code reads and prefetch code read requests that accounts for d… 61 …"BriefDescription": "Counts Demand code reads and prefetch code read requests that accounts for d… 71 …"BriefDescription": "Counts Demand cacheable data and L1 prefetch data read requests that account… 81 …"BriefDescription": "Counts Demand cacheable data and L1 prefetch data read requests that account… 91 …"BriefDescription": "Counts Demand cacheable data and L1 prefetch data read requests that account… 101 …"BriefDescription": "Counts Demand cacheable data and L1 prefetch data read requests that account… [all …]
H A D	cache.json	3 …"BriefDescription": "Counts the number of MEC requests that were not accepted into the L2Q because… 42 …that reference a cache line (cacheable requests) excluding SW prefetches filling only to L2 cache … 67 …"BriefDescription": "Counts the loads retired that get the data from the other core in the same ti… 73 …"PublicDescription": "This event counts the number of load micro-ops retired that got data from an… 78 "BriefDescription": "Counts the number of load micro-ops retired that miss in L1 D cache", 82 …: "This event counts the number of load micro-ops retired that miss in L1 Data cache. Note that pr… 87 …"BriefDescription": "Counts the number of load micro-ops retired that hit in the L2 (Precise Event… 93 …"PublicDescription": "This event counts the number of load micro-uops retired that hit in the L2 (… 98 …"BriefDescription": "Counts the number of load micro-ops retired that miss in the L2 (Precise Even… 104 …"PublicDescription": "This event counts the number of load micro-ops retired that miss in the L2 (… [all …]
/linux/Documentation/admin-guide/
H A D	reporting-issues.rst	15 you don't find any, install `the latest release from that series 31 If it shows the problem, search for the change that fixed it in mainline and 47 Once the report is out, answer any questions that come up and help where you 48 can. That includes keeping the ball rolling by occasionally retesting with newer 55 developers. It might be all that's needed for people already familiar with 63 a slightly different order. That's in your interest, to make sure you notice 64 early if an issue that looks like a Linux kernel problem is actually caused by 80 issue, or a really severe problem: those are 'issues of high priority' that 81 need special handling in some steps that are about to follow. 83 * Make sure it's not the kernel's surroundings that are causing the issue [all …]
/linux/include/kunit/
H A D	test.h	98 * that makes expectations and assertions (see KUNIT_EXPECT_TRUE() and 196 * is used to lazily generate a series of arbitrarily typed values that fit into 232 * A kunit_suite is a collection of related &struct kunit_case s, such that 237 * Note that @exit and @suite_exit will run even if @init or @suite_init 298 * Because resources is a list that may be updated multiple times (with 393 * This functions similar to kunit_test_suites() except that it compiles the 397 * _probe; so that modpost suppresses warnings about referencing init data 429 * Note that some internal context data is also allocated with GFP_KERNEL, 442 * Note that some internal context data is also allocated with GFP_KERNEL, 651 * The opposite of KUNIT_FAIL(), it is an expectation that cannot fail. In other [all …]
/linux/Documentation/networking/devlink/
H A D	devlink-trap.rst	21 kernel so that it will route it as well and generate an ICMP Time Exceeded 39 as it allows users to obtain further visibility into packet drops that would 123 Generic packet traps are used to describe traps that trap well-defined packets 124 or packets that are trapped due to well-defined conditions (e.g., TTL error). 136 - Traps incoming packets that the device decided to drop because of a 140 - Traps incoming packets that the device decided to drop in case of VLAN 145 - Traps incoming packets that the device decided to drop in case they are 146 tagged with a VLAN that is not configured on the ingress bridge port 149 - Traps incoming packets that the device decided to drop in case the STP 153 - Traps packets that the device decided to drop in case they need to be [all …]
/linux/tools/perf/pmu-events/arch/arm64/ampere/ampereonex/
H A D	core-imp-def.json	15 "PublicDescription": "Predictable branch speculatively executed that hit any level of BTB", 18 "BriefDescription": "Predictable branch speculatively executed that hit any level of BTB" 21 …"PublicDescription": "Predictable conditional branch speculatively executed that hit any level of … 24 …"BriefDescription": "Predictable conditional branch speculatively executed that hit any level of B… 27 …scription": "Predictable taken branch speculatively executed that hit any level of BTB that access… 30 …scription": "Predictable taken branch speculatively executed that hit any level of BTB that access… 33 …scription": "Predictable taken branch speculatively executed that hit any level of BTB that access… 36 …scription": "Predictable taken branch speculatively executed that hit any level of BTB that access… 39 …"PublicDescription": "Predictable unconditional branch speculatively executed that did not hit any… 42 …"BriefDescription": "Predictable unconditional branch speculatively executed that did not hit any … [all …]
/linux/tools/perf/pmu-events/arch/x86/sierraforest/
H A D	uncore-cache.json	22 …"BriefDescription": "Counts transactions that looked into the multi-socket cacheline Directory sta… 32 …"BriefDescription": "Counts transactions that looked into the multi-socket cacheline Directory st… 158 …Note the non-standard filtering equation. This event will count requests that lookup the cache mu… 224 …Note the non-standard filtering equation. This event will count requests that lookup the cache mu… 246 …Note the non-standard filtering equation. This event will count requests that lookup the cache mu… 268 …Note the non-standard filtering equation. This event will count requests that lookup the cache mu… 279 …Note the non-standard filtering equation. This event will count requests that lookup the cache mu… 301 …Note the non-standard filtering equation. This event will count requests that lookup the cache mu… 334 …Note the non-standard filtering equation. This event will count requests that lookup the cache mu… 356 …Note the non-standard filtering equation. This event will count requests that lookup the cache mu… [all …]
/linux/Documentation/admin-guide/pm/
H A D	cpuidle.rst	33 CPU idle time management operates on CPUs as seen by the CPU scheduler (that 35 work in the system). In its view, CPUs are logical units. That is, they need 38 entity which appears to be fetching instructions that belong to one sequence 43 program) at a time, it is a CPU. In that case, if the hardware is asked to 44 enter an idle state, that applies to the processor as a whole. 51 time. The entire cores are CPUs in that case and if the hardware is asked to 52 enter an idle state, that applies to the core that asked for it in the first 54 that the core belongs to (in fact, it may apply to an entire hierarchy of larger 57 remaining core asks the processor to enter an idle state, that may trigger it 59 other cores in that unit. [all …]
/linux/tools/perf/pmu-events/arch/x86/silvermont/
H A D	cache.json	3 …"BriefDescription": "Counts the number of request that were not accepted into the L2Q because the … 7 …that would have gone directly to the XQ, but are rejected due to a full or nearly full condition, … 15 …that fetch is stalled due to an outstanding ICache miss. That is, the decoder queue is able to acc… 20 … "BriefDescription": "Counts the number of request from the L2 that were not accepted into the XQ", 24 …"PublicDescription": "This event counts the number of demand and prefetch transactions that the L2… 41 …"PublicDescription": "This event counts requests originating from the core that references a cache… 69 …"PublicDescription": "This event counts the number of load ops retired that got data from the othe… 78 …ption": "This event counts the number of load ops retired that miss in L1 Data cache. Note that pr… 88 "PublicDescription": "This event counts the number of load ops retired that hit in the L2.", 98 … "PublicDescription": "This event counts the number of load ops retired that miss in the L2.", [all …]
/linux/Documentation/RCU/
H A D	checklist.rst	9 that make use of RCU. Violating any of the rules listed below will 10 result in the same sorts of problems that leaving out a locking primitive 17 performance measurements show that RCU is nonetheless the right 36 of lockless algorithms that garbage collectors do. 54 relating to itself that other tasks can read, there by definition 55 can be no bottleneck). Note that the definition of "large" has 74 Please note that you cannot rely on code known to be built 87 any locks or atomic operations. This means that readers will 94 RCU-protected data structures that have been added to 100 locks (that are acquired by both readers and writers) [all …]
/linux/Documentation/maintainer/
H A D	rebasing-and-merging.rst	12 those tools incorrectly, but avoiding problems is not actually all that 15 One thing to be aware of in general is that, unlike many other projects, 26 within a repository. There are two different types of operations that are 43 history; used improperly, it can obscure that history and introduce bugs. 45 There are a few rules of thumb that can help developers to avoid the worst 48 - History that has been exposed to the world beyond your private system 51 work is in need of rebasing, that is usually a sign that it is not yet 54 That said, there are always exceptions. Some trees (linux-next being 58 testing services. If you do expose a branch that may be unstable in 59 this way, be sure that prospective users know not to base work on it. [all …]

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