From owner-freebsd-current Tue Jul 16 11:16:24 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 EF3AF37B400 for ; Tue, 16 Jul 2002 11:16:19 -0700 (PDT) Received: from duke.cs.duke.edu (duke.cs.duke.edu [152.3.140.1]) by mx1.FreeBSD.org (Postfix) with ESMTP id 9ECBF43E64 for ; Tue, 16 Jul 2002 11:16:18 -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 OAA21200; Tue, 16 Jul 2002 14:16:16 -0400 (EDT) Received: (from gallatin@localhost) by grasshopper.cs.duke.edu (8.11.6/8.9.1) id g6GIFkk51922; Tue, 16 Jul 2002 14:15:46 -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: <15668.25298.312139.824563@grasshopper.cs.duke.edu> Date: Tue, 16 Jul 2002 14:15:46 -0400 (EDT) To: Alfred Perlstein Cc: Andrew Kolchoogin , current@freebsd.org Subject: Re: VOP_GETATTR panic on Alpha In-Reply-To: <20020716181005.GW77219@elvis.mu.org> References: <20020716145107.GA69162@snark.rinet.ru> <15668.23528.719956.574605@grasshopper.cs.duke.edu> <20020716181005.GW77219@elvis.mu.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: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Alfred Perlstein writes: > > We need to somehow let only interrupt threads and the panic'ed process > > run after a panic. I have no idea how to do this in a clean, > > low-impact way. > > > > Drew > > > > PS: I was trying to make crashdumps fail on x86 by increasing HZ. But > > I cannot. I have no idea why this only happens on alpha. > > um, psuedocode... > > for ithreads, td->td_flags |= TD_ITHREAD > for panicing thread, td->td_flags |= TD_INPANIC > > if ((cold || panicstr) && (td->td_flags & (TD_ITHREAD|TD_INPANIC)) != 0) { > I have no idea what's planned for td_flags. Is stealing 2 values for this use acceptable? I didn't consider touching the flags to be lightweight.. If so, I was thinking more like #define TDF_PANICSCHED 0x000002 /* may be scheduled during/after a panic */ Drew To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message