Lines Matching refs:shared

46 the modeling of bare C (or plain) shared memory accesses.  It is meant
53 the basic notions shared by all such models.  People already familiar
87 systems, with multiple CPUs making concurrent accesses to shared
107 and the flag are memory locations shared between the two CPUs.
141 shared memory locations and another CPU loads from those locations in
222 each CPU stores to its own shared location and then loads from the
292 	Read events correspond to loads from shared memory, such as
296 	Write events correspond to stores to shared memory, such as
311 shared memory, do not give rise to events.  Thus, arithmetic and
316 gets stored to a shared memory location (or in the case of an array
369 buf and P0's write event to flag, and similarly for the other shared
372 Since private variables are not shared between CPUs, they can be
485 somehow on a value that doesn't get loaded from shared memory until
561 shared memory, the stores to that location must form a single global
667 another motivation for using READ_ONCE() when accessing shared memory
892 shared location in memory form a global ordering.  We can imagine
1140 we have yet another reason why shared data should always be read with