[PATCH RESEND 24/27] drivers/hv: correct tsc page sequence invalid value

2015-12-14 Thread K. Y. Srinivasan
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 =

[PATCH RESEND 24/27] drivers/hv: correct tsc page sequence invalid value

2015-12-14 Thread K. Y. Srinivasan
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

[PATCH RESEND 24/27] drivers/hv: correct tsc page sequence invalid value

2015-12-11 Thread K. Y. Srinivasan
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 =

[PATCH RESEND 24/27] drivers/hv: correct tsc page sequence invalid value

2015-12-11 Thread K. Y. Srinivasan
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