中斷處理

作業系統

簡介

行程管理

記憶體管理

輸出入管理

檔案管理

使用者介面

嵌入式系統

RTOS

中斷處理

案例研究

EOS0

CurtOS

F9

UNIXv6

NachOS

uCOSII

L4

RtThread

Haiku

MINIX

Linux

Windows

mykernel

訊息

相關網站

參考文獻

最新修改

簡體版

English

Intel Architecture 保護模式架構:http://www.csie.ntu.edu.tw/~wcchen/asm98/asm/proj/b85506061/cover.html

中斷描述表:http://www.csie.ntu.edu.tw/~wcchen/asm98/asm/proj/b85506061/chap4/idt.html
摘錄:
由中斷處理程序中返回時,必須使用 IRET 指令。IRET 和 RET 指令不同的地方,即在於它會取回 EFLAGS 的值。不過,EFLAGS 中的 IOPL 只有在 CPL 為 0 時,才會改變。而 EFLAGS 中的 IF 旗標只有在 CPL 小於或等於 IOPL 時,才會改變。如果在中斷時有切換堆疊,IRET 也會把堆疊切換回來。

http://en.wikipedia.org/wiki/Interrupt
摘錄:

http://en.wikipedia.org/wiki/Interrupt_handler

摘錄:
In several operating systems - Linux, Unix, Mac OS X, Microsoft Windows, and some other operating systems in the past, interrupt handlers are divided into two parts: the First-Level Interrupt Handler (FLIH) and the Second-Level Interrupt Handlers (SLIH). FLIHs are also known as hard interrupt handlers or fast interrupt handlers, and SLIHs are also known as slow/soft interrupt handlers, Deferred Procedure Call.

A FLIH implements at minimum platform-specific interrupt handling similarly to interrupt routines. In response to an interrupt, there is a context switch, and the code for the interrupt is loaded and executed. The job of a FLIH is to quickly service the interrupt, or to record platform-specific critical information which is only available at the time of the interrupt, and schedule the execution of a SLIH for further long-lived interrupt handling.

ARM 处理器中断及可重入中断在 Windows CE 操作系统的应用

Facebook

Unless otherwise stated, the content of this page is licensed under Creative Commons Attribution-NonCommercial-ShareAlike 3.0 License