From: Paolo Bonzini <pbonzini@redhat.com>
To: asmetanin@virtuozzo.com, kvm@vger.kernel.org
Cc: Gleb Natapov <gleb@kernel.org>, Joerg Roedel <joro@8bytes.org>,
"K. Y. Srinivasan" <kys@microsoft.com>,
Haiyang Zhang <haiyangz@microsoft.com>,
Roman Kagan <rkagan@virtuozzo.com>,
"Denis V. Lunev" <den@openvz.org>,
qemu-devel@nongnu.org
Subject: Re: [PATCH v3 2/5] drivers/hv: Move VMBus hypercall codes into Hyper-V UAPI header
Date: Fri, 12 Feb 2016 14:16:02 +0100 [thread overview]
Message-ID: <56BDDB12.7020608@redhat.com> (raw)
In-Reply-To: <56BD9358.9040307@virtuozzo.com>
On 12/02/2016 09:10, Andrey Smetanin wrote:
>>>
>>> - hv_do_hypercall(HVCALL_SIGNAL_EVENT, channel->sig_event, NULL);
>>> + hv_do_hypercall(HV_X64_HCALL_SIGNAL_EVENT, channel->sig_event,
>>> NULL);
>>
>> What tree does this apply to?
> next-20160211
Ok, I'll check whether I can just merge something from KY to get the
hv.c->connection.c code movement. Otherwise we probably should just
leave the HVCALL_* constants unchanged.
Paolo
next prev parent reply other threads:[~2016-02-12 13:16 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-02-11 13:44 [PATCH v3 0/5] KVM: Hyper-V VMBus hypercalls Andrey Smetanin
2016-02-11 13:44 ` [PATCH v3 1/5] kvm/x86: Rename Hyper-V long spin wait hypercall Andrey Smetanin
2016-02-11 13:44 ` [PATCH v3 2/5] drivers/hv: Move VMBus hypercall codes into Hyper-V UAPI header Andrey Smetanin
2016-02-11 21:46 ` Paolo Bonzini
2016-02-12 8:10 ` Andrey Smetanin
2016-02-12 13:16 ` Paolo Bonzini [this message]
2016-02-11 13:44 ` [PATCH v3 3/5] kvm/x86: Pass return code of kvm_emulate_hypercall Andrey Smetanin
2016-02-11 13:45 ` [PATCH v3 4/5] kvm/x86: Reject Hyper-V hypercall continuation Andrey Smetanin
2016-02-11 13:45 ` [PATCH v3 5/5] kvm/x86: Hyper-V VMBus hypercall userspace exit Andrey Smetanin
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=56BDDB12.7020608@redhat.com \
--to=pbonzini@redhat.com \
--cc=asmetanin@virtuozzo.com \
--cc=den@openvz.org \
--cc=gleb@kernel.org \
--cc=haiyangz@microsoft.com \
--cc=joro@8bytes.org \
--cc=kvm@vger.kernel.org \
--cc=kys@microsoft.com \
--cc=qemu-devel@nongnu.org \
--cc=rkagan@virtuozzo.com \
/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).