On 21.11.2008, at 18:18, Avi Kivity <[EMAIL PROTECTED]> wrote:

Alexander Graf wrote:

Yeah. We could move some of these out, and emulate the rest (ltr I think is needed).

Then older versions of kvm would still break

If emulation fails, go back to virtualization. Or am I missing something?


Yes, and exactly that part broke for me too. I just gave up at one point.


That's what kvm_x86_ops is for. We already emulate vendor specific instructions (vmcall and vmmcall).

From what I can tell kvm_x86_ops tries to multiplex calls that happen to be different on svm/vmx, but existent on both. SVM instructions usually don't appear on VMX ;-).

Right. But so what? I don't want to lose any future improvements the emulator may have (like traps on debug register, etc).

Hum, makes sense.




--
I have a truly marvellous patch that fixes the bug which this
signature is too narrow to contain.

--
To unsubscribe from this list: send the line "unsubscribe kvm" in
the body of a message to [EMAIL PROTECTED]
More majordomo info at  http://vger.kernel.org/majordomo-info.html

Reply via email to