kernelnewbies.kernelnewbies.org archive mirror
 help / color / mirror / Atom feed
From: vishu.kernel@gmail.com (Vishwas Srivastava)
To: kernelnewbies@lists.kernelnewbies.org
Subject: Kernelnewbies Digest, Vol 44, Issue 51
Date: Sat, 26 Jul 2014 22:37:10 +0530	[thread overview]
Message-ID: <CAGM3cC6WsZTmsOaSNMOxJk_hFUR4dfWTz6mMH-7dgxSMUW1zdA@mail.gmail.com> (raw)
In-Reply-To: <mailman.412.1406325749.2642.kernelnewbies@kernelnewbies.org>

Hi All,
          I have a doubt regarding the  threaded interrupt handing
mechanism.
what is the kernel context of execution while executing interrupt thread.
if i check for macro
in_irq() or in_interrupt() withing handler thread , my understanding is
that they both are going to return me 0 (since we are in kernel thread),
as threads runs in process context.

Also, since they are "kernel threads", they must be schedulable enteties.
what conceptually deviated me from my understanding is one of the driver
which had a threaded interrupt mechanism and when i checked

in_interrupt() macro, it returned me a non zero value so i am a bit
confused.

thanks in advance.

Vishwas S
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.kernelnewbies.org/pipermail/kernelnewbies/attachments/20140726/4b6fb106/attachment.html 

       reply	other threads:[~2014-07-26 17:07 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <mailman.412.1406325749.2642.kernelnewbies@kernelnewbies.org>
2014-07-26 17:07 ` Vishwas Srivastava [this message]
2014-07-28 16:24   ` Kernelnewbies Digest, Vol 44, Issue 51 Jeff Haran
2014-07-28 17:28     ` Vishwas Srivastava
     [not found]       ` <4E5779AD88B2F040B8A7E83ECF544D1A5366A6@SJCPEX01CL02.citrite.net>
2014-07-28 19:56         ` Vishwas Srivastava

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=CAGM3cC6WsZTmsOaSNMOxJk_hFUR4dfWTz6mMH-7dgxSMUW1zdA@mail.gmail.com \
    --to=vishu.kernel@gmail.com \
    --cc=kernelnewbies@lists.kernelnewbies.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;
as well as URLs for NNTP newsgroup(s).