On Wednesday, October 28, 2015 08:58:11 PM Viresh Kumar wrote: > On 28-10-15, 16:31, Rafael J. Wysocki wrote: > > Is the current code really problematic? > > Its not problematic, but just that I didn't like special code written > here. > > Also, its a blocker for the next patch which tries to schedule work on > all the policy->cpus together.
Well, the second statement above sort of contradicts the first one. :-) I guess the answer is "it is problematic, because I can't do the other optimization then". To that I'd really suggest trying to rework the code to use timer functions directly in the first place. Thanks, Rafael -- 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/
