From: "pradeep singh" <2500.pradeep@gmail.com>
To: Learning Linux <learninglinux4@gmail.com>
Cc: kernelnewbies@nl.linux.org, linux-newbie@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: Why can't we sleep in an ISR?
Date: Mon, 14 May 2007 12:40:14 +0530 [thread overview]
Message-ID: <366312910705140010m78b215a2t1753445e81120288@mail.gmail.com> (raw)
In-Reply-To: <9f1dc2cf0705132337k13aa3ccesc575d4550492a24e@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1054 bytes --]
On 5/14/07, Learning Linux <learninglinux4@gmail.com> wrote:
>
> I have a very basic doubt here ... what makes it impossible to sleep
> in an ISR? I mean, I know that the kernel preemption is disabled and
> the kernel will panic, but I could not understand why?
Because the interrupt which you are serving in the ISR has been masked
to avoid preemption(
true for maskable inetrrupts ).Any locks you are holding in ISR are now with
you solely. So, if you try to sleep you take the locks
you untill you are rescheduled and complete. This may lead to a
deadlock for the lock resource.
Thus to avoid this, kernel developers disable preemption and also on every
schedule check if you are *in_interrupt*, if you are, you are probably doing
something really bad.So its better to panic in such case.
This is my naive understanding.
Please CMIIW.
Thanks
TIA,
>
> LL
>
> --
> To unsubscribe from this list: send an email with
> "unsubscribe kernelnewbies" to ecartis@nl.linux.org
> Please read the FAQ at http://kernelnewbies.org/FAQ
>
>
--
play the game
[-- Attachment #2: Type: text/html, Size: 1989 bytes --]
next prev parent reply other threads:[~2007-05-14 7:10 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-05-14 6:37 Why can't we sleep in an ISR? Learning Linux
2007-05-14 7:10 ` pradeep singh [this message]
2007-05-14 7:16 ` Learning Linux
2007-05-14 15:24 ` Bahadir Balban
2007-05-14 15:56 ` Dong Feng
2007-05-15 5:17 ` pradeep singh
2007-05-15 6:45 ` Dong Feng
2007-05-15 7:10 ` pradeep singh
2007-05-15 7:28 ` Dong Feng
2007-05-15 8:12 ` pradeep singh
2007-05-15 8:40 ` Learning Linux
2007-05-15 8:58 ` Dong Feng
2007-05-15 16:57 ` Phillip Susi
2007-05-15 22:49 ` Dong Feng
2007-05-16 15:20 ` Phillip Susi
2007-05-16 23:17 ` Dong Feng
2007-05-17 16:07 ` Phillip Susi
2007-05-17 23:50 ` Dong Feng
2007-05-14 12:25 ` Helge Hafting
2007-05-14 12:52 ` pradeep singh
2007-05-14 13:36 ` Dong Feng
-- strict thread matches above, loose matches on Subject: below --
2007-05-14 15:22 linux
2007-05-14 15:55 ` Rik van Riel
2007-05-15 9:34 rohit hooda
2007-05-15 9:46 ` pradeep singh
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=366312910705140010m78b215a2t1753445e81120288@mail.gmail.com \
--to=2500.pradeep@gmail.com \
--cc=kernelnewbies@nl.linux.org \
--cc=learninglinux4@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-newbie@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox