From: "Denis V. Lunev" <den-lists@parallels.com>
To: Paolo Bonzini <pbonzini@redhat.com>, "Denis V. Lunev" <den@openvz.org>
Cc: "Eduardo Habkost" <ehabkost@redhat.com>,
"Marcelo Tosatti" <mtosatti@redhat.com>,
qemu-devel@nongnu.org,
"Andrey Smetanin" <asmetanin@virtuozzo.com>,
"Andreas Färber" <afaerber@suse.de>,
"Richard Henderson" <rth@twiddle.net>
Subject: Re: [Qemu-devel] [PATCH 0/3] QEMU: necessary simple pre-requisites for VMBus emulation
Date: Wed, 16 Sep 2015 13:41:41 +0300 [thread overview]
Message-ID: <55F94765.1060604@parallels.com> (raw)
In-Reply-To: <55F94525.1010907@redhat.com>
On 09/16/2015 01:32 PM, Paolo Bonzini wrote:
>
> 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 kvm@vger.kernel.org. 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
>
that sounds great to me. OK, will do.
Den
prev parent reply other threads:[~2015-09-16 10:42 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-09-16 9:59 [Qemu-devel] [PATCH 0/3] QEMU: necessary simple pre-requisites for VMBus emulation Denis V. Lunev
2015-09-16 9:59 ` [Qemu-devel] [PATCH 1/3] target-i386/kvm: Hyper-V HV_X64_MSR_RESET support Denis V. Lunev
2015-09-16 9:59 ` [Qemu-devel] [PATCH 2/3] target-i386/kvm: set Hyper-V features cpuid bit HV_X64_MSR_VP_INDEX_AVAILABLE Denis V. Lunev
2015-09-16 9:59 ` [Qemu-devel] [PATCH 3/3] target-i386/kvm: Hyper-V HV_X64_MSR_VP_RUNTIME support Denis V. Lunev
2015-09-16 10:32 ` [Qemu-devel] [PATCH 0/3] QEMU: necessary simple pre-requisites for VMBus emulation Paolo Bonzini
2015-09-16 10:41 ` Denis V. Lunev [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=55F94765.1060604@parallels.com \
--to=den-lists@parallels.com \
--cc=afaerber@suse.de \
--cc=asmetanin@virtuozzo.com \
--cc=den@openvz.org \
--cc=ehabkost@redhat.com \
--cc=mtosatti@redhat.com \
--cc=pbonzini@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=rth@twiddle.net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).