are (full) in projects: Linux-v6.1 - OpenGrok search results

Project(s)

Full Search
Definition
Symbol
File Path
History
Type

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

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

/Linux-v6.1/tools/perf/pmu-events/arch/x86/ivytown/
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 …]
D	uncore-other.json	8 …e write cache.; When two requests to the same address from the same source are received back to ba… 28 …wnership but have not yet returned their data to the uncore. These writes are generally queued up… 38 …wnership but have not yet returned their data to the uncore. These writes are generally queued up… 48 …"PublicDescription": "Accumulates the number of writes (and write prefetches) that are outstanding… 58 …"PublicDescription": "Accumulates the number of writes (and write prefetches) that are outstanding… 68 …"PublicDescription": "Accumulates the number of reads that are outstanding in the uncore in each c… 78 …"PublicDescription": "Accumulates the number of reads that are outstanding in the uncore in each c… 88 …"PublicDescription": "Accumulates the number of reads and writes that are outstanding in the uncor… 98 …"PublicDescription": "Accumulates the number of reads and writes that are outstanding in the uncor… 108 …"PublicDescription": "Accumulates the number of writes (and write prefetches) that are outstandin… [all …]
/Linux-v6.1/Documentation/input/
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-v6.1/Documentation/fb/
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-v6.1/tools/perf/pmu-events/arch/x86/jaketown/
D	uncore-cache.json	154 …are passing by and when packets are being sunk, but does not include when packets are being sent f… 164 …are passing by and when packets are being sunk, but does not include when packets are being sent f… 174 …are passing by and when packets are being sunk, but does not include when packets are being sent f… 184 …are passing by and when packets are being sunk, but does not include when packets are being sent f… 194 …are passing by and when packets are being sunk, but does not include when packets are being sent f… 204 …are passing by and when packets are being sunk, but does not include when packets are being sent f… 214 …are passing by and when packets are being sunk, but does not include when packets are being sent f… 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… [all …]
D	uncore-other.json	28 …wnership but have not yet returned their data to the uncore. These writes are generally queued up… 38 …wnership but have not yet returned their data to the uncore. These writes are generally queued up… 48 …"PublicDescription": "Accumulates the number of writes (and write prefetches) that are outstanding… 58 …"PublicDescription": "Accumulates the number of writes (and write prefetches) that are outstanding… 68 …"PublicDescription": "Accumulates the number of reads that are outstanding in the uncore in each c… 78 …"PublicDescription": "Accumulates the number of reads that are outstanding in the uncore in each c… 88 …"PublicDescription": "Accumulates the number of reads and writes that are outstanding in the uncor… 98 …"PublicDescription": "Accumulates the number of reads and writes that are outstanding in the uncor… 108 …"PublicDescription": "Accumulates the number of writes (and write prefetches) that are outstandin… 118 …"PublicDescription": "Accumulates the number of writes (and write prefetches) that are outstandin… [all …]
/Linux-v6.1/sound/pci/cs46xx/
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-v6.1/Documentation/userspace-api/media/v4l/
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-v6.1/tools/perf/pmu-events/arch/x86/broadwellde/
D	uncore-other.json	8 …"PublicDescription": "Accumulates the number of reads and writes that are outstanding in the uncor… 18 …"PublicDescription": "Accumulates the number of reads and writes that are outstanding in the uncor… 475 …mes when it is not possible to issue a request to the R2PCIe because there are no AD Egress Credit… 484 …er times when it is not possible to issue data to the R2PCIe because there are no BL Egress Credit… 529 …are acquired in the R2PCIe agent for sending transactions into the IIO on either NCB or NCS are in… 539 …are acquired in the R2PCIe agent for sending transactions into the IIO on either NCB or NCS are in… 549 …are acquired in the R2PCIe agent for sending transactions into the IIO on either NCB or NCS are in… 559 …are in use. Transactions from the BL ring going into the IIO Agent must first acquire a credit. … 569 …are in use. Transactions from the BL ring going into the IIO Agent must first acquire a credit. … 579 …are in use. Transactions from the BL ring going into the IIO Agent must first acquire a credit. … [all …]
D	uncore-cache.json	32 …he number of cycles either the local distress or incoming distress signals are asserted. Incoming… 281 …are passing by and when packets are being sunk, but does not include when packets are being sent f… 291 …are passing by and when packets are being sunk, but does not include when packets are being sent f… 301 …are passing by and when packets are being sunk, but does not include when packets are being sent f… 311 …are passing by and when packets are being sunk, but does not include when packets are being sent f… 321 …are passing by and when packets are being sunk, but does not include when packets are being sent f… 331 …are passing by and when packets are being sunk, but does not include when packets are being sent f… 341 …are passing by and when packets are being sunk, but does not include when packets are being sent f… 351 …are passing by and when packets are being sunk, but does not include when packets are being sent f… 361 …are passing by and when packets are being sunk, but does not include when packets are being sent f… [all …]
/Linux-v6.1/Documentation/livepatch/
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, get 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-v6.1/tools/include/nolibc/
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 my_syscall0() to 17 * implementation is limited to 5 arguments. All input arguments are cast 24 * depending on the syscall definition. These functions are responsible 27 * A few of them are architecture-specific because the syscalls are not all 45 * Some stdint-like integer types are defined. These are valid on all currently 46 * supported architectures, because signs are enforced, ints are assumed to be 53 * The definitions start with the architecture-specific parts, which are picked 54 * based on what the compiler knows about the target architecture, and are [all …]
/Linux-v6.1/Documentation/admin-guide/pm/
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-v6.1/tools/perf/pmu-events/arch/arm64/arm/cortex-a75/
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-v6.1/Documentation/process/
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-v6.1/Documentation/mm/
D	hugetlbfs_reserv.rst	10 Huge pages as described at :ref:`hugetlbpage` are typically 11 preallocated for application use. These huge pages are instantiated in a 12 task's address space at page fault time if the VMA indicates huge pages are 28 This description is primarily targeted at kernel developers who are modifying 37 huge pages are only available to the task which reserved them. 62 The 'from' and 'to' fields of the file region structure are huge page 67 These are stored in the bottom bits of the reservation map pointer. 89 of mappings. Location differences are: 95 inode->i_mapping->private_data. Since shared mappings are always backed 103 Reservations are created when a huge page backed shared memory segment is [all …]
/Linux-v6.1/Documentation/admin-guide/LSM/
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-v6.1/Documentation/devicetree/bindings/
D	writing-schema.rst	6 Devicetree bindings are written using json-schema vocabulary. Schema files are 18 top-level json-schema properties used are: 48 schema. By default, without 'select', nodes are matched against their possible 58 binding. The exact schema syntax depends on whether properties are known, 59 common properties (e.g. 'interrupts') or are binding/vendor-specific 68 Optional. Similar to 'properties', but names are regex. 78 Unless noted otherwise, all properties are required. 85 vocabulary for that property. The properties schemas are what are used for 89 binding schema need to be defined such as how many values are valid or what 90 possible values are valid. [all …]
/Linux-v6.1/Documentation/admin-guide/device-mapper/
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-v6.1/Documentation/filesystems/
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 …]
D	squashfs.rst	10 directories. Inodes in the system are very small and all blocks are packed to 11 minimise data overhead. Block sizes greater than 4K are supported up to a 51 directory data are highly compacted, and packed on byte boundaries. Each 100 Compressed data blocks are written to the filesystem as files are read from 103 xattr tables are written. 110 these are stored here. 115 Metadata (inodes and directories) are compressed in 8Kbyte blocks. Each 120 Inodes are packed into the metadata blocks, and are not aligned to block 121 boundaries, therefore inodes overlap compressed blocks. Inodes are identified 126 To maximise compression there are different inodes for each file type [all …]
/Linux-v6.1/Documentation/hid/
D	hid-transport.rst	15 drivers on top of it. The transport drivers are responsible for raw data 18 and quirks are handled by all layers depending on the quirk. 62 drivers are not required to register themselves with HID core. HID core is never 63 aware of which transport drivers are available and is not interested in it. It 68 this struct are used by HID core to communicate with the device. 70 Transport drivers are responsible for detecting device failures and unplugging. 100 reports. No management commands or data acknowledgements are sent on this 103 send their input events on this channel. Outgoing events are normally 107 channel and are normally ignored. Instead, devices only send management 111 Outgoing reports are usually sent on the ctrl channel via synchronous [all …]
/Linux-v6.1/net/netlabel/
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-v6.1/Documentation/
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-v6.1/Documentation/core-api/
D	this_cpu_ops.rst	8 this_cpu operations are a way of optimizing access to per cpu 18 This means that there are no atomicity issues between the calculation of 24 Read-modify-write operations are of particular interest. Frequently 32 synchronization is not necessary since we are dealing with per cpu 34 processor should be accessing that variable and therefore there are no 37 Please note that accesses by remote processors to a per cpu area are 45 are defined. These operations can be used without worrying about 116 the value of the individual counters for each processor are 120 Per cpu variables are used for performance reasons. Bouncing cache 190 Operations on these fields are straightforward:: [all …]

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