From owner-freebsd-hackers Thu Jan 11 3: 9: 0 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from pcs113.sasi.com (samar.sasken.com [164.164.56.2]) by hub.freebsd.org (Postfix) with ESMTP id 2760137B400 for ; Thu, 11 Jan 2001 03:08:40 -0800 (PST) Received: from localhost (pmk@localhost) by pcs113.sasi.com (8.9.3/8.9.3) with ESMTP id QAA01407; Thu, 11 Jan 2001 16:38:06 +0530 X-Authentication-Warning: pcs113.sasi.com: pmk owned process doing -bs Date: Thu, 11 Jan 2001 16:38:06 +0530 (IST) From: Mohana Krishna Penumetcha To: Alfred Perlstein Cc: freebsd-hackers@FreeBSD.ORG Subject: Re: kernel debugging!!! In-Reply-To: <20010111023928.X7240@fw.wintelcom.net> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > Afaik, on i386 you have ~4k of kernel stack, however you have to > realize that driver entry can come from an interrupt generated when > the stack is already nearly exhausted. I'm not really that much > of a driver programmer, but I've heard of people facing this problem > before, solutions varied, but since each driver instance is single > threaded you can pre-allocate via malloc (i think) the space you > need and attach it to the per-driver data structure (softc afaik). i am confused between the kernel stack in kernel space (where ISRs are called) and kernel stack each process has. the UPAGES constant defines the size of process kernel stack. does it define kernel stack in kernel space also?? (fig 3.1, page 51, BSD book) BTW, memory for softc is allocated from the heap in newbus architecture. -- mohan To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message