Re: a bullet-point summary of interrupt context

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



my two cents:

* No process context. So, data transfer from/to user space is invalid.

  * not associated with any process, so not allowed to "sleep" in any
way

So, no calling schedule, no taking any semaphores, no calling wait_ functions. Also, allocating memory only with GFP_ATOMIC.

  * 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

This explicit disabling of interrupts can only be done for the local processor.

CMIIW.
Thanks,
- Ratnadeep

[Index of Archives]     [Newbies FAQ]     [Linux Kernel Mentors]     [Linux Kernel Development]     [IETF Annouce]     [Git]     [Networking]     [Security]     [Bugtraq]     [Yosemite]     [MIPS Linux]     [ARM Linux]     [Linux RAID]     [Linux SCSI]     [Linux ACPI]
  Powered by Linux