What are the ARMv8 exception levels, and how does virtualization use EL2?
Short answer: ARMv8-A has four exception levels: EL0 user applications, EL1 the OS kernel, EL2 the hypervisor, and EL3 the secure monitor (firmware such as TF-A that switches between Normal and Secure worlds). A guest kernel runs at EL1 and its applications at EL0, exactly as on bare metal; EL2 configures what traps to it and controls the second stage of address translation, which is how the hypervisor stays in control.
| Level | Runs | Examples |
|---|---|---|
| EL0 | applications | user processes (guest and host) |
| EL1 | OS kernel | Linux, guest kernels |
| EL2 | hypervisor | KVM (or its low-level part), Xen |
| EL3 | secure monitor | TF-A BL31, handles SMC calls and PSCI |
Higher numbers are more privileged. Moving up happens only through an exception (interrupt, abort, or the instructions SVC → EL1, HVC → EL2, SMC → EL3). Moving down happens with ERET.
What EL2 controls
HCR_EL2(Hypervisor Configuration Register): which guest operations trap to EL2 (e.g.TWItrapsWFI,TSCtrapsSMC,IMO/FMOroute physical IRQ/FIQ to EL2,VMenables stage-2 translation).- Stage-2 translation (
VTTBR_EL2,VTCR_EL2): the guest's "physical" addresses (IPAs) are translated again to real physical addresses. - Virtual interrupts: injecting IRQs into the guest through the GIC's virtual CPU interface.
- Virtual timer offset (
CNTVOFF_EL2) so each guest sees its own time base.
How KVM uses EL2: nVHE vs VHE
- nVHE (non-VHE, ARMv8.0): the host kernel runs at EL1. A small piece of KVM code ("hyp" code) is installed at EL2 and does the world switch. Every switch between host and guest goes EL1 → EL2 → EL1.
- VHE (Virtualization Host Extensions, ARMv8.1+): the host kernel itself runs at EL2, and EL1 register accesses are redirected to their EL2 versions. Entering and leaving the guest is cheaper. Cortex-A53 does not have VHE (it is ARMv8.0); Cortex-A55/A76 and later do.
- pKVM (protected KVM), used on Android: the host runs at EL1 and a small trusted hypervisor at EL2 protects guest memory even from the host kernel.
Interview follow-up: "Does a guest system call (SVC) go to the hypervisor?" No. It goes to the guest kernel at EL1 without any hypervisor involvement. That is a big part of why virtualization is fast.