On Thursday, January 28, 2016 07:45:53 AM Viresh Kumar wrote: > On 27-01-16, 23:54, Rafael J. Wysocki wrote: > > So I've applied this, but I'm not sure it is sufficient yet. > > At least, this solves the crash Juri was hitting on a multi cluster > box. Yes, it makes the crash go away in his setup. > > Have you double checked whether or not stuff cannot be reordered by > > the CPU and/or the compiler and no additional memory barriers are needed? > > I don't think CPU will reorder things before a function call. It can do that in theory. First of all, functions may be inlined by the compiler. Second, even if they aren't, the call instruction only means "take the next instruction from that other location in memory" to the CPU and the instructions following the call go into the pipeline along with the ones preceding it and they may be reordered in the process. > It can reorder lines, Not lines, but instructions. > which CPU thinks aren't related but it can't assume the > same in this case. We have tons of code like this. Code that relies on specific ordering of instructions executed by different CPUs for correctness usually requires memory barriers. Thanks, Rafael -- To unsubscribe from this list: send the line "unsubscribe stable" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html