On Fri, Feb 23, 2018 at 5:18 PM, Bart Van Assche <Bart.VanAssche@xxxxxxx> wrote: > On Fri, 2018-02-23 at 11:05 +0100, Rafael J. Wysocki wrote: >> On Fri, Feb 23, 2018 at 1:22 AM, Bart Van Assche <bart.vanassche@xxxxxxx> wrote: >> > Avoid that the following is reported during boot with kmemleak >> > enabled: >> >> OK, so why is this fix the right one in your view? > > No Linux kernel code should keep running for multiple seconds without giving > the scheduler a chance to schedule another thread. Hence the insertion of the > cond_resched() call. I see. > It is very well possible that the fact that this code keeps the CPU for > itself so long is a bug by itself. However, I'm not familiar enough with the > ACPI code to figure out whether any alternative solutions exist that would be > better than the patch I posted. OK, we'll look at the code and see how it can be improved upstream. Thanks a lot for letting us know about this issue! -- 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
