From owner-cvs-src@FreeBSD.ORG Tue Mar 14 23:30:41 2006 Return-Path: X-Original-To: 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 C193416A41F; Tue, 14 Mar 2006 23:30:41 +0000 (UTC) (envelope-from davidxu@freebsd.org) Received: from freefall.freebsd.org (freefall.freebsd.org [216.136.204.21]) by mx1.FreeBSD.org (Postfix) with ESMTP id 89BC543D46; Tue, 14 Mar 2006 23:30:41 +0000 (GMT) (envelope-from davidxu@freebsd.org) Received: from localhost.my.domain (root@localhost [127.0.0.1]) by freefall.freebsd.org (8.13.4/8.13.4) with ESMTP id k2ENUeMH011997; Tue, 14 Mar 2006 23:30:41 GMT (envelope-from davidxu@freebsd.org) From: David Xu To: John Baldwin Date: Wed, 15 Mar 2006 07:30:36 +0800 User-Agent: KMail/1.8.2 References: <200603140400.k2E40LiR095530@repoman.freebsd.org> <200603140825.40761.jhb@freebsd.org> In-Reply-To: <200603140825.40761.jhb@freebsd.org> MIME-Version: 1.0 Content-Disposition: inline Message-Id: <200603150730.36818.davidxu@freebsd.org> Content-Type: text/plain; charset="iso-8859-15" Content-Transfer-Encoding: 7bit Cc: cvs-src@freebsd.org, src-committers@freebsd.org, cvs-all@freebsd.org Subject: Re: cvs commit: src/sys/kern kern_exit.c kern_thread.c X-BeenThere: cvs-src@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: CVS commit messages for the src tree List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 14 Mar 2006 23:30:41 -0000 On Tuesday 14 March 2006 21:25, John Baldwin wrote: > > On Monday 13 March 2006 11:00 pm, David Xu wrote: > > davidxu 2006-03-14 04:00:21 UTC > > > > FreeBSD src repository > > > > Modified files: > > sys/kern kern_exit.c kern_thread.c > > Log: > > 1. Count last time slice, this intends to fix > > "calcru: runtime went backwards" bug for threaded process. > > 2. Add comment about possible logical problem with scheduler. > > > > MFC after: 3 days > > Great! Thanks for testing this! > > I was very upset, and forgot to put your name in the log, apologize. Note that because the thread has detached itself from scheduler, calling PROC_UNLOCK in theory is not safe, so I have moved up this patch code a bit. David Xu