On Thu, Mar 26, 2015 at 05:36:47PM +0100, Peter Zijlstra wrote: > Can't we make an argument that these barrier calls are not required? The > memcpy() call already guarantees we emit the loads and its opaque so the > compiler cannot 'cache' the value. So I see not immediate reason for the > dual memory clobber. Oh wait, it needs to reassess the content of the target variable after the memcpy of course. Could we then at least make the 64bit case unconditional as well? -- To unsubscribe from this list: send the line "unsubscribe linux-next" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
