summaryrefslogtreecommitdiffstats
path: root/tools/sched
Commit message (Collapse)AuthorAgeFilesLines
* - Add some notes on what is required to run schedgraph.py successfully.arr2004-12-281-0/+11
| | | | | | This was pulled from Jeff Roberson's email to current@ "the other day." Approved by: jeff@
* - For preemption and yield events, we want to skip the next two state eventsjeff2004-12-261-3/+4
| | | | | | | as they are the setrunqueue() and sched_add() calls. Since they happen immediately before the thread is placed on a run queue they would normally dwarf the more informative preemption or yield event and it is implicitly understood that a thread is back on the run queue as part of these events.
* - Call self.checkstamp() in the cpu load parsing functions in case thejeff2004-12-261-0/+4
| | | | timestamp has wrapped.
* - The regexp for the load should have been (/d+), fix this so loads over 9jeff2004-12-261-2/+3
| | | | are properly represented.
* - Add 'schedgraph' a scheduler trace visualization tool written withjeff2004-12-261-0/+1209
python and tkinter. Schedgraph takes input from files produces by ktrdump -ct when KTR_SCHED is compiled into the kernel. The output represents the states of each thread with colored line segments as well as colored points for non-state scheduler events. Each line segment and point is clickable to obtain extra detail.
OpenPOWER on IntegriCloud