The eCos, QNX, ChorusOs irq handling API

[Valette Eric]

gregory.menke at gsfc.nasa.gov wrote:

> I would prefer to keep the semantics of setting a vector and then
> allowing the interrupt itself to be disabled- the RTEMS task interrupt
> level provides a means of controlling the set of enabled interrupts on
> a per task basis.  Its not been useful to me yet, but I'd hate to
> loose functionality in an enhancement.

I'm not sure I understand what you mean. If processor IRQ enabling level 
is part of a SR and saved as part of the context switch, fine. However, 
allowing such things, makes it very difficult to guaranty any interrupt 
latency... Besides, I do not see what in the current new API prevents 
that...


-- 
    __
   /  `                   	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