[coyotos-dev] Status and roadmap

[Sam Mason]

On Fri, Jan 19, 2007 at 10:29:16AM -0500, Jonathan Adams wrote:
> On Fri, 2007-01-19 at 14:28 +0000, Sam Mason wrote:
> > One thing that worries me now is where the kernel gets the memory to
> > "synthesize a message to be delivered" when the userland scheduler is
> > activated.  In fact where does this memory come from in the general
> > case?
> 
> The message is a "short" message, which any non-blocked FCRB can receive
> without needing additional storage.

OK, I've just noticed the "handler" FCRB in the process state.  In the
non-activated case the kernel will dispatch to this as normal.  The
Activated case has the strange wording that I quoted above that doesn't
make sense to me.

What happens if a process has designated itself as its exception handler
and faults in a non-activated state, then subsequently faults in the
activated state while handling the non-activated fault.  Does the FCRB
get overwritten by the activated fault, and the previous message get
lost?  Potentially confusing the handler when it tries to resume itself
after handling the exception it recieved while activated.


  Sam