CS 423 Operating System Design: Far too much information about - - PowerPoint PPT Presentation
CS 423 Operating System Design: Far too much information about interrupts Professor Adam Bates Fall 2018 CS423: Operating Systems Design Goals for Today Learning Objectives: Understand the role and types of of Interrupts
CS423: Operating Systems Design
CS 423: Operating Systems Design 2
CS 423: Operating Systems Design
3
Program Counter Program instructions Code Segment Offset Heap Data Segment Offset
Operand
Data Operand Current Instruction
OpCode
Stack Segment Offset Stack Pointer Stack Registers
CS 423: Operating Systems Design
4
Program Counter Program instructions Code Segment Offset Heap Data Segment
Operand
Data Operand
OpCode
Stack Segment Stack Pointer Registers Stack Program Counter Program instructions Code Segment Offset Heap Data Segment
Operand
Data Operand
OpCode
Stack Segment Stack Pointer Stack
Save State (Context) Load State (Context)
Registers
CS 423: Operating Systems Design
5
The state for processes that are not running on the CPU are maintained in the Process Control Block (PCB) data structure
Updated during context switch
An alternate PCB diagram
CS 423: Operating Systems Design
6
The Hardware (CPU) “Virtual” CPU “Virtual” CPU “Virtual” CPU
Context Switching + Scheduling
CS 423: Operating Systems Design
7
The Hardware (CPU) “Virtual” CPU
Context Switching + Scheduling
“Virtual” CPU “Virtual” CPU External Devices Interrupt Handler Interrupt Handler Interrupt Handler
CS 423: Operating Systems Design
8
Program Counter Program instructions Code Segment Offset Stack Segment Stack Pointer Stack Program Counter Program instructions Code Segment Offset Stack Segment Stack Pointer Stack
Save PC on thread stack Jump to Interrupt handler Handler
(SP, registers, segment pointers, …)
Thread Control Block Thread Control Block
Registers Registers
CS 423: Operating Systems Design 9
Program Counter Program instructions Code Segment Offset Stack Segment Stack Pointer Registers Stack Program Counter Program instructions Code Segment Offset Stack Segment Stack Pointer Registers Stack
Save PC on thread stack Jump to yield() function yield()
(SP, registers, segment pointers, …)
Thread Control Block Thread Control Block
CS423: Operating Systems Design
10
CS423: Operating Systems Design
11
Interrupt Vector Processor Register
h a n d l e Ti m e r I n t e r r u p t ( ) { . . . } h a n d l e D i v i d e B y Z e r o ( ) { . . . } h a n d l e S y s t e m C a l l ( ) { . . . }
CS423: Operating Systems Design
12
CS423: Operating Systems Design
13
User Stack Kernel Stack
Proc2 Running Proc1 Main Proc2 Ready to Run Proc1 Main User CPU State User CPU State Syscall Handler I/O Driver Top Half Proc2 Syscall Waiting for I/O Proc1 Main
CS 423: Operating Systems Design
14
■ Hardware generated:
■ Different I/O devices are connected to different
■ Device hardware signals the corresponding line ■ Interrupt controller signals the CPU (by signaling the
■ CPU saves return address after next instruction and
CS 423: Operating Systems Design
15
CS 423: Operating Systems Design
15
■ Hardware devices may need asynchronous and
■ Timer interrupt: Timers and time-dependent activities need
to be updated with the passage of time at precise intervals
CS 423: Operating Systems Design
15
■ Hardware devices may need asynchronous and
■ Timer interrupt: Timers and time-dependent activities need
to be updated with the passage of time at precise intervals
■ Network interrupt: The network card interrupts the CPU
when data arrives from the network
■ I/O device interrupt: I/O devices (such as mouse and
keyboard) issue hardware interrupts when they have input (e.g., a new character or mouse click)
CS 423: Operating Systems Design
16
CS 423: Operating Systems Design
17
CS 423: Operating Systems Design 18
LINTx — lines/pins for hardware interrupts. In this case… LINT0 — line for unmaskable interrupts LINT1 — line for maskable interrupts
CS 423: Operating Systems Design
19
CS 423: Operating Systems Design
19
■ How are interrupts handled on multicore machines?
CS 423: Operating Systems Design
19
■ How are interrupts handled on multicore machines?
■ On x86 systems each CPU gets its own local Advanced
■ The OS can program the APICs to determine which
■ The default (unless OS states otherwise) is to route all
CS 423: Operating Systems Design
20
HALT START Fetch next instruction Execute Instruction
CS 423: Operating Systems Design
21
HALT START Fetch next instruction Execute Instruction
interrupts disabled
Check for INT, init INT handler
Interrupt Stage Execute Stage Fetch Stage
CS 423: Operating Systems Design
22
Hardware
Device controller or other hardware issues an interrupt. Processor finishes execution
P r o c e s s o r s i g n a l s acknowledgment of interrupt. Processor pushes PSW and PC onto control stack.
Software
Save remainder of state information. Process interrupt. R e s t o r e p r o c e s s s t a t e information. Restore old PSW and PC. Processor loads new PC value based on interrupt.
Program Status Word (PSW) contains interrupt masks, privilege states, etc.
CS 423: Operating Systems Design
23
■ Software Interrupts:
■ Interrupts caused by the execution of a software
■ INT <interrupt_number>
■ Used by the system call interrupt()
■ Initiated by the running (user level) process ■ Cause current processing to be interrupted and
CS 423: Operating Systems Design
24
■ Exceptions
■ Initiated by processor hardware itself ■ Example: divide by zero
■ Like a software interrupt, they cause a transfer
CS423: Operating Systems Design
25
CS 423: Operating Systems Design
26
CS 423: Operating Systems Design
26
■ Interrupts (as the name suggests) have the
■ What are the implications on regular program
CS 423: Operating Systems Design
26
■ Interrupts (as the name suggests) have the
■ What are the implications on regular program
■ Must keep interrupt code short in order not to keep
■ Cannot block (regular processing does not resume until
interrupt returns, so if the interrupt blocks in the middle the system “hangs”)
CS 423: Operating Systems Design
27
CS 423: Operating Systems Design
27
■ Can an interrupt handler use malloc()?
CS 423: Operating Systems Design
27
■ Can an interrupt handler use malloc()? ■ Can an interrupt handler write data to disk?
CS 423: Operating Systems Design
27
■ Can an interrupt handler use malloc()? ■ Can an interrupt handler write data to disk? ■ Can an interrupt handler use busy wait?
■ E.G. — while (!event) loop;
CS423: Operating Systems Design
28
CS 423: Operating Systems Design
29
■ Since the interrupt handler must be minimal, all other
■ Example:
■ Network interrupt causes packet to be copied from network card ■ Other processing on the packet should be deferred until its time
comes
■ The deferred portion of interrupt processing is called
CS 423: Operating Systems Design
30
■ 32 handlers that must be statically defined in the Linux
■ A hardware interrupt (before returning) uses raise_softirq()
■ At a later time, when scheduling permits, the marked
■ When a hardware interrupt is finished ■ When a process makes a system call ■ When a new process is scheduled
CS 423: Operating Systems Design
31
■ HI_SOFTIRQ ■ TIMER_SOFTIRQ ■ NET_TX_SOFTRQ ■ NET_RX_SOFTIRQ ■ BLOCK_SOFTIRQ ■ TASKLET_SOFTIRQ ■ SCHED_SOFTIRQ ■ …
CS 423: Operating Systems Design
32
■ HI_SOFTIRQ ■ TIMER_SOFTIRQ ■ NET_TX_SOFTRQ ■ NET_RX_SOFTIRQ ■ BLOCK_SOFTIRQ ■ TASKLET_SOFTIRQ ■ SCHED_SOFTIRQ ■ …
CS 423: Operating Systems Design
33
■ Bottom halves multiplexed on top of soft_irq’s ■ Scheduled using
■ tasklet_schedule() ■ tasklet_hi_schedule()
■ Same tasklet invocations are serialized ■ Tasklets can be created or removed
■ Cannot sleep (cannot save their context)
CS 423: Operating Systems Design
34
■
Work deferred to its own thread
■
Can be scheduled together with other threads according to priorities set by a scheduling policy
■
Associated with its thread control block and hence can block (and save context)
■
DECLARE_WORK(name, void (*func)(void *), void *data);
■
INIT_WORK(struct work_struct *work, void (*func)(void *), void *data);
■
schedule_work(&work);