qemu-devel
[Top][All Lists]
Advanced

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

Re: [Qemu-devel] [PATCH 0/3] QEMU: necessary simple pre-requisites for V


From: Paolo Bonzini
Subject: Re: [Qemu-devel] [PATCH 0/3] QEMU: necessary simple pre-requisites for VMBus emulation
Date: Wed, 16 Sep 2015 12:32:05 +0200
User-agent: Mozilla/5.0 (X11; Linux x86_64; rv:38.0) Gecko/20100101 Thunderbird/38.2.0


On 16/09/2015 11:59, Denis V. Lunev wrote:
> Hyper-V reset, vp index, vp runtime support is required to
> support loading Windows guest driver Winhv.sys. Winhv.sys in guest
> is required to support Windows VMBus.
> 
> These changes are simple and straightforward. Let's them go first.
> 
> Paolo, I am sending these patches without taking into account your
> patchset with header cleanup. Should we do something? I would be also
> be happy to hear news about remaining patches from Andrey about HyperV
> panic.

They didn't compile on ARM or Win32, hence the header file changes which
delayed them a bit.  But I still plan to send out the pull request very
soon, maybe today (ouch, it's already 12:30).

I wanted to include the record-replay patches, but they are big enough
that they probably deserve their own pull request, and my queue already
has 23 patches...

> Please let us know is something from our side will improve the
> situation.

No, it's just my issue.

However, there is something we can improve about the process.  QEMU
typically updates header files around 4.3-rc5 (by importing the changes
destined to 4.4), so we need a place to put this kind of patch that
depends on Linux header changes.  Therefore:

1) I've made a staging branch uq/hyperv (uq = upstream queue) on
git://git.kernel.org/pub/scm/virt/kvm/qemu-kvm.git - you can base your
patches on that branch as soon as I create it.

2) if you have more changes to asm/hyperv.h, bundle them and send them
to address@hidden  I'll include them in kvm/queue all at the same
time, which will make header file synchronization less of a problem in
the future.

Paolo



reply via email to

[Prev in Thread] Current Thread [Next in Thread]