My Concern is towards RT IRQ's; Does RTLinux provides any Interrupt Levels/Priorities ? If Yes, then will a high priority Interrupt preempt over a low priority interrupt before the latter's completion ? [May be Bottom Half's being queued in this scenario]
Can somebody enlighten more on these ? - Tom -----Original Message----- From: Dresner, Norman A. [mailto:[EMAIL PROTECTED]] Sent: Wednesday, March 20, 2002 7:10 PM To: '[EMAIL PROTECTED]' Subject: RE: [rtl] Nested Interrupt Handlers ? Well, Victor or one of his colleagues can answer this question better than I can, but AFAIK, the answer is a qualified "Yes, but..." The largest part of the "BUT" is that it will hold any normal Linux interrupts until after the last real-time task has ceded control of the CPU back to its scheduler. Other than that, I believe -- and it's only a belief because I've never tried it -- that it is possible to nest RT IRQ's. Norm -----Original Message----- From: Sudhir S [mailto:[EMAIL PROTECTED]] Sent: Wednesday, March 20, 2002 1:21 AM To: [EMAIL PROTECTED] Subject: [rtl] Nested Interrupt Handlers ? Does RTLinux allows further interrupts to occur even when servicing an existing interrupt ? - Tom -- Ageing is Inevitable; Maturing is Optional -- [rtl] --- To unsubscribe: echo "unsubscribe rtl" | mail [EMAIL PROTECTED] OR echo "unsubscribe rtl <Your_email>" | mail [EMAIL PROTECTED] -- For more information on Real-Time Linux see: http://www.rtlinux.org/ -- [rtl] --- To unsubscribe: echo "unsubscribe rtl" | mail [EMAIL PROTECTED] OR echo "unsubscribe rtl <Your_email>" | mail [EMAIL PROTECTED] -- For more information on Real-Time Linux see: http://www.rtlinux.org/ -- [rtl] --- To unsubscribe: echo "unsubscribe rtl" | mail [EMAIL PROTECTED] OR echo "unsubscribe rtl <Your_email>" | mail [EMAIL PROTECTED] -- For more information on Real-Time Linux see: http://www.rtlinux.org/
