1 /* -----------------------------------------------------------------------------
3 * (c) The GHC Team, 1995-1999
5 * Interval timer for profiling and pre-emptive scheduling.
7 * ---------------------------------------------------------------------------*/
10 * The interval timer is used for profiling and for context switching in the
11 * threaded build. Though POSIX 1003.1b includes a standard interface for
12 * such things, no one really seems to be implementing them yet. Even
13 * Solaris 2.3 only seems to provide support for @CLOCK_REAL@, whereas we're
14 * keen on getting access to @CLOCK_VIRTUAL@.
16 * Hence, we use the old-fashioned @setitimer@ that just about everyone seems
17 * to support. So much for standards.
23 #include "posix/Itimer.h"
24 #include "Proftimer.h"
27 #include "posix/Select.h"
29 /* As recommended in the autoconf manual */
30 # ifdef TIME_WITH_SYS_TIME
31 # include <sys/time.h>
34 # ifdef HAVE_SYS_TIME_H
35 # include <sys/time.h>
47 * In the threaded RTS, we can't set the virtual timer because the
48 * thread which has the virtual timer might be sitting waiting for a
49 * capability, and the virtual timer only ticks in CPU time.
51 * So, possible solutions:
53 * (1) tick in realtime. Not very good, because this ticker is used for
54 * profiling, and this will give us unreliable time profiling
57 * (2) save/restore the virtual timer around excursions into STG land.
58 * Sounds great, but I tried it and the resolution of the virtual timer
59 * isn't good enough (on Linux) - most of our excursions fall
60 * within the timer's resolution and we never make any progress.
62 * (3) have a virtual timer in every OS thread. Might be reasonable,
63 * because most of the time there is only ever one of these
64 * threads running, so it approximates a single virtual timer.
65 * But still quite bogus (and I got crashes when I tried this).
67 * For now, we're using (1), but this needs a better solution. --SDM
70 #if defined(HAVE_TIMER_CREATE) && defined(HAVE_TIMER_SETTIME)
72 # define USE_TIMER_CREATE
73 # define ITIMER_SIGNAL SIGVTALRM
75 # define TIMER_FLAVOUR CLOCK_REALTIME
77 # define TIMER_FLAVOUR CLOCK_PROCESS_CPUTIME_ID
80 #elif defined(HAVE_SETITIMER)
84 // Oh dear, we have to use SIGALRM if there's no timer_create and
85 // we're using the THREADED_RTS. This leads to problems, see bug #850.
86 # define ITIMER_SIGNAL SIGALRM
87 # define ITIMER_FLAVOUR ITIMER_REAL
89 # define ITIMER_SIGNAL SIGVTALRM
90 # define ITIMER_FLAVOUR ITIMER_VIRTUAL
95 # error No way to set an interval timer.
99 #if defined(USE_TIMER_CREATE)
105 install_vtalrm_handler(TickProc handle_tick)
107 struct sigaction action;
109 action.sa_handler = handle_tick;
111 sigemptyset(&action.sa_mask);
114 // specify SA_RESTART. One consequence if we don't do this is
115 // that readline gets confused by the -threaded RTS. It seems
116 // that if a SIGALRM handler is installed without SA_RESTART,
117 // readline installs its own SIGALRM signal handler (see
118 // readline's signals.c), and this somehow causes readline to go
119 // wrong when the input exceeds a single line (try it).
120 action.sa_flags = SA_RESTART;
125 if (sigaction(ITIMER_SIGNAL, &action, NULL) == -1) {
126 sysErrorBelch("sigaction");
127 stg_exit(EXIT_FAILURE);
132 startTicker(nat ms, TickProc handle_tick)
134 install_vtalrm_handler(handle_tick);
136 #if !defined(THREADED_RTS)
137 timestamp = getourtimeofday();
140 #if defined(USE_TIMER_CREATE)
142 struct itimerspec it;
145 ev.sigev_notify = SIGEV_SIGNAL;
146 ev.sigev_signo = ITIMER_SIGNAL;
148 it.it_value.tv_sec = ms / 1000;
149 it.it_value.tv_nsec = (ms % 1000) * 1000000;
150 it.it_interval = it.it_value;
152 if (timer_create(TIMER_FLAVOUR, &ev, &timer) != 0) {
153 sysErrorBelch("timer_create");
154 stg_exit(EXIT_FAILURE);
157 if (timer_settime(timer, 0, &it, NULL) != 0) {
158 sysErrorBelch("timer_settime");
159 stg_exit(EXIT_FAILURE);
166 it.it_value.tv_sec = ms / 1000;
167 it.it_value.tv_usec = (ms % 1000) * 1000;
168 it.it_interval = it.it_value;
170 if (setitimer(ITIMER_FLAVOUR, &it, NULL) != 0) {
171 sysErrorBelch("setitimer");
172 stg_exit(EXIT_FAILURE);
181 #if defined(USE_TIMER_CREATE)
182 struct itimerspec it;
184 it.it_value.tv_sec = 0;
185 it.it_value.tv_nsec = 0;
186 it.it_interval = it.it_value;
188 if (timer_settime(timer, 0, &it, NULL) != 0) {
189 sysErrorBelch("timer_settime");
190 stg_exit(EXIT_FAILURE);
195 it.it_value.tv_sec = 0;
196 it.it_value.tv_usec = 0;
197 it.it_interval = it.it_value;
199 if (setitimer(ITIMER_FLAVOUR, &it, NULL) != 0) {
200 sysErrorBelch("setitimer");
201 stg_exit(EXIT_FAILURE);
207 /* Currently unused */
209 block_vtalrm_signal(void)
213 sigemptyset(&signals);
214 sigaddset(&signals, ITIMER_SIGNAL);
216 (void) sigprocmask(SIG_BLOCK, &signals, NULL);
220 unblock_vtalrm_signal(void)
224 sigemptyset(&signals);
225 sigaddset(&signals, ITIMER_SIGNAL);
227 (void) sigprocmask(SIG_UNBLOCK, &signals, NULL);
231 /* gettimeofday() takes around 1us on our 500MHz PIII. Since we're
232 * only calling it 50 times/s, it shouldn't have any great impact.
235 getourtimeofday(void)
238 gettimeofday(&tv, (struct timezone *) NULL);
239 // cast to lnat because nat may be 64 bit when int is only 32 bit
240 return ((lnat)tv.tv_sec * 1000 / RtsFlags.MiscFlags.tickInterval +
241 (lnat)tv.tv_usec / (RtsFlags.MiscFlags.tickInterval * 1000));