RE: [PATCH 1/1] drivers/hv: correct tsc page sequence invalid value

2015-11-12 Thread KY Srinivasan
<asmeta...@virtuozzo.com>; > Haiyang Zhang <haiya...@microsoft.com>; Vitaly Kuznetsov > <vkuzn...@redhat.com> > Subject: Re: [PATCH 1/1] drivers/hv: correct tsc page sequence invalid value > > On 11/02/2015 10:42 PM, KY Srinivasan wrote: > > > >>

Re: [PATCH 1/1] drivers/hv: correct tsc page sequence invalid value

2015-11-12 Thread Denis V. Lunev
Andrey Smetanin <asmeta...@virtuozzo.com>; Haiyang Zhang <haiya...@microsoft.com>; Vitaly Kuznetsov <vkuzn...@redhat.com> Subject: Re: [PATCH 1/1] drivers/hv: correct tsc page sequence invalid value On 11/02/2015 10:42 PM, KY Srinivasan wrote: -Original Message- From:

Re: [PATCH 1/1] drivers/hv: correct tsc page sequence invalid value

2015-11-11 Thread Denis V. Lunev
t;; KY Srinivasan <k...@microsoft.com>; Haiyang Zhang <haiya...@microsoft.com>; Vitaly Kuznetsov <vkuzn...@redhat.com>; Denis V. Lunev <d...@openvz.org> Subject: [PATCH 1/1] drivers/hv: correct tsc page sequence invalid value From: Andrey Smetanin <asmeta...@virtuozzo.com&

RE: [PATCH 1/1] drivers/hv: correct tsc page sequence invalid value

2015-11-02 Thread KY Srinivasan
asan <k...@microsoft.com>; Haiyang Zhang > <haiya...@microsoft.com>; Vitaly Kuznetsov <vkuzn...@redhat.com>; > Denis V. Lunev <d...@openvz.org> > Subject: [PATCH 1/1] drivers/hv: correct tsc page sequence invalid value > > From: Andrey Smetanin <asmeta...@virtuozzo

[PATCH 1/1] drivers/hv: correct tsc page sequence invalid value

2015-11-02 Thread Denis V. Lunev
From: Andrey Smetanin Hypervisor Top Level Functional Specification v3/4 says that TSC page sequence value = -1(0x) is used to indicate that TSC page no longer reliable source of reference timer. Unfortunately, we found that Windows Hyper-V guest side