On 20/05/07, Robert P. J. Day <rpjday@xxxxxxxxxxxxxx> wrote:
as i'm going to be explaining the various contexts to some folks this coming week, i wanted a short list of what was so special about interrupt context (IC), and here's what i've come up with: * not associated with any process, so not allowed to "sleep" in any way * since sleeping is not allowed, kernel preemption is automatically disabled * when servicing a given interrupt, that interrupt is masked out on all processors so interrupt handlers don't have to be re-entrant * however, when servicing a given interrupt, *other* interrupts are still possible unless you explicitly disable them is this a reasonable list? anyone want to add anything else, or correct anything that's not accurate? thanks.
When servicing an interrupt your handler should do as little work as possible (in order to return fast) - top/bottom half split. -- Jesper Juhl <jesper.juhl@xxxxxxxxx> Don't top-post http://www.catb.org/~esr/jargon/html/T/top-post.html Plain text mails only, please http://www.expita.com/nomime.html -- To unsubscribe from this list: send an email with "unsubscribe kernelnewbies" to ecartis@xxxxxxxxxxxx Please read the FAQ at http://kernelnewbies.org/FAQ
