Re: [Chicken-hackers] [PATCH] Reschedule when a thread blocked on thread-join! is forcibly resumed

[Jörg F . Wittenberger]

On Jun 2 2016, address@hidden wrote:

> > Am 02.06.2016 um 14:18 schrieb address@hidden:
> > >> AFAICT from past discussions, whether forcing is good, bad, or just 
> > >> a necessary evil is still unclear, and this needs some agreement 
> > >> before we can simply rip out that code. I'm open to removing it in 
> > >> chicken-5, at least, which is where something like a dedicated 
> > >> interrupt handling thread could go should one materialize. If anyone 
> > >> has any thoughts about this, please speak up.
> > >
> > > Threads are and should be optional.
> > >
> > >
> > > ferlix
> >
> > Sure, but how does this relate to the question of forcing the primordial?
>
> It would make a dedicated interrupt-handler thread impossible.

Why?

##sys#force-primordial would become ##sys#force-interrupt-handler-thread or 
alike.

Still local to the scheduler and thus optional.

The only difference would be so far that the thread it unleashes would be 
the signal handler thread (which we could completely control from 
scheduler.scm) instead of the primordial (which is under user control).

Without threads nothing would change.

> felix