From owner-freebsd-current  Sat Jul  6  7:34:16 2002
Delivered-To: freebsd-current@freebsd.org
Received: from mx1.FreeBSD.org (mx1.FreeBSD.org [216.136.204.125])
	by hub.freebsd.org (Postfix) with ESMTP id AC93D37B400
	for <freebsd-current@freebsd.org>; Sat,  6 Jul 2002 07:34:14 -0700 (PDT)
Received: from duke.cs.duke.edu (duke.cs.duke.edu [152.3.140.1])
	by mx1.FreeBSD.org (Postfix) with ESMTP id B060B43E4A
	for <freebsd-current@freebsd.org>; Sat,  6 Jul 2002 07:34:13 -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 KAA15431;
	Sat, 6 Jul 2002 10:34:13 -0400 (EDT)
Received: (from gallatin@localhost)
	by grasshopper.cs.duke.edu (8.11.6/8.9.1) id g66EXhP33398;
	Sat, 6 Jul 2002 10:33:43 -0400 (EDT)
	(envelope-from gallatin@cs.duke.edu)
From: Andrew Gallatin <gallatin@cs.duke.edu>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Message-ID: <15654.65479.31155.182179@grasshopper.cs.duke.edu>
Date: Sat, 6 Jul 2002 10:33:43 -0400 (EDT)
To: Julian Elischer <julian@elischer.org>
Cc: freebsd-current@freebsd.org
Subject: Re: more on dumping
In-Reply-To: <Pine.BSF.4.21.0207052242550.16316-100000@InterJet.elischer.org>
References: <15654.31389.772589.952477@grasshopper.cs.duke.edu>
	<Pine.BSF.4.21.0207052242550.16316-100000@InterJet.elischer.org>
X-Mailer: VM 6.75 under 21.1 (patch 12) "Channel Islands" XEmacs Lucid
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
List-ID: <freebsd-current.FreeBSD.ORG>
List-Archive: <http://docs.freebsd.org/mail/> (Web Archive)
List-Help: <mailto:majordomo@FreeBSD.ORG?subject=help> (List Instructions)
List-Subscribe: <mailto:majordomo@FreeBSD.ORG?subject=subscribe%20freebsd-current>
List-Unsubscribe: <mailto:majordomo@FreeBSD.ORG?subject=unsubscribe%20freebsd-current>
X-Loop: FreeBSD.ORG


Julian Elischer writes:
 > 
 > 
 > On Sat, 6 Jul 2002, Andrew Gallatin wrote:
 > 
 > > 
 > > 
 > > OK, current is really confusing me.  When we are panic'ing and syncing
 > > disks, how are we supposed to come back to the current thread which
 > > caused the dump after we do an mi_switch() to allow an interrupt
 > > thread to run?
 > > 
 > 
 > It depends.
 > 
 > the previous thread should have been put back onto the run queue
 > before the interrupt thread was scheduled.

Could it have anything to do with interrupt preemption being disabled on
alpha & enabled on i386?

Drew

To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message