> if cpu2 gets the lock, then it has seen the "write LOCK_1" from cpu1.
> but this automagically means that it has also seen the "write DATA" from
> cpu1.
Exactly.
A process that try to spin_lock ( == read and set a memory address ) _must_
see
the unlocked value set by the exiting task and hence _must_ see all writes
mades by
the leaving process inside the locked section.
Cheers,
Davide.
-- "Debian, the Freedom in Freedom."
- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.rutgers.edu Please read the FAQ at http://www.tux.org/lkml/