| /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/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/Documentation/userspace-api/media/v4l/ |
| H A D | colorspaces.rst | 21 the human eye has color receptors that are sensitive to three different 23 color. Be glad you are not a mantis shrimp as those are sensitive to 12 28 color receptors are stimulated. This is based on the Spectral Power 36 those receptors and are perceived as the same color, even though the SPD 44 After some further mathematical transforms these stimuli are known as 46 color as perceived by a human unambiguously. These X, Y and Z values are 57 The x and y values are the chromaticity coordinates and can be used to 60 colors are specified with lower case 'x' and 'y', then the CIE xyY 65 will find reading resources that go into much more detail if you are 72 phosphors used in the displays. These *color primaries* are part of what [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/filesystems/nfs/ |
| H A D | nfsd-maintainer-entry-profile.rst | 5 documents (found in Documentation/process/) with customs that are 16 reside on file systems that are shared by NFS servers. A single 30 conversations that are not related directly to the Linux NFS stack. 41 Bug reports against upstream Linux code bases are welcome on the 66 fests). Non-Linux NFS clients are not part of upstream NFSD CI/CD. 101 easy to introduce a new administrative setting. However, there are 105 - As with any API, administrative interfaces are difficult to get 108 - Once they are documented and have a legacy of use, administrative 146 - Counters are always on, but provide little information about 150 (via a glob). These are generally low overhead, and thus are [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/tools/perf/pmu-events/arch/arm64/arm/cortex-a75/ |
| H A D | pipeline.json | 21 "PublicDescription": "Duration for which all slots in the Load-Store Unit (LSU) are busy", 24 "BriefDescription": "Duration for which all slots in the Load-Store Unit (LSU) are busy" 27 …all slots in the load-store issue queue are busy. This event counts the cycles where all slots in … 30 …all slots in the load-store issue queue are busy. This event counts the cycles where all slots in … 33 … in the data processing issue queue are busy. This event counts the cycles where all slots in the … 36 … in the data processing issue queue are busy. This event counts the cycles where all slots in the … 39 …"PublicDescription": "Duration for which all slots in the data engine issue queue are busy. This e… 42 …"BriefDescription": "Duration for which all slots in the data engine issue queue are busy. This ev…
|
| /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/tools/include/nolibc/ |
| H A D | nolibc.h | 10 * All syscalls are declared as static functions so that they can be optimized 13 * Syscalls are split into 3 levels: 15 * assembly code in compound expressions. These are called __nolibc_syscall0() to 17 * are castto a long stored in a register. These expressions always return 23 * depending on the syscall definition. These functions are responsible 26 * A few of them are architecture-specific because the syscalls are not all 43 * Some stdint-like integer types are defined. These are valid on all currently 44 * supported architectures, because signs are enforce [all...] |
| /linux/Documentation/admin-guide/device-mapper/ |
| H A D | statistics.rst | 6 regions of a DM device. If no regions are defined no statistics are 8 devices are currently supported. 14 The I/O statistics counters for each step-sized area of a region are 16 Documentation/admin-guide/iostats.rst). But two extra counters (12 and 13) are 22 The reported times are in milliseconds and the granularity depends on 24 reported times are in nanoseconds. 65 The following optional arguments are supported: 70 used, the resulting times are in nanoseconds instead of 71 milliseconds. Precise timestamps are a little bit slower 75 numbers n1, n2, etc are times that represent the boundaries [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/net/netlabel/ |
| H A D | netlabel_mgmt.h | 23 * The following NetLabel payloads are supported by the management interface. 33 * If IPv4 is specified the following attributes are required: 38 * If IPv6 is specified the following attributes are required: 43 * If using NETLBL_NLTYPE_CIPSOV4 the following attributes are required: 47 * If using NETLBL_NLTYPE_UNLABELED no other attributes are required, 71 * If the IP address selectors are not used the following attribute is 76 * If the IP address selectors are used then the following attritbute is 82 * attributes are required: 87 * attributes are required. 97 * If using NETLBL_NLTYPE_CIPSOV4 the following attributes are required: [all …]
|
| /linux/Documentation/ |
| H A D | atomic_t.txt | 5 RMW operations between CPUs (atomic operations on MMIO are not supported and 82 The non-RMW ops are (typically) regular LOADs and STOREs and are canonically 86 and are doing it wrong. 91 C Atomic-RMW-ops-are-atomic-WRT-atomic_set 142 these are limited to the arithmetic operations because those are 143 reversible. Bitops are irreversible and therefore the modified value 150 - misc; the special purpose operations that are commonly used and would, 152 are time critical and can, (typically) on LL/SC architectures, be more 155 All these operations are SMP atomic; that is, the operations (for a single 165 - non-RMW operations are unordered; [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 …]
|