Re: scheduler event-types

(Correction to previous message: where I wrote "asynchronous VM events"
I meant "asynchronous VM interrupts".)

I looked at this some more and I've changed my mind. The current solution
maps signals queued by name to OS signal numbers on resumption, but leaves
signals queued by number alone, even if the number refers to a different
POSIX signal in the new system. This behavior would be hard to maintain
if we move signal queues and the interrupt handler to the runtime system.

That leaves keeping a count of threads waiting on signals, or keeping a
count of threads that promise to be waiting on some unspecified interrupt
(this is Roderic's proposal as I understand it).

Regards,
Will