On Wed, Oct 08, 2014 at 04:28:36PM -0700, Mike Turquette wrote: > > Yeah, like hell no. We do not want modules to affect scheduler > > behaviour. > > If a CPUfreq driver is the best place to know how frequency affects the > capacity of a CPU for a given system, are you suggesting that we must > compile that code into the kernel image instead of it being a loadable > module?
Ideally we'll end up doing away with the cpufreq policy modules and integrate the entire thing into the scheduler. -- 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/
