Lines Matching refs:tasks

535         Traces all tasks as an average developer would expect.
540         RT tasks (as the current "wakeup" does). This is useful
541         for those interested in wake up timings of RT tasks.
1391 Now for non Real-Time tasks, this can be arbitrary. But tracing
1431 Non Real-Time tasks are not that interesting. A more interesting
1432 trace is to concentrate only on Real-Time tasks.
1440 latency". I stress the point that this is about RT tasks. It is
1441 also important to know the scheduling latency of non-RT tasks,
1442 but the average schedule latency is better for non-RT tasks.
1450 work well with Real-Time tasks.  The wakeup_rt tracer was designed
1451 to record the worst case wakeups of RT tasks. Non-RT tasks are
1453 tracing non-RT tasks that are unpredictable will overwrite the
1454 worst case latency of RT tasks (just run the normal wakeup
1457 Since this tracer only deals with RT tasks, we will run this
2093 functions or tasks.