Machine-translated by Google. Questions are authored in English.
Top

Discussion

A handler must not block on a kernel object because

  • A.the handler has no stack of its own to save
  • B.there is no task context to place in the blocked state
  • C.interrupts are disabled throughout every handler
  • D.the kernel's own tick is unavailable for the duration of a handler

Answer: B

Correct answer: there is no task context to place in the blocked state

Blocking means recording that a task is waiting and scheduling another, and a handler is not a task - it has no control block and no state to save. The kernel therefore provides from-interrupt variants that never block, and calling the ordinary ones from a handler faults or hangs.

No comment is present. Be the first to comment.
Loading…

Post your comment

Please log in or register to post a comment.