public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: "Denis V. Lunev" <den@openvz.org>
To: KY Srinivasan <kys@microsoft.com>
Cc: "rkagan@virtuozzo.com" <rkagan@virtuozzo.com>,
	"devel@linuxdriverproject.org" <devel@linuxdriverproject.org>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
	Andrey Smetanin <asmetanin@virtuozzo.com>,
	Haiyang Zhang <haiyangz@microsoft.com>,
	Vitaly Kuznetsov <vkuznets@redhat.com>
Subject: Re: [PATCH 1/1] drivers/hv: correct tsc page sequence invalid value
Date: Thu, 12 Nov 2015 10:16:19 +0300	[thread overview]
Message-ID: <56443CC3.5010002@openvz.org> (raw)
In-Reply-To: <BY2PR0301MB165451C8401EDD75A38C6488A02C0@BY2PR0301MB1654.namprd03.prod.outlook.com>

On 11/02/2015 10:42 PM, KY Srinivasan wrote:
>
>> -----Original Message-----
>> From: Denis V. Lunev [mailto:den@openvz.org]
>> Sent: Monday, November 2, 2015 3:34 AM
>> Cc: rkagan@virtuozzo.com; devel@linuxdriverproject.org; linux-
>> kernel@vger.kernel.org; Andrey Smetanin <asmetanin@virtuozzo.com>; KY
>> Srinivasan <kys@microsoft.com>; Haiyang Zhang
>> <haiyangz@microsoft.com>; Vitaly Kuznetsov <vkuznets@redhat.com>;
>> Denis V. Lunev <den@openvz.org>
>> Subject: [PATCH 1/1] drivers/hv: correct tsc page sequence invalid value
>>
>> From: Andrey Smetanin <asmetanin@virtuozzo.com>
>>
>> Hypervisor Top Level Functional Specification v3/4 says
>> that TSC page sequence value = -1(0xFFFFFFFF) is used to
>> indicate that TSC page no longer reliable source of reference
>> timer. Unfortunately, we found that Windows Hyper-V guest
>> side implementation uses sequence value = 0 to indicate
>> that Tsc page no longer valid. This is clearly visible
>> inside Windows 2012R2 ntoskrnl.exe HvlGetReferenceTime()
>> function dissassembly:
>>
>> HvlGetReferenceTime proc near
>>                   xchg    ax, ax
>> loc_1401C3132:
>>                   mov     rax, cs:HvlpReferenceTscPage
>>                   mov     r9d, [rax]
>>                   test    r9d, r9d
>>                   jz      short loc_1401C3176
>>                   rdtsc
>>                   mov     rcx, cs:HvlpReferenceTscPage
>>                   shl     rdx, 20h
>>                   or      rdx, rax
>>                   mov     rax, [rcx+8]
>>                   mov     rcx, cs:HvlpReferenceTscPage
>>                   mov     r8, [rcx+10h]
>>                   mul     rdx
>>                   mov     rax, cs:HvlpReferenceTscPage
>>                   add     rdx, r8
>>                   mov     ecx, [rax]
>>                   cmp     ecx, r9d
>>                   jnz     short loc_1401C3132
>>                   jmp     short loc_1401C3184
>> loc_1401C3176:
>>                   mov     ecx, 40000020h
>>                   rdmsr
>>                   shl     rdx, 20h
>>                   or      rdx, rax
>> loc_1401C3184:
>>                   mov     rax, rdx
>>                   retn
>> HvlGetReferenceTime endp
>>
>> This patch aligns Tsc page invalid sequence value with
>> Windows Hyper-V guest implementation which is more
>> compatible with both Hyper-V hypervisor and KVM hypervisor.
>>
>> Signed-off-by: Andrey Smetanin <asmetanin@virtuozzo.com>
>> CC: "K. Y. Srinivasan" <kys@microsoft.com>
> Thanks Andrey; the Hyper-V team will be updating the Hyper-V documentation.
>
> Acked-by: K. Y. Srinivasan <kys@microsoft.com>
>
> Regards,
>
> K. Y
K.Y.,

can you pls clarify the state of this patch? It is a bit unclear
to me whether it is applied or not.

By the way, I also do not see the following patch
"drivers/hv: cleanup synic msrs if vmbus connect failed"
as applied in the Linux-next. You have promised to resend
it will correct author.

Thank you in advance,
     Den

  reply	other threads:[~2015-11-12  7:16 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-11-02 11:34 [PATCH 1/1] drivers/hv: correct tsc page sequence invalid value Denis V. Lunev
2015-11-02 19:42 ` KY Srinivasan
2015-11-12  7:16   ` Denis V. Lunev [this message]
2015-11-12 17:35     ` KY Srinivasan
2015-11-12 18:57       ` Denis V. Lunev

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=56443CC3.5010002@openvz.org \
    --to=den@openvz.org \
    --cc=asmetanin@virtuozzo.com \
    --cc=devel@linuxdriverproject.org \
    --cc=haiyangz@microsoft.com \
    --cc=kys@microsoft.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=rkagan@virtuozzo.com \
    --cc=vkuznets@redhat.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