From owner-cvs-all Mon Oct 1 15:29:46 2001 Delivered-To: cvs-all@freebsd.org Received: from mail.wrs.com (unknown-1-11.windriver.com [147.11.1.11]) by hub.freebsd.org (Postfix) with ESMTP id 6F18437B407; Mon, 1 Oct 2001 15:29:41 -0700 (PDT) Received: from laptop.baldwin.cx ([147.11.46.209]) by mail.wrs.com (8.9.3/8.9.1) with ESMTP id PAA16004; Mon, 1 Oct 2001 15:29:35 -0700 (PDT) Message-ID: X-Mailer: XFMail 1.4.0 on FreeBSD X-Priority: 3 (Normal) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit MIME-Version: 1.0 In-Reply-To: <200110012226.f91MQmm44174@freefall.freebsd.org> Date: Mon, 01 Oct 2001 15:29:15 -0700 (PDT) From: John Baldwin To: John Baldwin Subject: RE: cvs commit: src/sys/alpha/alpha interrupt.c Cc: cvs-all@FreeBSD.org, cvs-committers@FreeBSD.org Sender: owner-cvs-all@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG On 01-Oct-01 John Baldwin wrote: > jhb 2001/10/01 15:26:48 PDT > > Modified files: > sys/alpha/alpha interrupt.c > Log: > Sigh, statclock_process() takes a KSE instead of a thread for its first > argument. Grrr, why does statclock_process() take a KSE, and hardclock_process() take a thread? Is consistency too much to ask? Also, the panic message in the KASSERT() in statclock_process() (td != curthread) implies that statclock_proceess() takes a thread. The panic message should be 'ke != curkse' instead if it stays using kse's. Personally, I think *clock_process() should both take threads and should be renamed *clock_thread(). -- John Baldwin -- http://www.FreeBSD.org/~jhb/ PGP Key: http://www.baldwin.cx/~john/pgpkey.asc "Power Users Use the Power to Serve!" - http://www.FreeBSD.org/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe cvs-all" in the body of the message