From mboxrd@z Thu Jan  1 00:00:00 1970
From: "Denis V. Lunev" <den@openvz.org>
Subject: Re: [PATCH v1 0/7] KVM: Hyper-V SynIC timers
Date: Tue, 1 Dec 2015 13:28:28 +0300
Message-ID: <565D764C.103@openvz.org>
References: <1448464821-8199-1-git-send-email-asmetanin@virtuozzo.com>
 <CANRm+CyKLT2yNDvzuJioVeT=+n62w3X=mJLPZv2sDmtwqatN8A@mail.gmail.com>
 <5656C42E.9090502@virtuozzo.com>
 <CANRm+Czx8hL28w7spSGNzCMDnCkWXvo5OhPxSrmf4P1DRMU6zA@mail.gmail.com>
Mime-Version: 1.0
Content-Type: text/plain; charset="utf-8"; format=flowed
Content-Transfer-Encoding: 7bit
Cc: kvm <kvm@vger.kernel.org>, Gleb Natapov <gleb@kernel.org>,
	Paolo Bonzini <pbonzini@redhat.com>,
	"K. Y. Srinivasan" <kys@microsoft.com>,
	Haiyang Zhang <haiyangz@microsoft.com>,
	Vitaly Kuznetsov <vkuznets@redhat.com>,
	Roman Kagan <rkagan@virtuozzo.com>,
	"qemu-devel@nongnu.org Developers" <qemu-devel@nongnu.org>
To: Wanpeng Li <kernellwp@gmail.com>,
	Andrey Smetanin <asmetanin@virtuozzo.com>
Return-path: <kvm-owner@vger.kernel.org>
Received: from relay.parallels.com ([195.214.232.42]:50432 "EHLO
	relay.parallels.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org
	with ESMTP id S1750721AbbLAK2q (ORCPT <rfc822;kvm@vger.kernel.org>);
	Tue, 1 Dec 2015 05:28:46 -0500
In-Reply-To: <CANRm+Czx8hL28w7spSGNzCMDnCkWXvo5OhPxSrmf4P1DRMU6zA@mail.gmail.com>
Sender: kvm-owner@vger.kernel.org
List-ID: <kvm.vger.kernel.org>

On 12/01/2015 01:12 PM, Wanpeng Li wrote:
> 2015-11-26 16:34 GMT+08:00 Andrey Smetanin <asmetanin@virtuozzo.com>:
>>
>> On 11/26/2015 08:28 AM, Wanpeng Li wrote:
>>> 2015-11-25 23:20 GMT+08:00 Andrey Smetanin <asmetanin@virtuozzo.com>:
>>>> Per Hyper-V specification (and as required by Hyper-V-aware guests),
>>>> SynIC provides 4 per-vCPU timers.  Each timer is programmed via a pair
>>>> of MSRs, and signals expiration by delivering a special format message
>>>> to the configured SynIC message slot and triggering the corresponding
>>>> synthetic interrupt.
>>>
>>> Could you post a link for this specification?
>>
>> Official link:
>>
>> http://download.microsoft.com/download/A/B/4/AB43A34E-BDD0-4FA6-BDEF-79EEF16E880B/Hypervisor%20Top%20Level%20Functional%20Specification%20v4.0.docx
>>
>> and there is a pdf variant(my own docx -> pdf conversion):
>>
>> https://www.dropbox.com/s/ehxictr5wgnedq7/Hypervisor%20Top%20Level%20Functional%20Specification%20v4.0.pdf?dl=0
> Btw, is there performance data for such feature?
>
> Regards,
> Wanpeng Li
not yet.

This is a requirement for any Hyper-V device emulation
to be activated by Windows. We are going to have
basic infrastructure merged and run performance tests
with all that stuff done.

Den