From owner-freebsd-current Tue Jul 16 11:26:33 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 1FAAE37B401 for ; Tue, 16 Jul 2002 11:26:29 -0700 (PDT) Received: from mail.speakeasy.net (mail11.speakeasy.net [216.254.0.211]) by mx1.FreeBSD.org (Postfix) with ESMTP id 506DB43E64 for ; Tue, 16 Jul 2002 11:26:28 -0700 (PDT) (envelope-from jhb@FreeBSD.org) Received: (qmail 11042 invoked from network); 16 Jul 2002 18:26:27 -0000 Received: from unknown (HELO server.baldwin.cx) ([216.27.160.63]) (envelope-sender ) by mail11.speakeasy.net (qmail-ldap-1.03) with DES-CBC3-SHA encrypted SMTP for ; 16 Jul 2002 18:26:27 -0000 Received: from laptop.baldwin.cx (gw1.twc.weather.com [216.133.140.1]) by server.baldwin.cx (8.11.6/8.11.6) with ESMTP id g6GIQP053687; Tue, 16 Jul 2002 14:26:25 -0400 (EDT) (envelope-from jhb@FreeBSD.org) Message-ID: X-Mailer: XFMail 1.5.2 on FreeBSD X-Priority: 3 (Normal) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit MIME-Version: 1.0 In-Reply-To: <15668.25298.312139.824563@grasshopper.cs.duke.edu> Date: Tue, 16 Jul 2002 14:26:31 -0400 (EDT) From: John Baldwin To: Andrew Gallatin Subject: Re: VOP_GETATTR panic on Alpha Cc: current@freebsd.org, Andrew Kolchoogin , Alfred Perlstein 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 On 16-Jul-2002 Andrew Gallatin wrote: > > 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 */ You can already do if (td->td_ithd != NULL) to do the TD_ITHREAD test. The problem is that this won't work if there is a process on the run queue with a higher priority than the currently running process. -- John Baldwin <>< http://www.FreeBSD.org/~jhb/ "Power Users Use the Power to Serve!" - http://www.FreeBSD.org/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message