Why _ThreadProcessSignalsFromIrq() in new exception processing?

[Valette Eric]

Sergei Organov wrote:
> Could somebody please explain what is the purpose of call to
> _ThreadProcessSignalsFromIrq() in the new-exception-processing from the
> shared_raw_irq_code_entry? Should it be implemented in the old exception
> processing for proper RTEMS behavior?

I guess, you will not get fully working posix signaling without doing 
this (look at pthreadkill or signalsend). This block of code is used to 
trigger a processing on the newly switched thread that end up calling 
_API_extensions_Run_postswitch.

NB : The code was already there on ix86 when I implemented the new 
exception model I just keeped it. When going to PPC, the call was 
missing so I added it.

In most advanced RTOS, there are things that should be done on the 
current thread that have been trigerred as the result of a system call 
from isr and that must be deffered until the thread runs again... In 
that case having a context is very usefull. I wanted to use it to 
implement a call to debugger from keyboard in particular....


> BTW, is the new exception processing model documented somewhere as this call
> is not the only violation of the old documentation describing how
> exceptions/interrupts should be handled by BSPs?

If documentation is not accurate, trust the code. If old code is broken, 
do not stick to it :-)


-- 
    __
   /  `                   	Eric Valette
  /--   __  o _.          	6 rue Paul Le Flem
(___, / (_(_(__         	35740 Pace

Tel: +33 (0)2 99 85 26 76	Fax: +33 (0)2 99 85 26 76
E-mail: eric.valette at free.fr