Date: Fri, 29 Jun 2001 01:02:16 -0700 From: Terry Lambert <tlambert2@mindspring.com> To: vinu pattery <vinupattery@hotmail.com> Cc: freebsd-hackers@FreeBSD.ORG Subject: Re: interrupt on to Kernel Message-ID: <3B3C3608.FF89B31D@mindspring.com> References: <LAW2-F146DbH8J0sca000004399@hotmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
vinu pattery wrote: > > Could some body let me know, how to hack the FReeBSD kernel > to learn the exact sequence of steps which happen when the > device driver interrupts the FreeBSD Kernel for resources. > Is there a trace debugger available, with which i can find > out the steps. It's not clear what you mean by "interrupt the Kernel for resources"... the only resources you can grab at interrupt are things that you pre-allocated, things you get from a zalloci() from a previously established interrupt safe zone in the zone allocator (e.g. mbufs), and CPU time. As far as your tracing question: "man ddb"; you can set breakpoints in the kernel, and step through them. You probably _don't_ want to do this in an interrupt routine, but you could. You may want to look at the FreeBSD Handbook, and at the device driver and bus articles on: http://www.daemonnews.org/ There is also a (fairly old) "Device Driver Writer's Guide": http://freebsd.dei.uc.pt/tutorials/ddwg/ddwg.html -- Terry 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?3B3C3608.FF89B31D>