diff options
| author | Alok Kataria <[email protected]> | 2008-06-20 15:06:33 -0700 |
|---|---|---|
| committer | Ingo Molnar <[email protected]> | 2008-06-23 22:51:33 +0200 |
| commit | 3da757daf86e498872855f0b5e101f763ba79499 (patch) | |
| tree | bffffafed7322c66a1b886b661cfd8a8a7f5a924 /tools/perf/scripts/python | |
| parent | e01b70ef3eb3080fecc35e15f68cd274c0a48163 (diff) | |
x86: use cpu_khz for loops_per_jiffy calculation
On the x86 platform we can use the value of tsc_khz computed during tsc
calibration to calculate the loops_per_jiffy value. Its very important
to keep the error in lpj values to minimum as any error in that may
result in kernel panic in check_timer. In virtualization environment, On
a highly overloaded host the guest delay calibration may sometimes
result in errors beyond the ~50% that timer_irq_works can handle,
resulting in the guest panicking.
Does some formating changes to lpj_setup code to now have a single
printk to print the bogomips value.
We do this only for the boot processor because the AP's can have
different base frequencies or the BIOS might boot a AP at a different
frequency.
Signed-off-by: Alok N Kataria <[email protected]>
Cc: Arjan van de Ven <[email protected]>
Cc: Daniel Hecht <[email protected]>
Cc: Tim Mann <[email protected]>
Cc: Zach Amsden <[email protected]>
Cc: Sahil Rihan <[email protected]>
Signed-off-by: Ingo Molnar <[email protected]>
Diffstat (limited to 'tools/perf/scripts/python')
0 files changed, 0 insertions, 0 deletions