This is the mail archive of the
cygwin-developers@cygwin.com
mailing list for the Cygwin project.
Re: Improving setitimer resolution
- From: Christopher Faylor <cgf at redhat dot com>
- To: cygwin-developers at cygwin dot com
- Date: Thu, 17 Jul 2003 00:08:20 -0400
- Subject: Re: Improving setitimer resolution
- References: <3.0.5.32.20030716230550.00807900@mail.attbi.com>
- Reply-to: cygwin-developers at cygwin dot com
On Wed, Jul 16, 2003 at 11:05:50PM -0400, Pierre A. Humblet wrote:
>I am trying to improve the resolution of the Cygwin timers
>(setitimer, alarm, ualarm) by using the multimedia timers,
>which have 1 ms resolution.
What is different about using multimedia timers here? I had to abandon
them for settimeofday due to the fact that suspending the computer caused
timing anomalies.
>Incidentally how-signals-work says
>"After determining that sigsave is available, setup_handler will take one
>of two routes, depending on whether the main thread is executing in the
>cygwin DLL or is currently in "user" code. We'll discuss the cygwin DLL
>case first."
>Is the second case discussed?
No. It's simple though. SetThreadContext is used to force a call to
the signal handler which then returns to the location where the signal
happened.
cgf