Re: [Qemu-devel] [PATCH v2] target-i386/kvm: Hyper-V VMBus hypercalls blank handlers

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 




----- Original Message -----
> From: "Eduardo Habkost" <ehabkost@xxxxxxxxxx>
> To: "Andrey Smetanin" <asmetanin@xxxxxxxxxxxxx>
> Cc: qemu-devel@xxxxxxxxxx, kvm@xxxxxxxxxxxxxxx, "Marcelo Tosatti" <mtosatti@xxxxxxxxxx>, "Roman Kagan"
> <rkagan@xxxxxxxxxxxxx>, "Denis V. Lunev" <den@xxxxxxxxxx>, "Paolo Bonzini" <pbonzini@xxxxxxxxxx>, "Andreas Färber"
> <afaerber@xxxxxxx>, "Richard Henderson" <rth@xxxxxxxxxxx>
> Sent: Saturday, January 23, 2016 4:20:13 PM
> Subject: Re: [Qemu-devel] [PATCH v2] target-i386/kvm: Hyper-V VMBus hypercalls blank handlers
> 
> On Thu, Jan 21, 2016 at 05:04:20PM +0300, 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
> > 
> 
> Paolo, this needs a linux-headers update. Should I let you update
> the headers in your tree and apply this patch, or can I run
> update-linux-headers.sh on my x86 branch?

This patch's dependency is not even in any upstream KVM branch, so it
will take some time.  For now, just apply it with the linux-headers
changes, and don't "graduate" it from x86-next to x86 until the
headers are updated.

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



[Index of Archives]     [KVM ARM]     [KVM ia64]     [KVM ppc]     [Virtualization Tools]     [Spice Development]     [Libvirt]     [Libvirt Users]     [Linux USB Devel]     [Linux Audio Users]     [Yosemite Questions]     [Linux Kernel]     [Linux SCSI]     [XFree86]
  Powered by Linux