Home
last modified time | relevance | path

Searched full:checking (Results 1 – 25 of 2352) sorted by relevance

12345678910>>...95

/linux-6.12.1/tools/perf/tests/shell/lib/
Dstat_output.sh13 echo -n "Checking $1 output: no args "
21 echo -n "Checking $1 output: system wide "
34 echo -n "Checking $1 output: system wide no aggregation "
47 echo -n "Checking $1 output: interval "
55 echo -n "Checking $1 output: event "
63 echo -n "Checking $1 output: per core "
76 echo -n "Checking $1 output: per thread "
89 echo -n "Checking $1 output: per cache instance "
102 echo -n "Checking $1 output: per cluster "
114 echo -n "Checking $1 output: per die "
[all …]
/linux-6.12.1/tools/perf/tests/shell/
Dstat+json_output.sh38 echo -n "Checking json output: no args "
46 echo -n "Checking json output: system wide "
59 echo -n "Checking json output: system wide no aggregation "
72 echo -n "Checking json output: interval "
81 echo -n "Checking json output: event "
89 echo -n "Checking json output: per core "
102 echo -n "Checking json output: per thread "
115 echo -n "Checking json output: per cache_instance "
127 echo -n "Checking json output: per cluster "
139 echo -n "Checking json output: per die "
[all …]
/linux-6.12.1/lib/
DKconfig.ubsan58 bool "Perform array index bounds checking"
90 bool "Perform checking for bit-shift overflows"
98 bool "Perform checking for integer divide-by-zero"
110 bool "Perform checking for unreachable code"
111 # objtool already handles unreachable checking and gets angry about
120 bool "Perform checking for signed arithmetic wrap-around"
132 sanitizer versions will allow for wrap-around checking (rather than
136 bool "Perform checking for non-boolean values used as boolean"
144 bool "Perform checking for out of bounds enum values"
152 bool "Perform checking for misaligned pointer usage"
/linux-6.12.1/tools/testing/selftests/pstore/
Dpstore_post_reboot_tests40 prlog -n "Checking dmesg files exist in pstore filesystem ... "
43 prlog -n "Checking console files exist in pstore filesystem ... "
46 prlog -n "Checking pmsg files exist in pstore filesystem ... "
49 prlog -n "Checking dmesg files contain oops end marker"
56 prlog -n "Checking console file contains oops end marker ... "
60 prlog -n "Checking pmsg file properly keeps the content written before crash ... "
Dpstore_tests12 prlog -n "Checking pstore console is registered ... "
16 prlog -n "Checking /dev/pmsg0 exists ... "
/linux-6.12.1/Documentation/arch/arm64/
Dmemory-tagging-extension.rst95 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 …]
/linux-6.12.1/tools/testing/kunit/test_data/
Dtest_is_test_passed-no_tests_run_no_header.log4 Checking environment variables for a tempdir...none found
5 Checking if /dev/shm is on tmpfs...OK
6 Checking PROT_EXEC mmap in /dev/shm...OK
22 Checking that host ptys support output SIGIO...Yes
23 Checking that host ptys support SIGIO on close...No, enabling workaround
30 Checking host MADV_REMOVE support...OK
/linux-6.12.1/tools/lib/perf/include/internal/
Drc_check.h9 * Enable reference count checking implicitly with leak checking, which is
21 * Shared reference count checking macros.
23 * Reference count checking is an approach to sanitizing the use of reference
25 * are paired with a put. Reference count checking adds a malloc-ed layer of
/linux-6.12.1/tools/testing/selftests/x86/
Dsyscall_numbering.c231 run("Checking for x32 by calling x32 getpid()\n"); in test_x32()
253 run("Checking some common syscalls as 64 bit\n"); in test_syscalls_common()
257 run("Checking some 64-bit only syscalls as 64 bit\n"); in test_syscalls_common()
261 run("Checking out of range system calls\n"); in test_syscalls_common()
280 run("Checking x32 syscalls as 64 bit\n"); in test_syscalls_with_x32()
283 run("Checking some common syscalls as x32\n"); in test_syscalls_with_x32()
287 run("Checking some x32 syscalls as x32\n"); in test_syscalls_with_x32()
291 run("Checking some 64-bit syscalls as x32\n"); in test_syscalls_with_x32()
299 run("Checking for absence of x32 system calls\n"); in test_syscalls_without_x32()
318 run("Checking system calls with msb = %d (0x%x)\n", in test_syscall_numbering()
/linux-6.12.1/fs/
Dattr.c90 * take care to map the inode according to @idmap before checking
91 * permissions. On non-idmapped mounts or if permission checking is to be
117 * take care to map the inode according to @idmap before checking
118 * permissions. On non-idmapped mounts or if permission checking is to be
154 * take care to map the inode according to @idmap before checking
155 * permissions. On non-idmapped mounts or if permission checking is to be
291 * take care to map the inode according to @idmap before checking
292 * permissions. On non-idmapped mounts or if permission checking is to be
373 * take care to map the inode according to @idmap before checking
374 * permissions. On non-idmapped mounts or if permission checking is to be
[all …]
/linux-6.12.1/Documentation/dev-tools/
Dtesting-overview.rst107 * 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
Dcheckuapi.rst78 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 …]
/linux-6.12.1/drivers/staging/octeon/
Dethernet-rgmii.c30 /* Set preamble checking. */ in cvm_oct_set_hw_preamble()
83 * disable preamble checking and do it in software. in cvm_oct_check_preamble_errors()
92 * enable preamble checking, FCS stripping, and clear error in cvm_oct_check_preamble_errors()
143 * preamble error checking, and we also need to call this in cvm_oct_rgmii_open()
/linux-6.12.1/include/linux/
Dpmbus.h18 * During register detection, skip checking the status register for
22 * register. For such chips, checking the status register is mandatory when
25 * communication errors for no explicable reason. For such chips, checking
Dfortify-string.h130 * unsafe_memcpy - memcpy implementation with no FORTIFY bounds checking
140 * checking has happened, and why existing solutions cannot be employed.
469 * can perform compile-time bounds checking where in fortify_memset_chk()
484 * so run-time bounds checking can be done where buffer sizes are in fortify_memset_chk()
521 * (e.g. see struct sk_buff.) Read overflow checking is currently only
525 * Bounds checking at:
540 * y = perform deterministic compile-time bounds checking
541 * n = cannot perform deterministic compile-time bounds checking
542 * n/a = no run-time bounds checking needed since compile-time deterministic
543 * B = can perform run-time bounds checking (currently unimplemented)
[all …]
/linux-6.12.1/tools/testing/selftests/bpf/map_tests/
Darray_map_batch_ops.c53 "key/value checking", in map_batch_verify()
58 CHECK(keys[i] + 1 != values[i], "key/value checking", in map_batch_verify()
65 CHECK(visited[i] != 1, "visited checking", in map_batch_verify()
160 CHECK(nr_cpus < 0, "nr_cpus checking", in test_array_map_batch_ops()
/linux-6.12.1/kernel/configs/
Dhardening.config38 # Basic buffer length bounds checking.
42 # Basic array index bounds checking.
57 # Linked list integrity checking.
/linux-6.12.1/arch/mips/include/asm/sn/sn0/
Dhubpi.h55 /* Processor control and status checking */
68 /* Regular Interrupt register checking. */
154 #define PI_SYSAD_ERRCHK_EN 0x000490 /* Enables SYSAD error checking */
368 #define PI_SYSAD_ERRCHK_SADP 0x04 /* Enable SysAD parity checking */
369 #define PI_SYSAD_ERRCHK_CMDP 0x08 /* Enable SysCmd parity checking */
370 #define PI_SYSAD_ERRCHK_STATE 0x10 /* Enable SysState parity checking */
371 #define PI_SYSAD_ERRCHK_QUAL 0x20 /* Enable data quality checking */
/linux-6.12.1/mm/
DKconfig.debug130 erroneously shared. Since the checking is performed at the time
137 bool "Enforce the page table checking by default"
140 Always enable page table checking. By default the page table checking
160 checking the poison pattern on alloc, you can boot the kernel with
/linux-6.12.1/drivers/thermal/broadcom/
DKconfig31 Management Unit) block with a thermal sensor that allows checking CPU
40 iHost, CRMU and NITRO has thermal sensor that allows checking its
/linux-6.12.1/scripts/dtc/libfdt/
Dlibfdt_internal.h71 /* Checking controls */
119 * assumption. This includes checking headers, tags and the like.
127 * extensive checking of parameters and the device tree, making various
189 /** helper macros for checking assumptions */
/linux-6.12.1/Documentation/input/devices/
Delantech.rst25 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.
/linux-6.12.1/arch/riscv/mm/
Dphysaddr.c12 * Boundary checking aginst the kernel linear mapping space. in __virt_to_phys()
28 * Boundary checking aginst the kernel image mapping. in __phys_addr_symbol()
/linux-6.12.1/Documentation/filesystems/
Docfs2-online-filecheck.rst25 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
/linux-6.12.1/block/
Ddisk-events.c59 * disk_block_events - block and flush disk event checking
62 * On return from this function, it is guaranteed that event checking
67 * Note that this intentionally does not block event checking from
124 * disk_unblock_events - unblock disk event checking
140 * disk_flush_events - schedule immediate event checking and flushing
144 * Schedule immediate event checking on @disk if not blocked. Events in

12345678910>>...95