On 10/12/2017 8:22 AM, Thomas Gleixner wrote:
On Thu, 12 Oct 2017, Mike Travis wrote:
On 10/12/2017 4:17 AM, Thomas Gleixner wrote:
On Thu, 5 Oct 2017, mike.tra...@hpe.com wrote:
@@ -89,6 +93,10 @@ bool tsc_store_and_check_tsc_adjust(bool
if (!boot_cpu_has(X86_FEATURE_TSC_ADJUST))
On 10/12/2017 8:22 AM, Thomas Gleixner wrote:
On Thu, 12 Oct 2017, Mike Travis wrote:
On 10/12/2017 4:17 AM, Thomas Gleixner wrote:
On Thu, 5 Oct 2017, mike.tra...@hpe.com wrote:
@@ -89,6 +93,10 @@ bool tsc_store_and_check_tsc_adjust(bool
if (!boot_cpu_has(X86_FEATURE_TSC_ADJUST))
If the TSC has already been determined to be unstable, then checking
TSC ADJUST values is a waste of time and generates unnecessary error
messages.
Signed-off-by: Mike Travis
Reviewed-by: Dimitri Sivanich
Reviewed-by: Russ Anderson
If the TSC has already been determined to be unstable, then checking
TSC ADJUST values is a waste of time and generates unnecessary error
messages.
Signed-off-by: Mike Travis
Reviewed-by: Dimitri Sivanich
Reviewed-by: Russ Anderson
Reviewed-by: Peter Zijlstra
---
v2: Add check_tsc_unstable to
On Thu, 12 Oct 2017, Mike Travis wrote:
> On 10/12/2017 4:17 AM, Thomas Gleixner wrote:
> > On Thu, 5 Oct 2017, mike.tra...@hpe.com wrote:
> > > @@ -89,6 +93,10 @@ bool tsc_store_and_check_tsc_adjust(bool
> > > if (!boot_cpu_has(X86_FEATURE_TSC_ADJUST))
> > > return
On Thu, 12 Oct 2017, Mike Travis wrote:
> On 10/12/2017 4:17 AM, Thomas Gleixner wrote:
> > On Thu, 5 Oct 2017, mike.tra...@hpe.com wrote:
> > > @@ -89,6 +93,10 @@ bool tsc_store_and_check_tsc_adjust(bool
> > > if (!boot_cpu_has(X86_FEATURE_TSC_ADJUST))
> > > return
On 10/12/2017 4:17 AM, Thomas Gleixner wrote:
On Thu, 5 Oct 2017, mike.tra...@hpe.com wrote:
If the TSC has already been determined to be unstable, then checking
TSC ADJUST values is a waste of time and generates unnecessary error
messages.
Signed-off-by: Mike Travis
On 10/12/2017 4:17 AM, Thomas Gleixner wrote:
On Thu, 5 Oct 2017, mike.tra...@hpe.com wrote:
If the TSC has already been determined to be unstable, then checking
TSC ADJUST values is a waste of time and generates unnecessary error
messages.
Signed-off-by: Mike Travis
Reviewed-by: Dimitri
On Thu, 5 Oct 2017, mike.tra...@hpe.com wrote:
> If the TSC has already been determined to be unstable, then checking
> TSC ADJUST values is a waste of time and generates unnecessary error
> messages.
>
> Signed-off-by: Mike Travis
> Reviewed-by: Dimitri Sivanich
On Thu, 5 Oct 2017, mike.tra...@hpe.com wrote:
> If the TSC has already been determined to be unstable, then checking
> TSC ADJUST values is a waste of time and generates unnecessary error
> messages.
>
> Signed-off-by: Mike Travis
> Reviewed-by: Dimitri Sivanich
> Reviewed-by: Russ Anderson
If the TSC has already been determined to be unstable, then checking
TSC ADJUST values is a waste of time and generates unnecessary error
messages.
Signed-off-by: Mike Travis
Reviewed-by: Dimitri Sivanich
Reviewed-by: Russ Anderson
If the TSC has already been determined to be unstable, then checking
TSC ADJUST values is a waste of time and generates unnecessary error
messages.
Signed-off-by: Mike Travis
Reviewed-by: Dimitri Sivanich
Reviewed-by: Russ Anderson
Reviewed-by: Peter Zijlstra
---
arch/x86/kernel/tsc_sync.c |
If the TSC has already been determined to be unstable, then checking
TSC ADJUST values is a waste of time and generates unnecessary error
messages.
Signed-off-by: Mike Travis
Reviewed-by: Dimitri Sivanich
Reviewed-by: Russ Anderson
If the TSC has already been determined to be unstable, then checking
TSC ADJUST values is a waste of time and generates unnecessary error
messages.
Signed-off-by: Mike Travis
Reviewed-by: Dimitri Sivanich
Reviewed-by: Russ Anderson
Reviewed-by: Peter Zijlstra
---
arch/x86/kernel/tsc_sync.c |
14 matches
Mail list logo