Lines Matching refs:tasks

524         Traces all tasks as an average developer would expect.
529         RT tasks (as the current "wakeup" does). This is useful
530         for those interested in wake up timings of RT tasks.
1378 Now for non Real-Time tasks, this can be arbitrary. But tracing
1418 Non Real-Time tasks are not that interesting. A more interesting
1419 trace is to concentrate only on Real-Time tasks.
1427 latency". I stress the point that this is about RT tasks. It is
1428 also important to know the scheduling latency of non-RT tasks,
1429 but the average schedule latency is better for non-RT tasks.
1437 work well with Real-Time tasks.  The wakeup_rt tracer was designed
1438 to record the worst case wakeups of RT tasks. Non-RT tasks are
1440 tracing non-RT tasks that are unpredictable will overwrite the
1441 worst case latency of RT tasks (just run the normal wakeup
1444 Since this tracer only deals with RT tasks, we will run this
2057 functions or tasks.