Messages in this thread | | | Subject | memory_barrier | From | Bart De Schuymer <> | Date | Sat, 09 Apr 2005 18:34:56 +0000 |
| |
Hi,
Is there any reason why __memory_barrier() is still referenced in the kernel source?
grep -r memory_barrier gave the following back, which at first seems to suggest barrier() is defined using some phantom __memory_barrier(), quite deceiving...
include/linux/compiler-intel.h:#define barrier() __memory_barrier() include/linux/compiler.h:# define barrier() __memory_barrier() include/asm-m32r/system.h: * memory_barrier() for examples and URLs to more information. include/asm-m32r/system.h: * memory_barrier(); include/asm-m32r/system.h: * memory_barrier(); include/asm-i386/system.h: * memory_barrier() for examples and URLs to more information. include/asm-i386/system.h: * memory_barrier(); include/asm-i386/system.h: * memory_barrier(); include/asm-mips/system.h: * memory_barrier() for examples and URLs to more information. include/asm-mips/system.h: * memory_barrier(); include/asm-mips/system.h: * memory_barrier(); include/asm-ia64/intel_intrin.h:void __memory_barrier(void); include/asm-ia64/intel_intrin.h:#define ia64_barrier() __memory_barrier()
cheers, Bart
- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
| |