Anthony Liguori wrote:
> This patch refactors the current hypercall infrastructure to better support
> live
> migration and SMP. It eliminates the hypercall page by trapping the UD
> exception that would occur if you used the wrong hypercall instruction for the
> underlying architecture and replacing it with the right one lazily.
>
> It also introduces the infrastructure to probe for hypercall available via
> CPUID leaves 0x40000002 and 0x40000003.
>
> A fall-out of this patch is that the unhandled hypercalls no longer trap to
> userspace. There is very little reason though to use a hypercall to
> communicate
> with userspace as PIO or MMIO can be used. There is no code in tree that uses
> userspace hypercalls.
>
>
Allowing userspace to handle hypercalls means that we can have block and
net drivers in the kernel or userspace, reflecting user privileges and
performance/flxibility tradeoffs. I think that's an important feature
to have.
> void kvm_emulate_cpuid(struct kvm_vcpu *vcpu)
> {
> int i;
> @@ -1632,6 +1575,12 @@ void kvm_emulate_cpuid(struct kvm_vcpu *vcpu)
> vcpu->regs[VCPU_REGS_RBX] = 0;
> vcpu->regs[VCPU_REGS_RCX] = 0;
> vcpu->regs[VCPU_REGS_RDX] = 0;
> +
> + if ((function & 0xFFFF0000) == 0x40000000) {
> + emulate_paravirt_cpuid(vcpu, function);
> + goto out;
> + }
> +
>
Hmm. Suppose we expose kvm capabilities to host userspace instead, and
let the host userspace decide which features to expose to the guest via
the regular cpuid emulation? That allows the qemu command line to
control the feature set.
>
> +static int ud_interception(struct vcpu_svm *svm, struct kvm_run *kvm_run)
> +{
> + int er;
> +
> + er = emulate_instruction(&svm->vcpu, kvm_run, 0, 0);
> +
> + /* we should only succeed here in the case of hypercalls which
> + cannot generate an MMIO event. MMIO means that the emulator
> + is mistakenly allowing an instruction that should generate
> + a UD fault so it's a bug. */
> + BUG_ON(er == EMULATE_DO_MMIO);
>
It's a guest-triggerable bug; one vcpu can be issuing ud2-in-a-loop
while the other replaces the instruction with something that does mmio.
> +
> +#define KVM_ENOSYS ENOSYS
>
A real number (well, an integer, not a real) here please. I know that
ENOSYS isn't going to change soon, but this file defines the kvm abi and
I'd like it to be as independent as possible.
Let's start it at 1000 so that spurious "return 1"s or "return -1"s
don't get translated into valid error numbers.
I really like the simplification to the guest/host interface that this
patch brings.
--
Any sufficiently difficult bug is indistinguishable from a feature.
-------------------------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc.
Still grepping through log files to find problems? Stop.
Now Search log events and configuration files using AJAX and a browser.
Download your FREE copy of Splunk now >> http://get.splunk.com/
_______________________________________________
kvm-devel mailing list
kvm-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/kvm-devel
