On Tue, Nov 28, 2006 at 10:47:31AM -0500, Jimi Xenidis wrote:
> On Nov 28, 2006, at 1:37 AM, Amos Waterland wrote:
> > The compiler is not told that read_clocks_cpumask is volatile, so it
> > is free to turn that loop into an infinite loop, as my gcc 4.1.1
> > cross-compiler does. I am surprised that other Xen architectures
> > have not seen the same problem.
> Found it, cpu_relax() is supposed to contain barrier() call.
> My fault but it coulda been hollis :)
> you _always_ have to wait for call_data.started it means that its
> safe to reuse call_data.
Yes, I know :) I only did that as a crude approximation, the proper
solution (pending your design comments), is not serializing do_external
with a lock (see the next patch I sent).
Xen-ppc-devel mailing list