From owner-cvs-src@FreeBSD.ORG  Sun Dec 26 03:25:09 2004
Return-Path: <owner-cvs-src@FreeBSD.ORG>
Delivered-To: cvs-src@freebsd.org
Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125])
	by hub.freebsd.org (Postfix) with ESMTP
	id 6ACDE16A4CE; Sun, 26 Dec 2004 03:25:09 +0000 (GMT)
Received: from repoman.freebsd.org (repoman.freebsd.org [216.136.204.115])
	by mx1.FreeBSD.org (Postfix) with ESMTP
	id 4312143D46; Sun, 26 Dec 2004 03:25:09 +0000 (GMT)
	(envelope-from jeff@FreeBSD.org)
Received: from repoman.freebsd.org (localhost [127.0.0.1])
	by repoman.freebsd.org (8.13.1/8.13.1) with ESMTP id iBQ3P9eX087127;
	Sun, 26 Dec 2004 03:25:09 GMT
	(envelope-from jeff@repoman.freebsd.org)
Received: (from jeff@localhost)
	by repoman.freebsd.org (8.13.1/8.13.1/Submit) id iBQ3P9NC087126;
	Sun, 26 Dec 2004 03:25:09 GMT
	(envelope-from jeff)
Message-Id: <200412260325.iBQ3P9NC087126@repoman.freebsd.org>
From: Jeff Roberson <jeff@FreeBSD.org>
Date: Sun, 26 Dec 2004 03:25:08 +0000 (UTC)
To: src-committers@FreeBSD.org, cvs-src@FreeBSD.org,
	cvs-all@FreeBSD.org
X-FreeBSD-CVS-Branch: HEAD
Subject: cvs commit: src/tools/sched schedgraph.py
X-BeenThere: cvs-src@freebsd.org
X-Mailman-Version: 2.1.1
Precedence: list
List-Id: CVS commit messages for the src tree <cvs-src.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/cvs-src>,
	<mailto:cvs-src-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/cvs-src>
List-Post: <mailto:cvs-src@freebsd.org>
List-Help: <mailto:cvs-src-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/cvs-src>,
	<mailto:cvs-src-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Sun, 26 Dec 2004 03:25:09 -0000

jeff        2004-12-26 03:25:08 UTC

  FreeBSD src repository

  Modified files:
    tools/sched          schedgraph.py 
  Log:
   - For preemption and yield events, we want to skip the next two state events
     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.
  
  Revision  Changes    Path
  1.4       +4 -3      src/tools/sched/schedgraph.py