Xref: news-dnh.mv.net comp.os.msdos.djgpp:4167
Path: news-dnh.mv.net!mv!news.sprintlink.net!newsfeed.internetmci.com!EU.net!Norway.EU.net!nntp.uio.no!news.vu.lt!santaka.sc-uni.ktu.lt!algikun
From: Martynas Kunigelis <algikun AT santaka DOT sc-uni DOT ktu DOT lt>
Newsgroups: comp.os.msdos.djgpp
Subject: Locking the HW intr. handlers
Date: Sun, 7 Jan 1996 19:03:24 +0200
Organization: LITNET
Lines: 25
Message-ID: <Pine.HPP.3.91.960107185206.11264A-100000@santaka.sc-uni.ktu.lt>
NNTP-Posting-Host: santaka.sc-uni.ktu.lt
To: djgpp AT delorie DOT com
DJ-Gateway: from newsgroup comp.os.msdos.djgpp


after reading messages about cwsdpmi 9 and the interrupt handlers causing 
page faults I have the following question to C. Sandmann: suppose I don't 
use _go32_allocate_iret_wrapper but write my own intr. handler in assembler
and give it the right DS by updating its code directly. Do I still have to do 
any locking or is code segment (text section) already locked in djgpp? I 
mean is any peace of *code* ever being paged out? If so, how do I lock a 
peace of memory where my handler resides? 

thanx in advance, 
Martynas

P.S.: BTW, has anyone read my suggestions about rewriting the libraries 
and startup files to be compatible with the register calling conventions?
Or maybe everyone thinks its just not worth anything? Where are you, 
djgpp gurus? If noone wants to do it, I can try to do it myself... 
Anyway, hope to hear something about it from you, people. (Come on, 
Sandmann!) Luv ya all, djgpp rules!!! 

+---------------------------------+--------------------------------+
| Martynas Kunigelis              | e-mail: algikun AT santaka DOT ktu DOT lt |
| Kaunas University of Technology | "use your imagination, Beavis!"|
| Informatics faculty student     |  Butt-head, 1995               |
+---------------------------------+--------------------------------+