Date: Fri, 24 Sep 2004 13:50:08 -0400 From: John Baldwin <jhb@FreeBSD.org> To: "M. Warner Losh" <imp@bsdimp.com> Cc: cvs-all@FreeBSD.org Subject: Re: cvs commit: src/sys/dev/fdc fdc.c fdcvar.h Message-ID: <200409241350.08480.jhb@FreeBSD.org> In-Reply-To: <20040923.194549.60785228.imp@bsdimp.com> References: <200409231923.40285.jhb@FreeBSD.org> <200409232135.31918.jhb@FreeBSD.org> <20040923.194549.60785228.imp@bsdimp.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On Thursday 23 September 2004 09:45 pm, M. Warner Losh wrote: > In message: <200409232135.31918.jhb@FreeBSD.org> > > John Baldwin <jhb@FreeBSD.org> 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 <jhb@FreeBSD.org> <>< http://www.FreeBSD.org/~jhb/ "Power Users Use the Power to Serve" = http://www.FreeBSD.org
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?200409241350.08480.jhb>