Home
last modified time | relevance | path

Searched refs:checks (Results 1 – 25 of 236) sorted by relevance

12345678910

/linux/scripts/clang-tools/
H A Drun-clang-tools.py54 checks = None
55 if args.checks:
56 checks = args.checks.split(',')
58 checks = ["-*"]
60 checks.append("linuxkernel-*")
62 checks.append("clang-analyzer-*")
63 checks.append("-clang-analyzer-security.insecureAPI.DeprecatedOrUnsafeBufferHandling")
69 pargs = ["clang-tidy", "-p", args.path, "-checks=" + ",".join(checks)]
/linux/Documentation/virt/kvm/x86/
H A Dcpuid.rst65 KVM_FEATURE_PV_UNHALT 7 guest checks this feature bit
69 KVM_FEATURE_PV_TLB_FLUSH 9 guest checks this feature bit
77 KVM_FEATURE_PV_SEND_IPI 11 guest checks this feature bit
85 KVM_FEATURE_PV_SCHED_YIELD 13 guest checks this feature bit
89 KVM_FEATURE_ASYNC_PF_INT 14 guest checks this feature bit
95 KVM_FEATURE_MSI_EXT_DEST_ID 15 guest checks this feature bit
99 KVM_FEATURE_HC_MAP_GPA_RANGE 16 guest checks this feature bit before
103 KVM_FEATURE_MIGRATION_CONTROL 17 guest checks this feature bit before
120 KVM_HINTS_REALTIME 0 guest checks this feature bit to
/linux/tools/perf/tests/shell/lib/
H A Dperf_json_output_lint.py50 checks = {
91 if key not in checks:
95 if not checks[key](value):
/linux/arch/parisc/
H A DKconfig.debug4 bool "Enable lightweight spinlock checks"
8 Add checks with low performance impact to the spinlock functions
/linux/tools/net/ynl/pyynl/
H A Dynl_gen_c.py67 self.checks = attr.get('checks', {})
121 value = self.checks.get(limit, default)
131 value = self.checks.get(limit, default)
153 if self.checks != self._get_real_attr().checks:
154 raise Exception("Overriding checks not supported by codegen, yet")
381 # computing checks, since we only need them for kernel policies
413 self.checks['sparse'] = True
415 if 'min' not in self.checks
[all...]
/linux/tools/testing/memblock/
H A DREADME16 consist of a series of checks that exercise both the basic operations and
18 memory allocator is initialized at the build time, so the checks here reuse its
57 The project has one target, main, which calls a group of checks for basic and
95 (...allocation checks...)
/linux/Documentation/arch/x86/x86_64/
H A Dmachinecheck.rst7 Machine checks report internal hardware error conditions detected
11 Machine checks are organized in banks (normally associated with
/linux/lib/
H A DKconfig.ubsan93 This option enables -fsanitize=shift which checks for bit-shift
104 This option enables -fsanitize=integer-divide-by-zero which checks
116 This option enables -fsanitize=unreachable which checks for control
142 This option enables -fsanitize=bool which checks for boolean values being
150 This option enables -fsanitize=enum which checks for values being loaded
/linux/fs/btrfs/
H A DKconfig67 Additional potentially expensive checks, debugging functionality or
68 sysfs exported information is enabled, like leak checks of internal
78 Enable run-time assertion checking. Additional safety checks are
/linux/Documentation/dev-tools/
H A Dtesting-overview.rst134 Smatch extends Sparse and provides additional checks for programming logic
144 available include API tests, tests for correct usage of kernel iterators, checks
164 It's generally easier to write checks in Smatch than it is to write checks in
165 Sparse. Nevertheless, there are some overlaps between Sparse and Smatch checks.
170 Coccinelle is probably the easiest for writing checks. It works before the
H A Dkasan.rst53 Software KASAN modes use compile-time instrumentation to insert validity checks
56 these checks but still requires a compiler version that supports the memory
141 register for arm64). The kernel periodically checks the hardware and
142 only reports tag faults during these checks.
147 checks the write (store) accesses only or all accesses (default: ``off``).
158 Note that enabling this parameter makes Hardware Tag-Based KASAN skip checks
312 checks before each memory access.
329 Compile-time instrumentation is used to insert memory access checks. Compiler
357 Software Tag-Based KASAN uses compile-time instrumentation to insert checks
358 before each memory access. These checks make sure that the tag of the memory
[all …]
/linux/kernel/rcu/
H A DKconfig.debug64 and bh-disabled checks are to take effect, and that PREEMPT_RCU
65 must be enabled for the RCU-nesting checks to take effect.
66 These checks add overhead, and this Kconfig options is therefore
194 This option provides consistency checks in RCU's handling of
195 NO_HZ. These checks have proven quite helpful in detecting
/linux/lib/kunit/
H A Dassert_test.c123 va_list checks; in validate_assert() local
127 va_start(checks, num_checks); in validate_assert()
132 cur_substr_exp = va_arg(checks, char *); in validate_assert()
/linux/Documentation/filesystems/ext4/
H A Dmmp.rst9 etc.), the MMP code running on the node (call it node A) checks a
16 code passes all of those checks, a new MMP sequence number is generated
/linux/fs/ocfs2/
H A DKconfig73 bool "OCFS2 expensive checks"
77 This option will enable expensive consistency checks. Enable
/linux/kernel/liveupdate/
H A DKconfig21 bool "Enable Kexec Handover debug checks"
24 This option enables extra sanity checks for the Kexec Handover
/linux/fs/xfs/
H A DKconfig199 It converts ASSERT checks to WARN, so will log any out-of-bounds
212 including ASSERT checks, function wrappers around macros,
221 bool "XFS expensive debugging checks"
224 Say Y here to get an XFS build with expensive debugging checks
225 enabled. These checks may affect performance significantly.
/linux/Documentation/staging/
H A Dspeculation.rst21 checks to be ignored by code which is speculatively executed. Consider the
69 The kernel provides a generic API to ensure that bounds checks are
/linux/drivers/iommu/generic_pt/
H A DKconfig13 bool "Extra debugging checks for GENERIC_PT"
15 Enable extra run time debugging checks for GENERIC_PT code. This
/linux/drivers/gpib/
H A DTODO3 These checks should be ignored:
/linux/Documentation/admin-guide/blockdev/drbd/
H A Dconn-states-8.dot5 WFReportParams -> StandAllone [ label = "checks in receive_param()" ]
/linux/drivers/firmware/psci/
H A DKconfig9 Run the PSCI checker during startup. This checks that hotplug and
/linux/Documentation/filesystems/xfs/
H A Dxfs-self-describing-metadata.rst51 not detected by automated verification checks) but are not correct. Finding and
89 fast. So while CRC32c is not the strongest of possible integrity checks that
178 further checks are made against the location information, followed by extensive
179 object specific metadata validation. If any of these checks fail, then the
267 /* object specific verification checks here */
292 /* object specific verification checks here */
339 verification checks are done when each inode is read from or written back to the
342 The structure of the verifiers and the identifiers checks is very similar to the
/linux/Documentation/tools/rv/
H A Drv-mon-wip.rst21 checks if the wakeup events always take place with preemption disabled.
/linux/scripts/dtc/
H A DMakefile9 srcpos.o checks.o util.o

12345678910