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

2015-11-12 Thread Denis V. Lunev
Zhang ; Vitaly Kuznetsov 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: Denis V. Lunev [mailto:d...@openvz.org] Sent: Monday, November 2, 2015 3:34 AM Cc: rka...@virtuozzo.com; de

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

2015-11-12 Thread KY Srinivasan
ng ; Vitaly Kuznetsov > > 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: Denis V. Lunev [mailto:d...@openvz.org] > >> Sent:

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

2015-11-11 Thread Denis V. Lunev
; Vitaly Kuznetsov ; Denis V. Lunev Subject: [PATCH 1/1] drivers/hv: correct tsc page sequence invalid value 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

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

2015-11-02 Thread KY Srinivasan
Kuznetsov ; > Denis V. Lunev > Subject: [PATCH 1/1] drivers/hv: correct tsc page sequence invalid value > > 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 n

[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 implementation uses sequence value =