Lines Matching +full:boot +full:- +full:up

1 # SPDX-License-Identifier: GPL-2.0-only
7 	def_bool (CC_IS_CLANG && $(cc-option,-fsanitize=thread -mllvm -tsan-distinguish-volatile=1)) || \
8 		 (CC_IS_GCC && $(cc-option,-fsanitize=thread --param tsan-distinguish-volatile=1))
11 	  <file:Documentation/dev-tools/kcsan.rst>.
21 	  data-race detector that relies on compile-time instrumentation.
22 	  KCSAN uses a watchpoint-based sampling approach to detect races.
29 	  See <file:Documentation/dev-tools/kcsan.rst> for more details.
34 …def_bool (CC_IS_CLANG && $(cc-option,-fsanitize=thread -mllvm -tsan-compound-read-before-write=1))…
35 		 (CC_IS_GCC && $(cc-option,-fsanitize=thread --param tsan-compound-read-before-write=1))
37 	  The compiler instruments plain compound read-write operations
38 	  differently (++, --, +=, -=, |=, &=, etc.), which allows KCSAN to
56 	bool "Perform short selftests on boot"
59 	  Run KCSAN selftests on boot. On test failure, causes the kernel to
74 	  Each test case may run at least up to KCSAN_REPORT_ONCE_IN_MS
80 	  during boot; say M if you want the test to build as a module; say N
84 	bool "Early enable during boot"
98 	  due to reducing cache-line contention. The chosen default is a
106 	  For tasks, the microsecond delay after setting up a watchpoint.
112 	  For interrupts, the microsecond delay after setting up a watchpoint.
125 	int "Skip instructions before setting up watchpoint"
128 	  The number of per-CPU memory operations to skip, before another
129 	  watchpoint is set up, i.e. one in KCSAN_SKIP_WATCH per-CPU
130 	  memory operations are used to set up a watchpoint. A smaller value
146 	  If enabled, a task that set up a watchpoint may be interrupted while
150 	  Currently disabled by default, because not all safe per-CPU access
165 # are not expected to be switched frequently by non-testers or at runtime.
178 	bool "Strict data-race checking"
181 	  closely aligns with the rules defined by the Linux-kernel memory
216 	bool "Assume that plain aligned writes up to word size are atomic"
220 	  Assume that plain aligned writes up to word size are atomic by
224 	  writes up to word size: conflicts between marked reads and plain
225 	  aligned writes up to word size will not be reported as data races;
254 	  to further reduce reported data races due to data-racy patterns