From owner-freebsd-current Mon Feb 11 19:34:22 2002 Delivered-To: freebsd-current@freebsd.org Received: from newman2.bestweb.net (newman2.bestweb.net [209.94.102.67]) by hub.freebsd.org (Postfix) with ESMTP id 5D4A937B50D; Mon, 11 Feb 2002 18:18:35 -0800 (PST) Received: from okeeffe.bestweb.net (okeefe.bestweb.net [209.94.100.110]) by newman2.bestweb.net (Postfix) with ESMTP id 0A00623109; Mon, 11 Feb 2002 21:17:47 -0500 (EST) Received: by okeeffe.bestweb.net (Postfix, from userid 0) id 4103A9F367; Mon, 11 Feb 2002 21:12:31 -0500 (EST) Date: Sat, 9 Feb 2002 10:42:53 -0800 (PST) From: Julian Elischer To: Bruce Evans Cc: bde@freebsd.org, FreeBSD current users Subject: Re: "fast" interrupt handler threads. Message-Id: <20020212021231.4103A9F367@okeeffe.bestweb.net> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Thanks On Sun, 10 Feb 2002, Bruce Evans wrote: > > Yes, anything that reaches doreti checks for ASTs and runs userret() if > necessary and possible (only for returns to user mode). > > Hmm, this check seems to be inadequate for fast interrupts. There is > no check for rescheduling if the return is to kernel mode. Do you plan on fixing anything you find wrong here? > > Bruce > > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message