Lines Matching full:reads

67 2.	Data-racy reads whose values are checked against marked reload.
69 3.	Reads whose values feed into error-tolerant heuristics.
74 Data-Racy Reads for Approximate Diagnostics
78 values are ignored, and other situations where reads from shared variables
82 reads can enable better checking of the remaining accesses implementing
84 prevents any non-diagnostic reads from shared variable x from running
86 to x allows KCSAN to detect reads from x from within regions of code
88 data_race() for the diagnostic reads because otherwise KCSAN would give
89 false-positive warnings about these diagnostic reads.
101 Data-Racy Reads That Are Checked Against Marked Reload
103 The values from some reads are not implicitly trusted.  They are instead
125 Reads Feeding Into Error-Tolerant Heuristics
127 Values from some reads feed into heuristics that can tolerate occasional
128 errors.  Such reads can use data_race(), thus allowing KCSAN to focus on
152 due to compiler-mangled reads, it can also tolerate the occasional
224 to be concurrent reads from foo from other CPUs, it is an error for some
283 reads from or updates to foo.  The data_race() in read_foo_diagnostic()
318 Lock-Protected Writes With Lockless Reads
348 Lock-Protected Writes With Heuristic Lockless Reads
441 Lockless Reads and Writes
467 flag any concurrent plain C-language reads from foo, and given
472 Lockless Reads and Writes, But With Single-Threaded Initialization
512 reads, and the ASSERT_EXCLUSIVE_ACCESS() call further allows KCSAN to