Mail Archives: djgpp/1995/07/10/15:14:27
Charles Sandmann <sandmann AT praline DOT no DOT NeoSoft DOT com> wrote:
> Joel Hunter (jhunter AT kendaco DOT telebyte DOT com> wrote:
>> It seems to me that the stack created for you when you call
>> _go32_allocate_iret_wrapper is never locked....
[SNIP]
>> Just curious, because we know
>> that this code and data will be accessed from within an interrupt...
>Yes, all of these things should be locked. The problem is that when you
>use these routines the C code your call code must be locked and all the data it
>touches must be locked too. This makes writing HW interrupt procedures in
>C in protected mode an iffy proposition if you page at all. So I didn't
>bother. Hey, at least the V2 versions work, unlike the V1 versions!
So true. I wouldn't have gotten nearly this far in V 1.0!!!!
V. 2.0 has behaved like a dream come true.
>If you want to build bullet proof code with HW interrupt handlers and/or
>RMCB's, you really need to write them in GAS, so you can put your variables
>and executable code together, not have to swap stacks, and know exactly what
>needs to be locked.
You're probably right. Unfortunately, this would be difficult for
me, because there is SO MUCH code being executed during the interrupt
it would be an overwhelming task to convert it all to asm.
>Or you can do what DOOM does, and just lock everything, in which case the
>suggested lock calls would be useless :-)
Hmmm....:^) Thanks for the info, Charles.
- Raw text -