> > When you are implementing the locking primitives on a new platform. When > > you are implementing the I/O and atomic prmitives on a new platform. Also > > in inline gcc assembler where "volatile" is used for subtly different > > purposes. > > Is there a good reason for using volatile in atomic/locking primitives? > AFAIKS there is not.
Depends on the platform. If you are writing a new architecture then who knows what you will need to get the barriers right - you may want to use volatile, you may want to use asm. - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
