Date: Tue, 16 Jul 2002 14:15:46 -0400 (EDT) From: Andrew Gallatin <gallatin@cs.duke.edu> To: Alfred Perlstein <bright@mu.org> Cc: Andrew Kolchoogin <andrew@snark.rinet.ru>, current@freebsd.org Subject: Re: VOP_GETATTR panic on Alpha Message-ID: <15668.25298.312139.824563@grasshopper.cs.duke.edu> In-Reply-To: <20020716181005.GW77219@elvis.mu.org> References: <xzpele33kq0.fsf@flood.ping.uio.no> <20020716145107.GA69162@snark.rinet.ru> <15668.23528.719956.574605@grasshopper.cs.duke.edu> <20020716181005.GW77219@elvis.mu.org>
next in thread | previous in thread | raw e-mail | index | archive | help
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
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?15668.25298.312139.824563>