Lines Matching refs:general
415 A general memory barrier gives a guarantee that all the LOAD and STORE
420 A general memory barrier is a partial ordering over both loads and stores.
832 including of course general barriers. A write barrier pairs with a data
834 barrier, a read barrier, or a general barrier. Similarly a read barrier,
836 barrier, an acquire barrier, a release barrier, or a general barrier:
861 <general barrier>
1264 <general barrier> <general barrier>
1279 In the Linux kernel, use of general memory barriers guarantees
1285 For example, suppose that CPU 2's general barrier in the above example
1292 <read barrier> <general barrier>
1306 To reiterate, if your code requires transitivity, use general barriers
1332 This is a general barrier -- there are no read-read or write-write variants
1972 A general memory barrier is interpolated automatically by set_current_state()
1980 <general barrier>
1988 which therefore also imply a general memory barrier after setting the state.
2021 <general barrier> STORE current->state
2341 The way to deal with this is to insert a general SMP memory barrier:
2371 about the state (old or new) implies an SMP-conditional general memory barrier
2474 so for _all_ general drivers locks should be used and mmiowb() must be