8a9e1b0f56
Issue: Current tsc based delay_calibration can result in significant errors in loops_per_jiffy count when the platform events like SMIs (System Management Interrupts that are non-maskable) are present. This could lead to potential kernel panic(). This issue is becoming more visible with 2.6 kernel (as default HZ is 1000) and on platforms with higher SMI handling latencies. During the boot time, SMIs are mostly used by BIOS (for things like legacy keyboard emulation). Description: The psuedocode for current delay calibration with tsc based delay looks like (0) Estimate a value for loops_per_jiffy (1) While (loops_per_jiffy estimate is accurate enough) (2) wait for jiffy transition (jiffy1) (3) Note down current tsc (tsc1) (4) loop until tsc becomes tsc1 + loops_per_jiffy (5) check whether jiffy changed since jiffy1 or not and refine loops_per_jiffy estimate Consider the following cases Case 1: If SMIs happen between (2) and (3) above, we can end up with a loops_per_jiffy value that is too low. This results in shorted delays and kernel can panic () during boot (Mostly at IOAPIC timer initialization timer_irq_works() as we don't have enough timer interrupts in a specified interval). Case 2: If SMIs happen between (3) and (4) above, then we can end up with a loops_per_jiffy value that is too high. And with current i386 code, too high lpj value (greater than 17M) can result in a overflow in delay.c:__const_udelay() again resulting in shorter delay and panic(). Solution: The patch below makes the calibration routine aware of asynchronous events like SMIs. We increase the delay calibration time and also identify any significant errors (greater than 12.5%) in the calibration and notify it to user. Patch below changes both i386 and x86-64 architectures to use this new and improved calibrate_delay_direct() routine. Signed-off-by: Venkatesh Pallipadi <venkatesh.pallipadi@intel.com> Signed-off-by: Adrian Bunk <bunk@stusta.de> Signed-off-by: Andrew Morton <akpm@osdl.org> Signed-off-by: Linus Torvalds <torvalds@osdl.org>
76 lines
1.6 KiB
C
76 lines
1.6 KiB
C
#include <linux/init.h>
|
|
#include <linux/kernel.h>
|
|
#include <linux/string.h>
|
|
#include <asm/timer.h>
|
|
|
|
#ifdef CONFIG_HPET_TIMER
|
|
/*
|
|
* HPET memory read is slower than tsc reads, but is more dependable as it
|
|
* always runs at constant frequency and reduces complexity due to
|
|
* cpufreq. So, we prefer HPET timer to tsc based one. Also, we cannot use
|
|
* timer_pit when HPET is active. So, we default to timer_tsc.
|
|
*/
|
|
#endif
|
|
/* list of timers, ordered by preference, NULL terminated */
|
|
static struct init_timer_opts* __initdata timers[] = {
|
|
#ifdef CONFIG_X86_CYCLONE_TIMER
|
|
&timer_cyclone_init,
|
|
#endif
|
|
#ifdef CONFIG_HPET_TIMER
|
|
&timer_hpet_init,
|
|
#endif
|
|
#ifdef CONFIG_X86_PM_TIMER
|
|
&timer_pmtmr_init,
|
|
#endif
|
|
&timer_tsc_init,
|
|
&timer_pit_init,
|
|
NULL,
|
|
};
|
|
|
|
static char clock_override[10] __initdata;
|
|
|
|
static int __init clock_setup(char* str)
|
|
{
|
|
if (str)
|
|
strlcpy(clock_override, str, sizeof(clock_override));
|
|
return 1;
|
|
}
|
|
__setup("clock=", clock_setup);
|
|
|
|
|
|
/* The chosen timesource has been found to be bad.
|
|
* Fall back to a known good timesource (the PIT)
|
|
*/
|
|
void clock_fallback(void)
|
|
{
|
|
cur_timer = &timer_pit;
|
|
}
|
|
|
|
/* iterates through the list of timers, returning the first
|
|
* one that initializes successfully.
|
|
*/
|
|
struct timer_opts* __init select_timer(void)
|
|
{
|
|
int i = 0;
|
|
|
|
/* find most preferred working timer */
|
|
while (timers[i]) {
|
|
if (timers[i]->init)
|
|
if (timers[i]->init(clock_override) == 0)
|
|
return timers[i]->opts;
|
|
++i;
|
|
}
|
|
|
|
panic("select_timer: Cannot find a suitable timer\n");
|
|
return NULL;
|
|
}
|
|
|
|
int read_current_timer(unsigned long *timer_val)
|
|
{
|
|
if (cur_timer->read_timer) {
|
|
*timer_val = cur_timer->read_timer();
|
|
return 0;
|
|
}
|
|
return -1;
|
|
}
|