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

Project(s)

Full Search
Definition
Symbol
File Path
History
Type

Searched full:are (Results 1 – 25 of 7545) sorted by relevance

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

/linux/tools/perf/pmu-events/arch/x86/ivytown/
H A D	uncore-io.json	17 …are acquired in the R2PCIe agent for sending transactions into the IIO on either NCB or NCS are in… 27 …are acquired in the R2PCIe agent for sending transactions into the IIO on either NCB or NCS are in… 37 …are acquired in the R2PCIe agent for sending transactions into the IIO on either NCB or NCS are in… 47 … available. NCB, or non-coherent bypass messages are used to transmit data without coherency (and… 57 …are in use. Transactions from the BL ring going into the IIO Agent must first acquire a credit. … 67 …are in use. Transactions from the BL ring going into the IIO Agent must first acquire a credit. … 77 …are in use. Transactions from the BL ring going into the IIO Agent must first acquire a credit. … 87 …stop. This includes when packets are passing by and when packets are being sunk, but does not inc… 97 …stop. This includes when packets are passing by and when packets are being sunk, but does not inc… 107 …stop. This includes when packets are passing by and when packets are being sunk, but does not inc… [all …]
H A D	uncore-cache.json	224 …are passing by and when packets are being sunk, but does not include when packets are being sent f… 234 …are passing by and when packets are being sunk, but does not include when packets are being sent f… 244 …are passing by and when packets are being sunk, but does not include when packets are being sent f… 254 …are passing by and when packets are being sunk, but does not include when packets are being sent f… 264 …are passing by and when packets are being sunk, but does not include when packets are being sent f… 274 …are passing by and when packets are being sunk, but does not include when packets are being sent f… 284 …are passing by and when packets are being sunk, but does not include when packets are being sent f… 294 …are passing by and when packets are being sunk, but does not include when packets are being sent f… 304 …are passing by and when packets are being sunk, but does not include when packets are being sent f… 314 …are passing by and when packets are being sunk, but does not include when packets are being sent f… [all …]
/linux/tools/perf/pmu-events/arch/x86/broadwellx/
H A D	uncore-io.json	53 …are acquired in the R2PCIe agent for sending transactions into the IIO on either NCB or NCS are in… 63 …are acquired in the R2PCIe agent for sending transactions into the IIO on either NCB or NCS are in… 73 …are acquired in the R2PCIe agent for sending transactions into the IIO on either NCB or NCS are in… 83 …are in use. Transactions from the BL ring going into the IIO Agent must first acquire a credit. … 93 …are in use. Transactions from the BL ring going into the IIO Agent must first acquire a credit. … 103 …are in use. Transactions from the BL ring going into the IIO Agent must first acquire a credit. … 113 …stop. This includes when packets are passing by and when packets are being sunk, but does not inc… 123 …stop. This includes when packets are passing by and when packets are being sunk, but does not inc… 133 …stop. This includes when packets are passing by and when packets are being sunk, but does not inc… 143 …stop. This includes when packets are passing by and when packets are being sunk, but does not inc… [all …]
H A D	uncore-cache.json	9 "PublicDescription": "Counts the number of entries successfully inserted into the TOR that match qualifications specified by the subevent. There are a number of subevent 'filters' but only a subset of the subevent combinations are valid. Subevents that require an opcode or NID match require the Cn_MSR_PMON_BOX_FILTER.{opc, nid} field to be set. If, for example, one wanted to count DRD Local Misses, one should select MISS_OPC_MATCH and set Cn_MSR_PMON_BOX_FILTER.opc to DRD (0x182).; Miss transactions inserted into the TOR that match an opcode.", 21 "PublicDescription": "Counts the number of entries successfully inserted into the TOR that match qualifications specified by the subevent. There are a number of subevent 'filters' but only a subset of the subevent combinations are valid. Subevents that require an opcode or NID match require the Cn_MSR_PMON_BOX_FILTER.{opc, nid} field to be set. If, for example, one wanted to count DRD Local Misses, one should select MISS_OPC_MATCH and set Cn_MSR_PMON_BOX_FILTER.opc to DRD (0x182).; Miss transactions inserted into the TOR that match an opcode.", 33 "PublicDescription": "Counts the number of entries successfully inserted into the TOR that match qualifications specified by the subevent. There are a number of subevent 'filters' but only a subset of the subevent combinations are valid. Subevents that require an opcode or NID match require the Cn_MSR_PMON_BOX_FILTER.{opc, nid} field to be set. If, for example, one wanted to count DRD Local Misses, one should select MISS_OPC_MATCH and set Cn_MSR_PMON_BOX_FILTER.opc to DRD (0x182).; Miss transactions inserted into the TOR that match an opcode.", 45 "PublicDescription": "Counts the number of entries successfully inserted into the TOR that match qualifications specified by the subevent. There are a number of subevent 'filters' but only a subset of the subevent combinations are valid. Subevents that require an opcode or NID match require the Cn_MSR_PMON_BOX_FILTER.{opc, nid} field to be set. If, for example, one wanted to count DRD Local Misses, one should select MISS_OPC_MATCH and set Cn_MSR_PMON_BOX_FILTER.opc to DRD (0x182).; Miss transactions inserted into the TOR that match an opcode.", 57 "PublicDescription": "Counts the number of entries successfully inserted into the TOR that match qualifications specified by the subevent. There are a number of subevent 'filters' but only a subset of the subevent combinations are vali [all...]
/linux/tools/perf/pmu-events/arch/x86/broadwellde/
H A D	uncore-io.json	53 …are acquired in the R2PCIe agent for sending transactions into the IIO on either NCB or NCS are in… 63 …are acquired in the R2PCIe agent for sending transactions into the IIO on either NCB or NCS are in… 73 …are acquired in the R2PCIe agent for sending transactions into the IIO on either NCB or NCS are in… 83 …are in use. Transactions from the BL ring going into the IIO Agent must first acquire a credit. … 93 …are in use. Transactions from the BL ring going into the IIO Agent must first acquire a credit. … 103 …are in use. Transactions from the BL ring going into the IIO Agent must first acquire a credit. … 113 …stop. This includes when packets are passing by and when packets are being sunk, but does not inc… 123 …stop. This includes when packets are passing by and when packets are being sunk, but does not inc… 133 …stop. This includes when packets are passing by and when packets are being sunk, but does not inc… 143 …stop. This includes when packets are passing by and when packets are being sunk, but does not inc… [all …]
H A D	uncore-cache.json	32 "PublicDescription": "Counts the number of cycles either the local distress or incoming distress signals are asserted. Incoming distress includes both up and dn.", 281 "PublicDescription": "Counts the number of cycles that the AD ring is being used at this ring stop. This includes when packets are passing by and when packets are being sunk, but does not include when packets are being sent from the ring stop. We really have two rings in BDX -- a clockwise ring and a counter-clockwise ring. On the left side of the ring, the UP direction is on the clockwise ring and DN is on the counter-clockwise ring. On the right side of the ring, this is reversed. The first half of the CBos are on the left side of the ring, and the 2nd half are on the right side of the ring. In other words (for example), in a 4c part, Cbo 0 UP AD is NOT the same ring as CBo 2 UP AD because they are on opposite sides of the ring.", 291 "PublicDescription": "Counts the number of cycles that the AD ring is being used at this ring stop. This includes when packets are passing by and when packets are being sunk, but does not include when packets are bein [all...]
/linux/tools/perf/pmu-events/arch/x86/jaketown/
H A D	uncore-io.json	17 …are acquired in the R2PCIe agent for sending transactions into the IIO on either NCB or NCS are in… 27 …are acquired in the R2PCIe agent for sending transactions into the IIO on either NCB or NCS are in… 37 …are acquired in the R2PCIe agent for sending transactions into the IIO on either NCB or NCS are in… 47 … available. NCB, or non-coherent bypass messages are used to transmit data without coherency (and… 57 … available. NCB, or non-coherent bypass messages are used to transmit data without coherency (and… 67 … available. NCB, or non-coherent bypass messages are used to transmit data without coherency (and… 77 …are in use. Transactions from the BL ring going into the IIO Agent must first acquire a credit. … 87 …are in use. Transactions from the BL ring going into the IIO Agent must first acquire a credit. … 97 …are in use. Transactions from the BL ring going into the IIO Agent must first acquire a credit. … 107 …stop. This includes when packets are passing by and when packets are being sunk, but does not inc… [all …]
H A D	uncore-cache.json	161 …are passing by and when packets are being sunk, but does not include when packets are being sent f… 171 …are passing by and when packets are being sunk, but does not include when packets are being sent f… 181 …are passing by and when packets are being sunk, but does not include when packets are being sent f… 191 …are passing by and when packets are being sunk, but does not include when packets are being sent f… 201 …are passing by and when packets are being sunk, but does not include when packets are being sent f… 211 …are passing by and when packets are being sunk, but does not include when packets are being sent f… 221 …are passing by and when packets are being sunk, but does not include when packets are being sent f… 231 …are passing by and when packets are being sunk, but does not include when packets are being sent f… 241 …are passing by and when packets are being sunk, but does not include when packets are being sent f… 251 …are passing by and when packets are being sunk, but does not include when packets are being sent f… [all …]
/linux/tools/perf/pmu-events/arch/x86/haswellx/
H A D	uncore-io.json	53 …are acquired in the R2PCIe agent for sending transactions into the IIO on either NCB or NCS are in… 63 …are acquired in the R2PCIe agent for sending transactions into the IIO on either NCB or NCS are in… 73 …are acquired in the R2PCIe agent for sending transactions into the IIO on either NCB or NCS are in… 83 …are in use. Transactions from the BL ring going into the IIO Agent must first acquire a credit. … 93 …are in use. Transactions from the BL ring going into the IIO Agent must first acquire a credit. … 103 …are in use. Transactions from the BL ring going into the IIO Agent must first acquire a credit. … 113 …stop. This includes when packets are passing by and when packets are being sunk, but does not inc… 123 …stop. This includes when packets are passing by and when packets are being sunk, but does not inc… 133 …stop. This includes when packets are passing by and when packets are being sunk, but does not inc… 143 …stop. This includes when packets are passing by and when packets are being sunk, but does not inc… [all …]
H A D	uncore-cache.json	9 "PublicDescription": "Counts the number of entries successfully inserted into the TOR that match qualifications specified by the subevent. There are a number of subevent 'filters' but only a subset of the subevent combinations are valid. Subevents that require an opcode or NID match require the Cn_MSR_PMON_BOX_FILTER.{opc, nid} field to be set. If, for example, one wanted to count DRD Local Misses, one should select MISS_OPC_MATCH and set Cn_MSR_PMON_BOX_FILTER.opc to DRD (0x182).; Miss transactions inserted into the TOR that match an opcode.", 21 "PublicDescription": "Counts the number of entries successfully inserted into the TOR that match qualifications specified by the subevent. There are a number of subevent 'filters' but only a subset of the subevent combinations are valid. Subevents that require an opcode or NID match require the Cn_MSR_PMON_BOX_FILTER.{opc, nid} field to be set. If, for example, one wanted to count DRD Local Misses, one should select MISS_OPC_MATCH and set Cn_MSR_PMON_BOX_FILTER.opc to DRD (0x182).; Miss transactions inserted into the TOR that match an opcode.", 33 "PublicDescription": "Counts the number of entries successfully inserted into the TOR that match qualifications specified by the subevent. There are a number of subevent 'filters' but only a subset of the subevent combinations are valid. Subevents that require an opcode or NID match require the Cn_MSR_PMON_BOX_FILTER.{opc, nid} field to be set. If, for example, one wanted to count DRD Local Misses, one should select MISS_OPC_MATCH and set Cn_MSR_PMON_BOX_FILTER.opc to DRD (0x182).; Miss transactions inserted into the TOR that match an opcode.", 45 "PublicDescription": "Counts the number of entries successfully inserted into the TOR that match qualifications specified by the subevent. There are a number of subevent 'filters' but only a subset of the subevent combinations are valid. Subevents that require an opcode or NID match require the Cn_MSR_PMON_BOX_FILTER.{opc, nid} field to be set. If, for example, one wanted to count DRD Local Misses, one should select MISS_OPC_MATCH and set Cn_MSR_PMON_BOX_FILTER.opc to DRD (0x182).; Miss transactions inserted into the TOR that match an opcode.", 57 "PublicDescription": "Counts the number of entries successfully inserted into the TOR that match qualifications specified by the subevent. There are a number of subevent 'filters' but only a subset of the subevent combinations are vali [all...]
/linux/tools/perf/pmu-events/arch/arm64/arm/neoverse-n1/
H A D	exception.json	4 … FIQ, SError, and other synchronous exceptions. Exceptions are counted whether or not they are tak… 12 …are taken locally that are due to attempting to execute an instruction that is UNDEFINED. Attempti… 20 …"PublicDescription": "Counts synchronous exceptions that are taken locally and caused by Instructi… 24 …ounts exceptions that are taken locally and are caused by data aborts or SErrors. Conditions that … 28 … "PublicDescription": "Counts IRQ exceptions including the virtual IRQs that are taken locally." 32 … "PublicDescription": "Counts FIQ exceptions including the virtual FIQs that are taken locally." 44 …"PublicDescription": "Counts exceptions which are traps not taken locally and are caused by Instru… 48 …tions which are traps not taken locally and are caused by Data Aborts or SError interrupts. Condit… 52 …ion": "Counts the number of synchronous trap exceptions which are not taken locally and are not SV… 56 …"PublicDescription": "Counts IRQ exceptions including the virtual IRQs that are not taken locally." [all …]
/linux/tools/perf/pmu-events/arch/arm64/arm/neoverse-v1/
H A D	exception.json	4 … FIQ, SError, and other synchronous exceptions. Exceptions are counted whether or not they are tak… 12 …are taken locally that are due to attempting to execute an instruction that is UNDEFINED. Attempti… 20 …"PublicDescription": "Counts synchronous exceptions that are taken locally and caused by Instructi… 24 …ounts exceptions that are taken locally and are caused by data aborts or SErrors. Conditions that … 28 … "PublicDescription": "Counts IRQ exceptions including the virtual IRQs that are taken locally." 32 … "PublicDescription": "Counts FIQ exceptions including the virtual FIQs that are taken locally." 44 …"PublicDescription": "Counts exceptions which are traps not taken locally and are caused by Instru… 48 …tions which are traps not taken locally and are caused by Data Aborts or SError interrupts. Condit… 52 …ion": "Counts the number of synchronous trap exceptions which are not taken locally and are not SV… 56 …"PublicDescription": "Counts IRQ exceptions including the virtual IRQs that are not taken locally." [all …]
/linux/Documentation/input/
H A D	gamepad.rst	12 document defines how gamepads are supposed to report their data. 44 4 buttons in diamonds-shape (on the right side). The buttons are 56 all devices have both or any, but they are present at most times. 59 Triggers are located on the upper-side of the pad in vertical direction. 60 Not all devices provide them, but the upper buttons are normally named 63 Many devices provide force-feedback features. But are mostly just 79 All new gamepads are supposed to comply with this mapping. Please report any 82 There are a lot of less-featured/less-powerful devices out there, which re-use 103 of the labels on the buttons, the codes are sent according to the 106 Please note that 2- and 3-button pads are fairly rare and old. You might [all …]
/linux/Documentation/fb/
H A D	api.rst	13 buffer core are not described. 24 Device and driver capabilities are reported in the fixed screen information 39 When supported, formats are configured using a FOURCC instead of manually 46 Pixels are stored in memory in hardware-dependent formats. Applications need 50 Formats are described by frame buffer types and visuals. Some visuals require 51 additional information, which are stored in the variable screen information 55 macropixels. Types describe how macropixels are stored in memory. The following 56 types and visuals are supported. 60 Macropixels are stored contiguously in a single plane. If the number of bits 61 per macropixel is not a multiple of 8, whether macropixels are padded to the [all …]
/linux/sound/pci/cs46xx/
H A D	cs46xx.h	173 * The following defines are for the flags in the host interrupt status 208 * The following defines are for the flags in the host signal register 0. 245 * The following defines are for the flags in the host interrupt control 252 * The following defines are for the flags in the DMA status register. 260 * The following defines are for the flags in the host DMA source address 275 * The following defines are for the flags in the host DMA destination address 290 * The following defines are for the flags in the host DMA control register. 299 * The following defines are for the flags in the host DMA control register. 329 * The following defines are for the flags in the performance monitor control 356 * The following defines are for the flags in the performance counter value 1 [all …]
/linux/Documentation/userspace-api/media/v4l/
H A D	colorspaces.rst	20 the human eye has color receptors that are sensitive to three different 22 color. Be glad you are not a mantis shrimp as those are sensitive to 12 27 color receptors are stimulated. This is based on the Spectral Power 35 those receptors and are perceived as the same color, even though the SPD 43 After some further mathematical transforms these stimuli are known as 45 color as perceived by a human unambiguously. These X, Y and Z values are 56 The x and y values are the chromaticity coordinates and can be used to 59 colors are specified with lower case 'x' and 'y', then the CIE xyY 64 will find reading resources that go into much more detail if you are 71 phosphors used in the displays. These color primaries are part of what [all …]
/linux/Documentation/livepatch/
H A D	livepatch.rst	15 There are many situations where users are reluctant to reboot a system. It may 26 There are multiple mechanisms in the Linux kernel that are directly related 30 - The kernel probes are the most generic. The code can be redirected by 39 are in any way modified. 43 Most of these problems are solved by using the dynamic ftrace framework as 46 a live patch is called with the help of a custom ftrace handler. But there are 53 Functions are there for a reason. They take some input parameters, acquire or 60 Most of these changes are self contained and the function presents itself 64 But there are more complex fixes. For example, a patch might change 70 when it is safe to do so, e.g. when the affected locks are released [all …]
/linux/Documentation/devicetree/bindings/
H A D	writing-schema.rst	6 Devicetree bindings are written using json-schema vocabulary. Schema files are 18 top-level json-schema properties used are: 47 block. The options are controlled with indicator characters following the key 50 parsed correctly, but are important when the text blocks are rendered to 51 another form. The options are as follows. 54 line breaks and leading whitespace are stripped. Paragraphs are delimited by 58 restrictions are on what the first character can be. 63 breaks on indented lines are also maintained. 78 schema. By default, without 'select', nodes are matched against their possible 88 binding. The exact schema syntax depends on whether properties are known, [all …]
/linux/Documentation/mm/
H A D	hugetlbfs_reserv.rst	8 Huge pages as described at Documentation/admin-guide/mm/hugetlbpage.rst are 9 typically preallocated for application use. These huge pages are instantiated 11 are to be used. If no huge page exists at page fault time, the task is sent 26 This description is primarily targeted at kernel developers who are modifying 35 huge pages are only available to the task which reserved them. 60 The 'from' and 'to' fields of the file region structure are huge page 65 These are stored in the bottom bits of the reservation map pointer. 87 of mappings. Location differences are: 93 inode->i_mapping->private_data. Since shared mappings are always backed 101 Reservations are created when a huge page backed shared memory segment is [all …]
/linux/Documentation/admin-guide/pm/
H A D	suspend-flows.rst	26 different sleep states of the system are quite similar, but there are some 36 states are mostly identical, so they both together will be referred to as 45 The following steps are taken in order to transition the system from the working 58 Tasks are frozen primarily in order to avoid unchecked hardware accesses 64 All user space tasks are intercepted as though they were sent a signal and 69 specific reasons are frozen subsequently, but they are not intercepted. 70 Instead, they are expected to periodically check whether or not they need 79 Devices are suspended in four phases called prepare, suspend, 87 phase and high-level ("action") interrupt handlers are prevented from being 90 Interrupts are still handled after that, but they are only acknowledged to [all …]
/linux/Documentation/admin-guide/device-mapper/
H A D	vdo-design.rst	43 Most of a vdo's main data structures are designed to be easily divided into 75 there are diminishing returns to looking further back in time. Therefore, 98 Records are collected into groups called chapters. New records are added to 106 reading. The records are written to a series of record pages based on the 116 chapters are read-only structures and their contents are never altered in 123 in the index, while unreferenced block names are forgotten over time. 128 mapping is updated as records for the block name are copied or updated, 145 accessed pages are cached so that these page reads can be amortized across 148 The volume index and the chapter indexes are implemented using a 150 entire block name (the key) for each entry, the entries are sorted by name [all …]
/linux/Documentation/process/
H A D	howto.rst	31 are not a good substitute for a solid C education and/or years of 32 experience, the following books are good for, if anything, reference: 39 adheres to the ISO C11 standard, it uses a number of extensions that are 42 portions of the C standard are not supported. Arbitrary long long 43 divisions and floating point are not allowed. It can sometimes be 49 Please remember that you are trying to learn how to work with the 54 possible about these standards ahead of time, as they are well 64 rules and how to use `SPDX <https://spdx.org/>`_ identifiers in source code are 67 not ask on the Linux kernel mailing list. The people on the mailing lists are 78 The Linux kernel source tree has a large range of documents that are [all …]
/linux/Documentation/admin-guide/LSM/
H A D	Smack.rst	15 are encouraged to compare Smack with the other mechanisms 22 - Basic utilities, which are helpful but not required 32 configurations are intolerant of IP options and can impede 44 There are five commands included in smackutil: 56 These two commands are obsolete with the introduction of 78 objects. The attributes are stored in the extended attribute security 82 The extended attributes that Smack uses are: 118 There are multiple ways to set a Smack label on a file:: 177 The following numbers are the categories:: 189 The following numbers are the categories:: [all …]
/linux/Documentation/rust/
H A D	testing.rst	9 There are three sorts of tests: 18 These are the tests that come from the examples in the Rust documentation. They 43 KUnit tests are documentation tests 46 These documentation tests are typically examples of usage of any item (e.g. 49 They are very convenient because they are just written alongside the 63 In userspace, the tests are collected and run via ``rustdoc``. Using the tool 65 (thus enforcing they are kept in sync with the code they document) and as well 94 operator are also supported as usual, e.g.: 104 The tests are also compiled with Clippy under ``CLIPPY=1``, just like normal 124 actually failed. Additionally, doctests are not run for nonpublic functions. [all …]
/linux/Documentation/filesystems/
H A D	ext2.rst	11 filesystem in use by Linux. There are also implementations available 17 Most defaults are determined by the filesystem superblock, and can be 18 set using tune2fs(8). Kernel-determined defaults are indicated by (*). 78 compression though these are not yet implemented (some are available as 86 The space in the device or file is split up into blocks. These are 95 Blocks are clustered into block groups in order to reduce fragmentation 99 Two blocks near the start of each group are reserved for the block usage 101 are in use. Since each bitmap is limited to a single block, this means 104 The block(s) following the bitmaps in each block group are designated 105 as the inode table for that block group and the remainder are the data [all …]

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