"Paul E. McKenney" <[email protected]> writes: > +KNOWN ISSUES
[...] > +o Unless all CPUs are idle, at least one CPU must keep the > + scheduling-clock interrupt going in order to support accurate > + timekeeping. At least with the implementation I'm using (Frederic's 3.9-nohz1 branch), at least one CPU is forced to stay out of dyntick-idle *always*, even if all CPUs are idle. IMO, this is important to list as a known issue since this will have its own power implications when the system is mostly idle. Otherwise, document looks great. Reviewed-by: Kevin Hilman <[email protected]> Kevin -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [email protected] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
