From owner-cvs-src@FreeBSD.ORG Fri Sep 24 19:14:36 2004 Return-Path: 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 6ACC716A4CE for ; Fri, 24 Sep 2004 19:14:36 +0000 (GMT) Received: from mail6.speakeasy.net (mail6.speakeasy.net [216.254.0.206]) by mx1.FreeBSD.org (Postfix) with ESMTP id 346B743D53 for ; Fri, 24 Sep 2004 19:14:36 +0000 (GMT) (envelope-from jhb@FreeBSD.org) Received: (qmail 1831 invoked from network); 24 Sep 2004 19:14:35 -0000 Received: from dsl027-160-063.atl1.dsl.speakeasy.net (HELO server.baldwin.cx) ([216.27.160.63]) (envelope-sender ) encrypted SMTP for ; 24 Sep 2004 19:14:35 -0000 Received: from [10.50.40.210] (gw1.twc.weather.com [216.133.140.1]) (authenticated bits=0) by server.baldwin.cx (8.12.11/8.12.11) with ESMTP id i8OJEVsF019871; Fri, 24 Sep 2004 15:14:32 -0400 (EDT) (envelope-from jhb@FreeBSD.org) From: John Baldwin To: "M. Warner Losh" Date: Fri, 24 Sep 2004 13:50:08 -0400 User-Agent: KMail/1.6.2 References: <200409231923.40285.jhb@FreeBSD.org> <200409232135.31918.jhb@FreeBSD.org> <20040923.194549.60785228.imp@bsdimp.com> In-Reply-To: <20040923.194549.60785228.imp@bsdimp.com> MIME-Version: 1.0 Content-Disposition: inline Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Message-Id: <200409241350.08480.jhb@FreeBSD.org> X-Spam-Checker-Version: SpamAssassin 2.63 (2004-01-11) on server.baldwin.cx cc: cvs-src@FreeBSD.org cc: src-committers@FreeBSD.org cc: cvs-all@FreeBSD.org Subject: Re: cvs commit: src/sys/dev/fdc fdc.c fdcvar.h X-BeenThere: cvs-src@freebsd.org X-Mailman-Version: 2.1.1 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: Fri, 24 Sep 2004 19:14:36 -0000 On Thursday 23 September 2004 09:45 pm, M. Warner Losh wrote: > In message: <200409232135.31918.jhb@FreeBSD.org> > > John Baldwin writes: > : What about someone else's interrupt preempting you? > > Do others sleep on the thread pointer? Are there other wakeups in the > system that could wake up the msleep than in the exit1() code? > > Warner There are other wakeups on the proc pointer (not thread) for things like PPWAIT but kthread's don't use PPWAIT (vfork(2) semantics basically). However, the ambiguity there is why I would like to change that interface so that kthread_exit() takes a condition variable as a pointer perhaps. -- John Baldwin <>< http://www.FreeBSD.org/~jhb/ "Power Users Use the Power to Serve" = http://www.FreeBSD.org