public inbox for linux-newbie@vger.kernel.org
 help / color / mirror / Atom feed
From: "Dong Feng" <middle.fengdong@gmail.com>
To: pradeep singh <2500.pradeep@gmail.com>
Cc: Bahadir Balban <bahadir.balban@gmail.com>,
	Learning Linux <learninglinux4@gmail.com>,
	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: Tue, 15 May 2007 14:45:43 +0800	[thread overview]
Message-ID: <a2ebde260705142345m440c70fbu33934334fbb69f8e@mail.gmail.com> (raw)
In-Reply-To: <366312910705142217geba69dbm98a6c0bf2aabb937@mail.gmail.com>

>
> good enough, but i have a query regarding this then.
> On a 8K kernel stack system, doesn't interrupts share the stack associated
> with the current process which was interrupted?

Yes, I think so.

> Doesn't interrupt steals the CPU slice time allocated to the running process
> to run?

I don't think so but I am not sure.

> Doesn't it run in current process's context ?
>

No. I think the concept of process context is a higher-level logical
concept. Though the interrupt share stack with the interrupted
process, in my opinion it logically does not share the context with
the process.

> What am i missing here?
>
> Thanks
> ~psr
>


But I do not see the exact relationship between your specific queries
and the original question. Could you elaborate?

  reply	other threads:[~2007-05-15  6:45 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
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 [this message]
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=a2ebde260705142345m440c70fbu33934334fbb69f8e@mail.gmail.com \
    --to=middle.fengdong@gmail.com \
    --cc=2500.pradeep@gmail.com \
    --cc=bahadir.balban@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