From owner-freebsd-hackers Thu Sep 10 14:17:45 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id OAA28872 for freebsd-hackers-outgoing; Thu, 10 Sep 1998 14:17:45 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from sumatra.americantv.com (sumatra.americantv.com [207.170.17.37]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id OAA28862 for ; Thu, 10 Sep 1998 14:17:42 -0700 (PDT) (envelope-from jlemon@americantv.com) Received: from right.PCS (right.PCS [148.105.10.31]) by sumatra.americantv.com (8.8.5/8.8.5) with ESMTP id QAA09507; Thu, 10 Sep 1998 16:17:32 -0500 (CDT) Received: (from jlemon@localhost) by right.PCS (8.6.13/8.6.4) id QAA14325; Thu, 10 Sep 1998 16:17:01 -0500 Message-ID: <19980910161701.54888@right.PCS> Date: Thu, 10 Sep 1998 16:17:01 -0500 From: Jonathan Lemon To: zhihuizhang Cc: hackers Subject: Re: curproc References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.61.1 In-Reply-To: ; from zhihuizhang on Sep 09, 1998 at 03:21:27PM -0400 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sep 09, 1998 at 03:21:27PM -0400, zhihuizhang wrote: > > curproc refers to the proc structure of the current running process. When > can the value of curproc be NULL? I see many !curproc in the source code. > There must be a running process at any time. ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ Not true; all processes may be idle, and the cpu is executing the idle loop. If an interrupt occurs, then there is no process context. -- Jonathan To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message