On 28/07/2009 06:40, "Juergen Gross" <juergen.gross@xxxxxxxxxxxxxx> wrote:
> BTW: continue_hypercall_on_cpu() exists on x86 only and it isn't really much
> better than my usage of it:
> - remember old pinning state of current vcpu
> - pin it temporarily to the cpu it should continue on
> - continue the hypercall
> - remove temporary pinning
> - re-establish old pinning (if any)
> Pretty much the same as my solution above ;-)
If your solution locks the pinning, as we do already, so that it cannot be
changed while the continue_hypercall_on_cpu() is running, then that is fine.
If it's not locked then it's not safe.
 -- Keir
_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-devel