Messages in this thread | | | From | David Mosberger <> | Date | Sat, 8 Dec 2001 08:41:23 -0800 | Subject | Re: [PATCH] 2.4.16 kernel/printk.c (per processorinitializationcheck) |
| |
>>>>> On Sat, 8 Dec 2001 11:27:19 +0000 (GMT), Alan Cox <alan@lxorguk.ukuu.org.uk> 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?
--david - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
| |