On 21/01/2016 15:04, Andrey Smetanin wrote: > Add Hyper-V VMBus hypercalls blank handlers which > just returns error code - HV_STATUS_INVALID_HYPERCALL_CODE. > > Changes v2: > * use KVM_EXIT_HYPERV exit type > > Signed-off-by: Andrey Smetanin <[email protected]> > Reviewed-by: Roman Kagan <[email protected]> > CC: Paolo Bonzini <[email protected]> > CC: Richard Henderson <[email protected]> > CC: Eduardo Habkost <[email protected]> > CC: "Andreas Färber" <[email protected]> > CC: Marcelo Tosatti <[email protected]> > CC: Roman Kagan <[email protected]> > CC: Denis V. Lunev <[email protected]> > CC: [email protected] > > --- > target-i386/hyperv.c | 12 ++++++++++++ > 1 file changed, 12 insertions(+) > > diff --git a/target-i386/hyperv.c b/target-i386/hyperv.c > index e79b173..d3f3059 100644 > --- a/target-i386/hyperv.c > +++ b/target-i386/hyperv.c > @@ -43,6 +43,18 @@ int kvm_hv_handle_exit(X86CPU *cpu, struct kvm_hyperv_exit > *exit) > return -1; > } > return 0; > + case KVM_EXIT_HYPERV_HCALL: { > + uint16_t code; > + > + code = exit->u.hcall.input & 0xffff; > + switch (code) { > + case HV_X64_HCALL_POST_MESSAGE: > + case HV_X64_HCALL_SIGNAL_EVENT: > + default: > + exit->u.hcall.result = HV_STATUS_INVALID_HYPERCALL_CODE; > + return 0; > + } > + } > default: > return -1; > } >
This is okay BTW, but I'm waiting for the header file update. Paolo
