kernelnewbies.kernelnewbies.org archive mirror
 help / color / mirror / Atom feed
From: zertsekel@gmail.com (Kosta Zertsekel)
To: kernelnewbies@lists.kernelnewbies.org
Subject: About interrupt handler
Date: Fri, 24 Feb 2012 11:19:36 +0200	[thread overview]
Message-ID: <CADxo8WJ4+8mXGPXkZfeKbZORtimDn2DL_N17skB6NVFZXdbmYA@mail.gmail.com> (raw)
In-Reply-To: <CABi1daENZ-3ndF=kic6A3fu8bAmJP20XnpPuVMXLLihWQeJhdg@mail.gmail.com>

>> I'm begin to learn the Kernel and i'm reading <<Linux kernel
>> development>>.It says "This is an important point, always keep in mind that
>> all interrupt handler has interrupted other code(possibly even another
>> interrupt handler on a different line)".What i am not able to understand is
>> how a interrupt handler be interrupted ? DID NOT it uninterrupted?
>
> It depends on the architecture and the interrupt controller being
> used, and the driver code itself.
>
> Normally, when an interrupt fires, that particular interrupt will be
> masked and your own handler won't interrupt itself, but you may very
> well be interrupted by other interrupts.

Can you please point out some code for explanation?
--- KostaZ

  reply	other threads:[~2012-02-24  9:19 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-02-22 15:59 About interrupt handler cheneydeng
2012-02-22 20:50 ` Dave Hylands
2012-02-24  9:19   ` Kosta Zertsekel [this message]
2012-02-24 21:08     ` Dave Hylands
2012-02-24 21:18       ` Dave Hylands
2012-02-26 12:11         ` Kosta Zertsekel
2012-02-26 17:53           ` Dave Hylands
  -- strict thread matches above, loose matches on Subject: below --
2012-02-23 10:46 cheneydeng
2012-02-22 15:38 cheneydeng
2012-02-23 10:07 ` Zhengwang Ruan

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=CADxo8WJ4+8mXGPXkZfeKbZORtimDn2DL_N17skB6NVFZXdbmYA@mail.gmail.com \
    --to=zertsekel@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).