Date: Mon, 27 Nov 2000 10:41:48 +1030 From: Greg Lehey <grog@lemis.com> To: Jake Burkholder <jburkhol@home.com> Cc: smp@FreeBSD.ORG Subject: Re: BSD/OS interrupt code Message-ID: <20001127104147.B27186@echunga.lemis.com> In-Reply-To: <20001126220749.BFB35BA7A@io.yi.org>; from jburkhol@home.com on Sun, Nov 26, 2000 at 02:07:49PM -0800 References: <20001126220749.BFB35BA7A@io.yi.org>
next in thread | previous in thread | raw e-mail | index | archive | help
On Sunday, 26 November 2000 at 14:07:49 -0800, Jake Burkholder wrote: > Hi, > > If anyone with access to the BSD/OS code is interested, I've written > a little program that runs their interrupt stub code generator in > userland. You can then abort(); and disassemble the stub from > the core dump to look at the code all in one piece. Makes it much > easier to follow. > > In case you haven't looked, their interrupt handlers are generated > by bcopy-ing various blocks of assembler code into an array at > runtime, and then poking in arguments and relocating branches. Interesting. I was wondering whether something similar would be a good idea. On the other hand, We don't waste much space by having multiple alternate stubs. What's your feeling? Greg -- Finger grog@lemis.com for PGP public key See complete headers for address and phone numbers To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-smp" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20001127104147.B27186>