47:(or IRQ) to the CPU with a certain priority level, and the CPU sets a mask that causes any other interrupts with a lower priority to be put into a pending state, until the CPU releases control back to the interrupt controller. If a signal comes in at a higher priority, then the current interrupt will be put into a pending state; the CPU sets the interrupt mask to the priority and places any interrupts with a lower priority into a pending state until the CPU finishes handling the new, higher priority interrupt.
50:
Windows maps not only hardware interrupt levels to its internal interrupt table but also maps software interrupts. The mappings in this table are called
Interrupt Request Levels, or IRQLs, and a separate IRQL is kept for each processor in a multiprocessor system. The IRQL values are specific to the
71:, which were supported briefly on early versions of Windows). This means that APCs (asynchronous procedure calls), user threads and kernel mode operations can be interrupted, and the system must run them at an IRQL lower than the thread scheduler (or "dispatcher").
156:
123:
63:
processor architectures that
Windows can run on, though theoretically they can support other CPUs that use a similar interrupt scheme (such as the
166:
44:
95:
40:
192:
135:
90:
39:. On processor architectures on which Windows runs, hardware generates signals that are sent to an
36:
8:
85:
68:
16:
Means by which
Windows prioritizes interrupts that come from the system's processors
119:
186:
131:
100:
28:
162:
80:
64:
32:
60:
56:
52:
184:
165:, April 26, 2016, pp. 6–7, archived from
27:) is a hardware-independent means with which
149:
118:
112:
185:
158:Scheduling, Thread Context, and IRQL
43:. The interrupt controller sends an
13:
14:
204:
96:Programmable Interrupt Controller
124:"Inside NT's Interrupt Handling"
1:
106:
35:that come from the system's
7:
74:
10:
209:
91:Interrupt priority level
21:Interrupt Request Level
193:Windows administration
138:on September 13, 2016
122:(October 31, 1997),
41:interrupt controller
169:on October 22, 2016
120:Russinovich, Mark
86:Interrupt handler
45:interrupt request
200:
178:
177:
176:
174:
153:
147:
146:
145:
143:
134:, archived from
116:
208:
207:
203:
202:
201:
199:
198:
197:
183:
182:
181:
172:
170:
155:
154:
150:
141:
139:
117:
113:
109:
77:
17:
12:
11:
5:
206:
196:
195:
180:
179:
148:
128:Windows IT Pro
110:
108:
105:
104:
103:
98:
93:
88:
83:
76:
73:
15:
9:
6:
4:
3:
2:
205:
194:
191:
190:
188:
168:
164:
160:
159:
152:
137:
133:
129:
125:
121:
115:
111:
102:
99:
97:
94:
92:
89:
87:
84:
82:
79:
78:
72:
70:
66:
62:
58:
54:
48:
46:
42:
38:
34:
30:
26:
22:
171:, retrieved
167:the original
157:
151:
140:, retrieved
136:the original
132:Penton Media
127:
114:
49:
31:prioritizes
24:
20:
18:
107:References
101:spl (Unix)
37:processors
33:interrupts
173:April 26,
163:Microsoft
142:April 26,
81:Interrupt
65:DEC Alpha
187:Category
75:See also
29:Windows
61:AMD64
175:2016
144:2016
69:MIPS
67:and
59:and
57:IA64
25:IRQL
53:x86
19:An
189::
161:,
130:,
126:,
55:,
23:(
Text is available under the Creative Commons Attribution-ShareAlike License. Additional terms may apply.