Lines Matching full:concurrent

4 This document provides guidelines for marking intentionally concurrent
183 5.	Any other loads for which there is not supposed to be a concurrent
186 6.	Any other stores for which there should be neither concurrent
187 	loads nor concurrent stores to that same variable.
221 concurrent access to variable foo by any other CPU is an error, even
222 if that concurrent access is marked with READ_ONCE().  In addition,
224 to be concurrent reads from foo from other CPUs, it is an error for some
225 other CPU to be concurrently writing to foo, even if that concurrent
238 your concurrent algorithm, to help the human reader, and to inform
345 concurrent lockless write.
466 there really can be concurrent lockless writers.  KCSAN would
467 flag any concurrent plain C-language reads from foo, and given
468 CONFIG_KCSAN_ASSUME_PLAIN_WRITES_ATOMIC=n, also any concurrent plain
510 are not supposed to be concurrent accesses during initialization.  The
511 ASSERT_EXCLUSIVE_ACCESS() allows KCSAN to flag buggy concurrent unmarked
513 flag buggy concurrent writes, even if:  (1) Those writes are marked or