Searched full:checking (Results 1 – 25 of 251) sorted by relevance
1234567891011
| /Documentation/arch/arm64/ |
| D | memory-tagging-extension.rst | 95 preferred tag checking modes" section below.
101 Tag checking can also be disabled for a user thread by setting the
112 system call) are not checked if the user thread tag checking mode is
113 ``PR_MTE_TCF_NONE`` or ``PR_MTE_TCF_ASYNC``. If the tag checking mode is
133 Per-CPU preferred tag checking mode
136 On some CPUs the performance of MTE in stricter tag checking modes
137 is similar to that of less strict tag checking modes. This makes it
139 checking mode is requested, in order to gain the error detection
142 tag checking mode as the CPU's preferred tag checking mode.
144 The preferred tag checking mode for each CPU is controlled by
[all …]
|
| /Documentation/w1/slaves/ |
| D | w1_ds28e04.rst | 20 Support is provided through the sysfs files "eeprom" and "pio". CRC checking
31 to the EEPROM of the DS28E04. If CRC checking mode is enabled only
|
| /Documentation/networking/ |
| D | ipsec.rst | 38 packet len), the packet is dropped when checking the policy as this packet
46 will skip policy checking on receiver side.
|
| /Documentation/dev-tools/ |
| D | testing-overview.rst | 107 * Runtime Verification (RV) supports checking specific behaviours for a given
129 Sparse can help test the kernel by performing type-checking, lock checking,
130 value range checking, in addition to reporting various errors and warnings while
136 error checking, forgetting to set an error code in the return of an error path,
155 Sparse does type checking, such as verifying that annotated variables do not
|
| D | checkuapi.rst | 78 Checking changes to UAPI headers between HEAD and dirty tree...
102 Checking changes to UAPI headers between HEAD and dirty tree...
126 Checking changes to UAPI headers between HEAD and dirty tree...
152 Checking changes to UAPI headers between HEAD and dirty tree...
177 Checking changes to UAPI headers between HEAD^1 and HEAD...
190 Checking changes to UAPI headers between HEAD~2 and HEAD...
240 Checking changes to UAPI headers between HEAD and dirty tree...
287 Checking changes to UAPI headers between HEAD and dirty tree...
333 Checking changes to UAPI headers between HEAD and dirty tree...
341 Checking Historic UAPI Compatibility
[all …]
|
| /Documentation/ABI/testing/ |
| D | sysfs-driver-altera-cvp | 7 error checking in altera-cvp driver is turned on or
|
| D | sysfs-devices-platform-dock | 29 (RO) Show dock station flags, useful for checking if undock
|
| /Documentation/filesystems/ |
| D | ocfs2-online-filecheck.rst | 25 checking/fixing is at the file level, initially for regular files and eventually
32 other components of the filesystem, such as but not limited to, checking if the
53 fixed. Currently, three operations are supported, which includes checking
|
| /Documentation/RCU/ |
| D | lockdep.rst | 4 RCU and lockdep checking
7 All flavors of RCU have lockdep checking available, so that lockdep is
30 checking of rcu_dereference() primitives:
|
| /Documentation/core-api/ |
| D | asm-annotations.rst | 83 Checking tools like ``objtool`` should ensure such marked functions conform
91 Checking tools mostly ignore checking of these functions. But some debug
121 generated object file. Second, it also eases checking and processing such
|
| /Documentation/input/devices/ |
| D | elantech.rst | 25 5.2.1 Parity checking and packet re-synchronization
111 Turns parity checking ON or OFF.
113 By echoing "0" to this file parity checking will be turned OFF. Any
123 data consistency checking can be done. For now checking is disabled by
200 P: 1 = enable parity checking for relative mode
245 when parity checking is enabled (reg_11, P = 1):
266 parity checking enabled (reg_11, P = 1):
395 Parity checking and packet re-synchronization
398 There is no parity checking, however some consistency checks can be performed.
|
| /Documentation/devicetree/bindings/sound/ |
| D | tas5720.txt | 4 serial bus is also used for periodic codec fault checking/reporting during
|
| /Documentation/devicetree/bindings/phy/ |
| D | nuvoton,ma35d1-usb2-phy.yaml | 26 phandle to syscon for checking the PHY clock status.
|
| /Documentation/scsi/ |
| D | dpti.rst | 60 - Added checking underflow conditions
61 - Added DATAPROTECT checking
|
| /Documentation/devicetree/bindings/arm/ |
| D | arm,trace-buffer-extension.yaml | 17 if it is permitted to use the component by checking the
|
| /Documentation/staging/ |
| D | xz.rst | 13 for executable code. CRC32 is supported for integrity checking.
63 Double checking the integrity would probably be waste of CPU cycles.
|
| /Documentation/doc-guide/ |
| D | checktransupdate.rst | 3 Checking for needed translation updates
|
| /Documentation/admin-guide/perf/ |
| D | hns3-pmu.rst | 41 Example usage of checking event code and subevent code::
61 Example usage of checking supported filter mode::
|
| /Documentation/filesystems/xfs/ |
| D | xfs-online-fsck-design.rst | 71 operations internal to the filesystem, such as internal consistency checking
209 metadata to enable targeted checking and repair operations while the system
262 The userspace driver program ``xfs_scrub`` splits the work of checking and
264 Each phase concentrates on checking specific types of scrub items and depends
311 The ability to use hardware-assisted data file integrity checking is new
324 The kernel scrub code uses a three-step strategy for checking and repairing
511 However, doing that is a fair amount more work than what the checking functions
555 Link count checking combines the view deltas and commit step into one because
664 During development of the online checking code, fstests was modified to run
665 ``xfs_scrub -n`` between each test to ensure that the new checking code
[all …]
|
| D | xfs-self-describing-metadata.rst | 80 integrity checking. We cannot trust the metadata if we cannot verify that it has
93 complexity and so there is no provision for changing the integrity checking
162 sibling pointer lists). Hence we still need stateful checking in the main code
175 The first step in read verification is checking the magic number and determining
241 by checking the superblock of the feature bit, and then if the CRC verifies OK
|
| /Documentation/devicetree/bindings/serial/ |
| D | xlnx,opb-uartlite.yaml | 49 Whether parity checking was enabled when the device was configured.
|
| /Documentation/bpf/ |
| D | map_cgroup_storage.rst | 88 // error checking omitted
119 // error checking omitted
|
| /Documentation/i2c/ |
| D | dev-interface.rst | 118 Selects SMBus PEC (packet error checking) generation and verification
196 checking on future transactions.)
203 The i2c-dev driver is responsible for checking all the parameters that
|
| /Documentation/arch/sparc/oradax/ |
| D | dax-hv-api.txt | 374 …access type used in the CCB command. ADI checking only occurs when reading data. When writing data,
377 …An ADI version value of 0 or 0xF indicates the ADI checking is disabled for that data access, even…
379 …also an option to disable ADI checking for all inputs accessed via virtual address for all CCBs su…
383 …uent data chunks may not be detected, so guest software should be careful to use page size checking
386 36.2.1.1.8. Page size checking
389 …are provided using a virtual address, the page size for checking is extracted from the TTE for tha…
484 page size code for the page boundary checking the guest wants
486 (checking is only guaranteed to be performed when using API
575 … page size code for the page boundary checking the guest wants
577 … (checking is only guaranteed to be performed when using API
[all …]
|
| /Documentation/driver-api/firmware/ |
| D | firmware-usage-guidelines.rst | 15 * Firmware files shall be designed in a way that it allows checking for
|
1234567891011