Anthony Liguori wrote:
quoted text
> The whole point of using the instruction is to allow hypercalls to be
> used in many locations.  This has the nice side effect of not
> requiring a central hypercall initialization routine in the guest to
> fetch the hypercall page.  A PV driver can be completely independent
> of any other code provided that it restricts itself to it's hypercall
> namespace.

I see.  So you take the fault, disassemble the instruction, see that its
another CPU's vmcall instruction, and then replace it with the current
CPU's vmcall?

quoted text
> Xen is currently using 0/1/2.  I had thought it was only using 0/1. 
> The intention was not to squash Xen's current CPUID usage so that it
> would still be possible for Xen to make use of the guest code.  Can we
> agree that Xen won't squash leaves 3/4 or is it not worth trying to be
> compatible at this point?

No, the point is that you're supposed to work out which hypervisor it is
from the signature in leaf 0, and then the hypervisor can put anything
it wants in the other leaves.

    J
-
unsubscribe notice
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/