[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [Qemu-devel] [PATCH v1 4/5] kvm/x86: Hyper-V VMBus hypercall userspa
From: |
Paolo Bonzini |
Subject: |
Re: [Qemu-devel] [PATCH v1 4/5] kvm/x86: Hyper-V VMBus hypercall userspace exit |
Date: |
Wed, 20 Jan 2016 14:59:08 +0100 |
User-agent: |
Mozilla/5.0 (X11; Linux x86_64; rv:38.0) Gecko/20100101 Thunderbird/38.5.0 |
On 14/01/2016 09:30, Pavel Fedin wrote:
> Hello!
>
>> --- a/Documentation/virtual/kvm/api.txt
>> +++ b/Documentation/virtual/kvm/api.txt
>> @@ -3359,6 +3359,14 @@ Hyper-V SynIC state change. Notification is used to
>> remap SynIC
>> event/message pages and to enable/disable SynIC messages/events processing
>> in userspace.
>>
>> + /* KVM_EXIT_HYPERV_HCALL */
>> + struct {
>> + __u64 input;
>> + __u64 params[2];
>> + __u64 result;
>> + } hv_hcall;
>> +Indicates that the VCPU exits into userspace to process some guest
>> +Hyper-V hypercalls.
>
> Why introducing this? We already have KVM_EXIT_HYPERCALL, which is
> exactly the same. AFAIK it's not used at the moment.
> Additionally, in theory we could have hypercalls handled in
> userspace for something else except HyperV. And not only for x86.
Because, as the docs say, we don't want to do that. We want to use
KVM_EXIT_IO or KVM_EXIT_MMIO, with two exceptions: s390 and wherever we
can't do that for compatibility purposes. This is the latter. So we
should not add a new exit (I suggested elsewhere the existing hyper-v
exit) but we shouldn't use KVM_EXIT_HYPERCALL either.
There is a precedent in fact of using "something else than
KVM_EXIT_HYPERCALL" for interoperability/compatibility hypercalls,
namely KVM_EXIT_PAPR_HCALL.
Paolo
- [Qemu-devel] [PATCH v1 3/5] kvm/x86: Pass return code of kvm_emulate_hypercall, (continued)
- [Qemu-devel] [PATCH v1 3/5] kvm/x86: Pass return code of kvm_emulate_hypercall, Andrey Smetanin, 2016/01/12
- [Qemu-devel] [PATCH v1 1/5] kvm/x86: Rename Hyper-V long spin wait hypercall, Andrey Smetanin, 2016/01/12
- [Qemu-devel] [PATCH v1 2/5] drivers/hv: Move VMBus hypercall codes into Hyper-V UAPI header, Andrey Smetanin, 2016/01/12
- [Qemu-devel] [PATCH v1 5/5] kvm/x86: Reject Hyper-V hypercall continuation, Andrey Smetanin, 2016/01/12
- [Qemu-devel] [PATCH v1 4/5] kvm/x86: Hyper-V VMBus hypercall userspace exit, Andrey Smetanin, 2016/01/12
- Re: [Qemu-devel] [PATCH v1 4/5] kvm/x86: Hyper-V VMBus hypercall userspace exit,
Paolo Bonzini <=
- Re: [Qemu-devel] [PATCH v1 4/5] kvm/x86: Hyper-V VMBus hypercall userspace exit, Pavel Fedin, 2016/01/20
- Re: [Qemu-devel] [PATCH v1 4/5] kvm/x86: Hyper-V VMBus hypercall userspace exit, 'Roman Kagan', 2016/01/20
- Re: [Qemu-devel] [PATCH v1 4/5] kvm/x86: Hyper-V VMBus hypercall userspace exit, Paolo Bonzini, 2016/01/20
- Re: [Qemu-devel] [PATCH v1 4/5] kvm/x86: Hyper-V VMBus hypercall userspace exit, 'Roman Kagan', 2016/01/20
- Re: [Qemu-devel] [PATCH v1 4/5] kvm/x86: Hyper-V VMBus hypercall userspace exit, Paolo Bonzini, 2016/01/20
Re: [Qemu-devel] [PATCH v1 4/5] kvm/x86: Hyper-V VMBus hypercall userspace exit, Paolo Bonzini, 2016/01/20
Re: [Qemu-devel] [PATCH v1 0/5] KVM: Hyper-V VMBus hypercalls, Andrey Smetanin, 2016/01/12
Re: [Qemu-devel] [PATCH v1 0/5] KVM: Hyper-V VMBus hypercalls, Denis V. Lunev, 2016/01/19