Xv6 traps and system calls

Traps and system calls

Learning xv6-riscv-book Chapter 4 Traps and system calls

Trap: CPU transfer to speical code to handle events

• system call: ecall into the kernel
• exception: something illegal
• interrupt: from device

xv6 kernel handles all traps.

code -> trap (handling in kernel) -> resume

trap handling proceeds:

1. hardware actions by CPU
2. vector prepares for kernel C code
3. trap handler decides what to do
4. do system call / device service

three cases of assembly vectors:

• traps from user space
• traps from kernel space
• timer interrupts

RISC-V trap machinery

Registers

A set of registers:

• kernel reads about a trap
• kernel writes to tell the CPU how to handle traps.

These registers are in supervisor mode: cannot be r/w in user mode

Machine mode has an equivalent set of these regs: only for timer interrupts

Each CPU has its own set: can handling traps at a same time