On 2018-12-14 10:27:41 [+0200], Benjamin Bouvier wrote: > As there is currently no information on which RT task is throttled, add a > new tracepoint for debug purpose. By the way improve printk debugging > message by adding task name, pid and cpu for which the throttle has been > executed.
Throttling is for _all_ RT class applications. The task you print might be innocent and getting the blame. The interesting part is to see all the RT tasks (not sure about DL) since the last time, the timer was started on the CPU. Sebastian
