Lines Matching full:concurrent

4 This document provides guidelines for marking intentionally concurrent
189 5.	Any other loads for which there is not supposed to be a concurrent
192 6.	Any other stores for which there should be neither concurrent
193 	loads nor concurrent stores to that same variable.
244 concurrent access to variable foo by any other CPU is an error, even
245 if that concurrent access is marked with READ_ONCE().  In addition,
247 to be concurrent reads from foo from other CPUs, it is an error for some
248 other CPU to be concurrently writing to foo, even if that concurrent
261 your concurrent algorithm, to help the human reader, and to inform
368 concurrent write, whether marked or not.
489 there really can be concurrent lockless writers.  KCSAN would
490 flag any concurrent plain C-language reads from foo, and given
491 CONFIG_KCSAN_ASSUME_PLAIN_WRITES_ATOMIC=n, also any concurrent plain
533 are not supposed to be concurrent accesses during initialization.  The
534 ASSERT_EXCLUSIVE_ACCESS() allows KCSAN to flag buggy concurrent unmarked
536 flag buggy concurrent writes, even if:  (1) Those writes are marked or