Date: Sun, 14 Jun 1998 13:31:07 +0300 (IDT)
From: Eli Zaretskii <eliz AT is DOT elta DOT co DOT il>
To: Shawn Hargreaves <Shawn AT talula DOT demon DOT co DOT uk>
cc: djgpp AT delorie DOT com
Subject: Re: dosmemget and memcpy inside an interrupt handler
In-Reply-To: <R+1jFFAdQDg1Ewc+@talula.demon.co.uk>
Message-ID: <Pine.SUN.3.91.980614133048.6294H-100000@is>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Precedence: bulk


On Thu, 11 Jun 1998, Shawn Hargreaves wrote:

> But the original poster was asking about a _software_ interrupt handler:
> my understanding is that you don't actually need to lock the memory used
> by these, as long as they can only be called by user level programs and
> not by DOS itself...

You can indeed avoid locking a handler of a software interrupt, but
you need a lot of care to do that correctly, especially if the
interrupt is called from the real-mode code.  And since the original
poster didn't post enough info for me to understand in what
environment does their handler need to work, I thought locking advice
is a prudent thing to do.