On Mon, Oct 14, 2013 at 05:13:11PM +0100, Arjan van de Ven wrote: > On 10/14/2013 9:10 AM, Morten Rasmussen wrote: > > On Mon, Oct 14, 2013 at 02:33:56PM +0100, Peter Zijlstra wrote: > >> On Fri, Oct 11, 2013 at 06:19:14PM +0100, Morten Rasmussen wrote: > >>> Removing power hints for kworker threads enables easier use of > >>> workqueues in the power driver late callback. That would otherwise > >>> lead to an endless loop unless it is prevented in the power driver. > >> > >> There's many kworker users; some of them actually consume lots of > >> cputime. Therefore how did you come to the conclusion that excepting all > >> users was the better choice of a little added complexity in the one > >> place where it actually matters? > > > > Agreed that it is not ideal. I will find a better solution for this > > problem. > > > > can you explain which architectures we're talking about that need this? > is it only old stuff, or is there anything current ? >
For now I need it for the cpufreq wrapper governor. I hope it can be avoided for native power drivers, but I don't have a complete overview of all architectures yet. -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
