From owner-freebsd-alpha Thu Sep 5 10:35:11 2002 Delivered-To: freebsd-alpha@freebsd.org Received: from mx1.FreeBSD.org (mx1.FreeBSD.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 2148937B401; Thu, 5 Sep 2002 10:35:10 -0700 (PDT) Received: from duke.cs.duke.edu (duke.cs.duke.edu [152.3.140.1]) by mx1.FreeBSD.org (Postfix) with ESMTP id D6D5043E65; Thu, 5 Sep 2002 10:35:08 -0700 (PDT) (envelope-from gallatin@cs.duke.edu) Received: from grasshopper.cs.duke.edu (grasshopper.cs.duke.edu [152.3.145.30]) by duke.cs.duke.edu (8.9.3/8.9.3) with ESMTP id NAA02783; Thu, 5 Sep 2002 13:35:08 -0400 (EDT) Received: (from gallatin@localhost) by grasshopper.cs.duke.edu (8.11.6/8.9.1) id g85HYcC58349; Thu, 5 Sep 2002 13:34:38 -0400 (EDT) (envelope-from gallatin@cs.duke.edu) From: Andrew Gallatin MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-ID: <15735.38318.66517.366474@grasshopper.cs.duke.edu> Date: Thu, 5 Sep 2002 13:34:38 -0400 (EDT) To: jhb@freebsd.org Cc: freebsd-alpha@freebsd.org Subject: ithread preemption X-Mailer: VM 6.75 under 21.1 (patch 12) "Channel Islands" XEmacs Lucid Sender: owner-freebsd-alpha@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org I've forgotten -- What are the symptoms of ithread preemption causing troubles on alpha? I have one (probably dumb) idea: Is the ithread preemption code guaranteed to switch back to the preempted thread when the ithread completes or blocks? And continue through to the end of the interrupt dispatch code, returning back to the palcode? Eg, I'm wondering if it could it have anything to do with continuing to run at IPL_IO when we shouldn't be (like running a normal process at that priority that the scheduler happened to run by mistake). Thanks, Drew To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-alpha" in the body of the message