Date: Thu, 11 Jan 2001 03:10:49 -0800 From: Alfred Perlstein <bright@wintelcom.net> To: Mohana Krishna Penumetcha <pmk@sasi.com> Cc: freebsd-hackers@FreeBSD.ORG Subject: Re: kernel debugging!!! Message-ID: <20010111031049.Y7240@fw.wintelcom.net> In-Reply-To: <Pine.LNX.4.10.10101111621480.1340-100000@pcs113.sasi.com>; from pmk@sasi.com on Thu, Jan 11, 2001 at 04:38:06PM %2B0530 References: <20010111023928.X7240@fw.wintelcom.net> <Pine.LNX.4.10.10101111621480.1340-100000@pcs113.sasi.com>
next in thread | previous in thread | raw e-mail | index | archive | help
* Mohana Krishna Penumetcha <pmk@sasi.com> [010111 03:08] wrote: > > > > 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. I'm pretty sure interrupts are piggybacked on the user-kernel-stack. How about trying the simple printf idea and letting us know if that works? -- -Alfred Perlstein - [bright@wintelcom.net|alfred@freebsd.org] "I have the heart of a child; I keep it in a jar on my desk." To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20010111031049.Y7240>