Re: 4.x -> 5.x locking?

[Mouse <mouse%Rodents-Montreal.ORG@localhost>]

>> Does mutex_exit also implicitly push writes to main RAM, or whatever
>> else is necessary to make them visible to other CPUs?
> I don't think it guarantees it by itself.  That is, if you want to
> access the data on a different CPU, you either need to take the mutex
> (and the read barrier in mutex_enter) or issue an explicit barrier.

Yes, I got slightly careless.  I should have said, mutex_exit on the
writing CPU plus mutex_enter on the reading CPU.

/~\ The ASCII                             Mouse
\ / Ribbon Campaign
 X  Against HTML                mouse%rodents-montreal.org@localhost
/ \ Email!           7D C8 61 52 5D E7 2D 39  4E F1 31 3E E8 B3 27 4B