On Wed, Mar 16, 2016 at 10:38:14PM +0100, Rafael J. Wysocki wrote: > > If you care what cpu the work runs on, you should schedule_work_on(), > > regular schedule_work() can end up on any random cpu (although typically > > it does not). > > I know, but I don't care too much. > > "ondemand" and "conservative" use schedule_work() for the same thing, so > drivers need to cope with that if they need things to run on a particular > CPU. Or are just plain buggy -- like a lot of code that uses schedule_work() for per-cpu thingies; that is, its a fairly common bug and only recently did we add that RR thing. -- To unsubscribe from this list: send the line "unsubscribe linux-acpi" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
