• State Not Answered
  • Locked Locked
  • Replies 14 replies
  • Subscribers 349 subscribers
  • Views 15619 views
  • Users 0 members are here
Options
Related
How was your experience today?
This discussion has been locked.
You can no longer post new replies to this discussion. If you have a question you can start a new discussion

Abort some questions of arm interrupt

josh zhao
Note: This was originally posted on 20th June 2008 at http://forums.arm.com

I try to understand arm interrupt,there are some questions I don't know,
  1.   Why the nested interrupt has to switch out of irq mode to svc mode?  I think  it only pushes the r14_irq into the irq stack.
   2.    The basic difference between a reentrant interrupt handler and a nested interrupt han-dler is that the interrupts are reenabled early on in the reentrant interrupt handler, which can reduce interrupt latency.
    I can't understand that ?

   thanks!
Parents
  • 0
    Note: This was originally posted on 26th June 2008 at http://forums.arm.com

    Sean,

    ...............
    Interrupt nesting: interrupt A can preempt handling of interrupt B; both interrupt A and interrupt B's handlers can be "active" at the same time.

    Re-entrant interrupt: interrupt A can preempt handling of interrupt A; interrupt A's handler can be active concurrently with itself.

    ..................

    hth
    s.

    Hi sim,
        For Interrupt nesting, I don't think interrupt A and interrupt B's handlers can be "active" at the same time. interrupt B must wait for returning by interrupt A if no interrupt occurs.
Reply
  • 0
    Note: This was originally posted on 26th June 2008 at http://forums.arm.com

    Sean,

    ...............
    Interrupt nesting: interrupt A can preempt handling of interrupt B; both interrupt A and interrupt B's handlers can be "active" at the same time.

    Re-entrant interrupt: interrupt A can preempt handling of interrupt A; interrupt A's handler can be active concurrently with itself.

    ..................

    hth
    s.

    Hi sim,
        For Interrupt nesting, I don't think interrupt A and interrupt B's handlers can be "active" at the same time. interrupt B must wait for returning by interrupt A if no interrupt occurs.
Children
No data