Date: Sun, 2 Nov 1997 02:35:05 +0000 (   )
From: "Gurunandan R. Bhat" <grbhat AT unigoa DOT ernet DOT in>
To: Eli Zaretskii <eliz AT is DOT elta DOT co DOT il>
Cc: djgpp AT delorie DOT com
Subject: Re: Tracing the path of Software Interrupts
In-Reply-To: <Pine.SUN.3.91.971102162522.11762A-100000@is>
Message-Id: <Pine.LNX.3.91.971102023229.2612A-100000@aditya.unigoa.ernet.in>
Mime-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Precedence: bulk



On Sun, 2 Nov 1997, Eli Zaretskii wrote:

> 
> On Sat, 1 Nov 1997, Gurunandan R. Bhat wrote:
> 
> > Yes. I will do that and report back. Though from the top of my head I 
> > cannot guess how to detect the *lost* ticks without installing another 
> > int 0x8 handler....
> 
> If you chain, compare to the BIOS clock tick count.  If you don't chain, 
> get the system clock and multiply seconds by 18.2.
> 

Did that. If I install only a PM handler it gets called at *every* tick. 
If I install a PM (first) as well as an RM (later) handler, only the RM
handler seems to be called, **even if I spend substantial amount of time
in PM**.