Re: [PATCH 1/4] nohz: Force boot CPU outside full dynticks range

[Ingo Molnar]

* Frederic Weisbecker <fweisbec@xxxxxxxxx> wrote:

> The timekeeping job must be able to run early on boot
> because there may be some pre-SMP (and thus pre-initcalls )
> components that rely on it. The IO-APIC is one such users
> as it tests the timer health by watching jiffies progression.

Btw., while I agree that a conservative mode is probably wise for bootup, 
that IO-APIC assumption could be fixed or even removed.

If the IO-APIC code wants to know whether an interrupt fired, it can take 
a look at the kstat_irqs numbers?

Also, could we restrict the boot CPU's mode only during the early bootup 
stage - i.e. until we are ready to execute user-space init?

Thaks,

	Ingo
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/