Xref:	news-dnh.mv.net comp.os.msdos.djgpp:2004
Path:	news-dnh.mv.net!mv!news.sprintlink.net!dfw.nkn.net!usenet
From:	tevans AT fastlane DOT net
Newsgroups:	comp.os.msdos.djgpp
Subject:	Bulletproof interrupt handlers??
Date:	12 Sep 1995 00:14:38 GMT
Organization:	National Knowledge Network
Lines:	25
Reply-To:	tevans AT fastlane DOT net
Nntp-Posting-Host:	fastlane.net
To:	djgpp AT sun DOT soe DOT clarkson DOT edu
Dj-Gateway:	from newsgroup comp.os.msdos.djgpp

  I have been working on writting interrupt handlers for the timer, mouse,
and keyboard for several days now, but I'm still not quite sure exactly
what needs to be done to make them "bulletproof"?  I know that all
stack, code, and data sections that your interrupt handler could possibly
use needs to be locked into memory.  Is that correct?

  Overall, I guess I need to know the best way to guarantee that everything
that I will ever use will be locked into memory.  So far, I have been real
careful to lock the code and data segments used by my handlers, but then
I read that when you allocate a wrapper that that data and stack is not
locked.  Is that correct also?  

  What is the best way to make sure that an interrupt handler, any part of
it including code, data, and stack, will never be swapped out?

  Is it possible to lock all of the code segment that my program uses and
all of my default stack?  If so, what is the easiest way of doing that?

  I don't need the memory that I malloc locked by default, except for the
wrappers for the interrupt handlers.

Thanks for any help.

Terry Evans
tevans AT fastlane DOT net

- Raw text -