Lines Matching full:accesses

1 MARKING SHARED-MEMORY ACCESSES
5 normal accesses to shared memory, that is "normal" as in accesses that do
7 document these accesses, both with comments and with special assertions
18 1.	Plain C-language accesses (unmarked), for example, "a = b;"
39 Neither plain C-language accesses nor data_race() (#1 and #2 above) place
46 C-language accesses.  It is permissible to combine #2 and #3, for example,
51 C-language accesses, but marking all accesses involved in a given data
60 data_race() and even plain C-language accesses is preferable to
88 reads can enable better checking of the remaining accesses implementing
135 the other accesses to the relevant shared variables.  But please note
169 Use of Plain C-Language Accesses
172 Here are some example situations where plain C-language accesses should
175 1.	Accesses protected by mutual exclusion, including strict locking
178 2.	Initialization-time and cleanup-time accesses.	This covers a
209 Note that it is important to use plain C-language accesses in these cases,
218 causes KCSAN to treat all accesses to that variable as if they were
234 It is important to comment marked accesses so that people reading your
236 However, it is even more important to comment plain C-language accesses
239 of how the compiler has been prevented from optimizing those accesses
303 the accesses to foo within both update_foo() and read_foo() can (and
304 should) be plain C-language accesses.  One benefit of making them be
305 plain C-language accesses is that KCSAN can detect any erroneous lockless
319 Alternatively, given that KCSAN is to ignore all accesses in this function,
338 conditionally trap on accesses.
366 Because foo is read locklessly, all accesses are marked.  The purpose
487 Because foo is accessed locklessly, all accesses are marked.  It does
533 are not supposed to be concurrent accesses during initialization.  The