From mboxrd@z Thu Jan 1 00:00:00 1970
Received: from eggs.gnu.org ([2001:4830:134:3::10]:39042)
by lists.gnu.org with esmtp (Exim 4.71)
(envelope-from
) id 1aB0Vh-00017a-Go
for qemu-devel@nongnu.org; Mon, 21 Dec 2015 08:28:22 -0500
Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71)
(envelope-from ) id 1aB0Vd-0006bI-HX
for qemu-devel@nongnu.org; Mon, 21 Dec 2015 08:28:21 -0500
Received: from mailout4.w1.samsung.com ([210.118.77.14]:22392)
by eggs.gnu.org with esmtp (Exim 4.71)
(envelope-from ) id 1aB0Vd-0006ay-B7
for qemu-devel@nongnu.org; Mon, 21 Dec 2015 08:28:17 -0500
Received: from eucpsbgm2.samsung.com (unknown [203.254.199.245])
by mailout4.w1.samsung.com
(Oracle Communications Messaging Server 7.0.5.31.0 64bit (built May 5
2014)) with ESMTP id <0NZP005WVMR11O80@mailout4.w1.samsung.com> for
qemu-devel@nongnu.org; Mon, 21 Dec 2015 13:28:13 +0000 (GMT)
From: Pavel Fedin
References: <1447158995-21919-1-git-send-email-asmetanin@virtuozzo.com>
<1447158995-21919-6-git-send-email-asmetanin@virtuozzo.com>
<01cc01d139a7$7baad550$73007ff0$@samsung.com>
<56742DF7.9000902@redhat.com>
<20151218183911.GF3050@rkaganb.sw.ru> <5677F7C5.5040404@virtuozzo.com>
In-reply-to: <5677F7C5.5040404@virtuozzo.com>
Date: Mon, 21 Dec 2015 16:28:12 +0300
Message-id: <003201d13bf3$714edae0$53ec90a0$@samsung.com>
MIME-version: 1.0
Content-type: text/plain; charset=us-ascii
Content-transfer-encoding: 7bit
Content-language: ru
Subject: Re: [Qemu-devel] [PATCH v4 5/5] kvm/x86: Hyper-V kvm exit
List-Id:
List-Unsubscribe: ,
List-Archive:
List-Post:
List-Help:
List-Subscribe: ,
To: asmetanin@virtuozzo.com, 'Roman Kagan' , 'Peter Hornyack' , 'Paolo Bonzini' , 'kvm list' , "'Denis V. Lunev'" , 'Gleb Natapov' , qemu-devel@nongnu.org
Hello!
> Yes, we can use KVM_EXIT_REG_IO/MSR_IO for Hyper-V SynIC MSRS's changes
> and can even use only one MSR value . So union inside struct
> kvm_hyperv_exit is excessive.
>
> But we still need Vcpu exit to handle VMBus hypercalls by QEMU to
> emulate VMBus devices inside QEMU.
>
> And currently we are going to extend struct kvm_hyperv_exit
> to store Hyper-V VMBus hypercall parameters.
Hm... Hypercalls, you say?
We already have KVM_EXIT_HYPERCALL. Documentation says it's currently unused. Is it a leftover from ia64 KVM? Could we reuse it for
the purpose?
> but could we replace Hyper-V VMBus hypercall and it's parameters
> by KVM_EXIT_REG_IO/MSR_IO too?
It depends. Can i read about these hypercalls somewhere? Is there any documentation?
Kind regards,
Pavel Fedin
Expert Engineer
Samsung Electronics Research center Russia