<feed xmlns='http://www.w3.org/2005/Atom'>
<title>src-test2/tools/sched, branch stable/6</title>
<subtitle>FreeBSD source tree</subtitle>
<id>https://cgit-dev.freebsd.org/src-test2/atom?h=stable%2F6</id>
<link rel='self' href='https://cgit-dev.freebsd.org/src-test2/atom?h=stable%2F6'/>
<link rel='alternate' type='text/html' href='https://cgit-dev.freebsd.org/src-test2/'/>
<updated>2005-03-14T11:52:24Z</updated>
<entry>
<title> - ktrace(1) has nothing to do with schedgraph.  Remove that from the</title>
<updated>2005-03-14T11:52:24Z</updated>
<author>
<name>Jeff Roberson</name>
<email>jeff@FreeBSD.org</email>
</author>
<published>2005-03-14T11:52:24Z</published>
<link rel='alternate' type='text/html' href='https://cgit-dev.freebsd.org/src-test2/commit/?id=de4c115cf80f8feaf7cac446586052d5151c30d5'/>
<id>urn:sha1:de4c115cf80f8feaf7cac446586052d5151c30d5</id>
<content type='text'>
   instructions.
</content>
</entry>
<entry>
<title>- Add some notes on what is required to run schedgraph.py successfully.</title>
<updated>2004-12-28T00:49:02Z</updated>
<author>
<name>Andrew R. Reiter</name>
<email>arr@FreeBSD.org</email>
</author>
<published>2004-12-28T00:49:02Z</published>
<link rel='alternate' type='text/html' href='https://cgit-dev.freebsd.org/src-test2/commit/?id=698e6141848fef4672919626825860c92ab3311c'/>
<id>urn:sha1:698e6141848fef4672919626825860c92ab3311c</id>
<content type='text'>
  This was pulled from Jeff Roberson's email to current@ "the other day."

Approved by: jeff@
</content>
</entry>
<entry>
<title> - For preemption and yield events, we want to skip the next two state events</title>
<updated>2004-12-26T03:25:08Z</updated>
<author>
<name>Jeff Roberson</name>
<email>jeff@FreeBSD.org</email>
</author>
<published>2004-12-26T03:25:08Z</published>
<link rel='alternate' type='text/html' href='https://cgit-dev.freebsd.org/src-test2/commit/?id=9a5c9d55e7103acf716cb19b1ca081405afa3928'/>
<id>urn:sha1:9a5c9d55e7103acf716cb19b1ca081405afa3928</id>
<content type='text'>
   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.
</content>
</entry>
<entry>
<title> - Call self.checkstamp() in the cpu load parsing functions in case the</title>
<updated>2004-12-26T02:02:34Z</updated>
<author>
<name>Jeff Roberson</name>
<email>jeff@FreeBSD.org</email>
</author>
<published>2004-12-26T02:02:34Z</published>
<link rel='alternate' type='text/html' href='https://cgit-dev.freebsd.org/src-test2/commit/?id=b0e485185fddd6ee87d332b4d260e6fec31c902b'/>
<id>urn:sha1:b0e485185fddd6ee87d332b4d260e6fec31c902b</id>
<content type='text'>
   timestamp has wrapped.
</content>
</entry>
<entry>
<title> - The regexp for the load should have been (/d+), fix this so loads over 9</title>
<updated>2004-12-26T01:18:49Z</updated>
<author>
<name>Jeff Roberson</name>
<email>jeff@FreeBSD.org</email>
</author>
<published>2004-12-26T01:18:49Z</published>
<link rel='alternate' type='text/html' href='https://cgit-dev.freebsd.org/src-test2/commit/?id=3e16b3e04f49a293c41e120417403220537992e6'/>
<id>urn:sha1:3e16b3e04f49a293c41e120417403220537992e6</id>
<content type='text'>
   are properly represented.
</content>
</entry>
<entry>
<title> - Add 'schedgraph' a scheduler trace visualization tool written with</title>
<updated>2004-12-26T00:13:07Z</updated>
<author>
<name>Jeff Roberson</name>
<email>jeff@FreeBSD.org</email>
</author>
<published>2004-12-26T00:13:07Z</published>
<link rel='alternate' type='text/html' href='https://cgit-dev.freebsd.org/src-test2/commit/?id=dcee3bd3124118af92913daed08cdfcc2a06ed58'/>
<id>urn:sha1:dcee3bd3124118af92913daed08cdfcc2a06ed58</id>
<content type='text'>
   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.
</content>
</entry>
</feed>
