From: ruan.zhengwang@gmail.com (Zhengwang Ruan)
To: kernelnewbies@lists.kernelnewbies.org
Subject: About interrupt handler
Date: Thu, 23 Feb 2012 18:07:22 +0800 [thread overview]
Message-ID: <4F460FDA.1010100@gmail.com> (raw)
In-Reply-To: <tencent_6945DAE3232824F226742DB4@qq.com>
-------- Original Message --------
From: cheneydeng
Sent: 2012?02?22? ??? 23?38?37?
To: kernelnewbies
Subject: About interrupt handler
> hi all,
> 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 has more related to CPU architecture. Generally, while an interrupt
handler is being executed, the handler itself can chose to disable or
enable external interrupts (i.e, take x86 for example, IF bit for cflags
reg controls this.). If IF is enabled, then the interrupt handler
currently being executed may be interrupted and then jump to the entry
for the coming interrupt.
Thanks,
-Zhengwang
>
> ------------------
> best regards?
> cheneydeng
>
>
> _______________________________________________
> Kernelnewbies mailing list
> Kernelnewbies at kernelnewbies.org
> http://lists.kernelnewbies.org/mailman/listinfo/kernelnewbies
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.kernelnewbies.org/pipermail/kernelnewbies/attachments/20120223/ff4def83/attachment-0001.html
next prev parent reply other threads:[~2012-02-23 10:07 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-02-22 15:38 About interrupt handler cheneydeng
2012-02-23 10:07 ` Zhengwang Ruan [this message]
-- strict thread matches above, loose matches on Subject: below --
2012-02-22 15:59 cheneydeng
2012-02-22 20:50 ` Dave Hylands
2012-02-24 9:19 ` Kosta Zertsekel
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
2012-02-23 10:46 cheneydeng
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=4F460FDA.1010100@gmail.com \
--to=ruan.zhengwang@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).