Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]


Groups > linux.kernel > #1419414 > unrolled thread

Re: [PATCH 0/9] x86: TSC calibration update

Started byThomas Gleixner <tglx@linutronix.de>
First post2016-06-10 15:30 +0200
Last post2016-06-10 15:30 +0200
Articles 1 — 1 participant

Back to article view | Back to linux.kernel

This discussion starts older than the indexed window; earlier articles aren't shown. The article labeled Started by below is the oldest one visible, not the original post.


Contents

  Re: [PATCH 0/9] x86: TSC calibration update Thomas Gleixner <tglx@linutronix.de> - 2016-06-10 15:30 +0200

#1419414 — Re: [PATCH 0/9] x86: TSC calibration update

FromThomas Gleixner <tglx@linutronix.de>
Date2016-06-10 15:30 +0200
SubjectRe: [PATCH 0/9] x86: TSC calibration update
Message-ID<rIuFA-55o-29@gated-at.bofh.it>
Len,

On Thu, 31 Mar 2016, Len Brown wrote:

> cpu_khz and tsc_khz initialization can be unreliable and expensive.
> They are initialized in tsc_init()/native_calibrate_tsc(), which prints:
> 
> pr_info("Detected %lu.%03lu MHz processor\n", cpu_khz...)
> 
> native_calibrate_cpu() first tries quick_pit_calibrate(),
> which can take over 50.0M cycles to succeed,
> or as few as 2.4M cycles to fail.
> 
> On failure, pit_calibrate_tsc() is attempted, which can succeed
> in as few as 20M cycles, but may consume over 240M cycles
> before it fails.
> 
> By comparison, on many processors, tsc frequency can be discovered by
> table and MSR or CPUID in under 0.002M cycles.

I found this in my backlog. Sorry for missing it. 

The series does not apply anymore and the hardcoded family constants want to
be replaced by the new model defines.

Could you please resend?

Thanks,

	tglx

[toc] | [standalone]


Back to top | Article view | linux.kernel


csiph-web