Re: [PATCH] 2.4.16 kernel/printk.c (per processorinitializationcheck)

From: David Mosberger (
Date: Sat Dec 08 2001 - 11:41:23 EST

>>>>> On Sat, 8 Dec 2001 11:27:19 +0000 (GMT), Alan Cox <> said:

>> I'm no x86 expert, but I have the impression that
>> current_cpu_data.loops_per_jiffy will be invalid (probably 0)
>> until smp_store_cpu_info() is called in smp_callin(). If so, a
>> console driver using udelay() might not work properly. I suspect
>> there are other issues, but this is just based on looking at the
>> x86 source code for 5 minutes.

  Alan> x86_udelay_tsc wont have been set at that point so the main
  Alan> timer is still being used.

x86 does use current_cpu_data.loops_per_jiffy in the non-TSC case, no?

To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to
More majordomo info at
Please read the FAQ at

This archive was generated by hypermail 2b29 : Sat Dec 15 2001 - 21:00:12 EST