Re: Why can't we sleep in an ISR?

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

 



On Mon, 2007-05-14 at 12:42 +0530, Learning Linux wrote:
[...]
> > On the other hand, when you sleep in a given context, the scheduler is
> > invoked. That means that the ISR routine would be replaced by a process
> > from the scheduler's queue(s). But how would you ever know to reschedule
> > the ISR? After all, it is asynchronous.
> 
> Uh, this is what I have my doubt about. Yes, the scheduler may try to
> replace the current process (already interrupted by the ISR) with

The interrupt doesn't interrupt a "process" as such but it interrupts
the kernel itself.
And it is totally random and irrelevant which process (or tasklet or
work-queue or kernel-thread or whatever) is running right now since the
interrupt simply indicates some event from some piece of hardware.

> another process.

	Bernd
-- 
Firmix Software GmbH                   http://www.firmix.at/
mobil: +43 664 4416156                 fax: +43 1 7890849-55
          Embedded Linux Development and Services


--
To unsubscribe from this list: send an email with
"unsubscribe kernelnewbies" to ecartis@xxxxxxxxxxxx
Please read the FAQ at http://kernelnewbies.org/FAQ


[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