Hypervisor mode executes at EL2 in the AArch32 state.
EL2 is implemented only in a non-secure state, to support guest operating system management.
EL2 virtualization provides:
virtual values for the contents of a small number of identification registers
traps for EL2 exceptions (a hypervisor might be presenting an emulated view of the system to EL1. In this instance a guest OS would not be able to directly invoke the device firmware using a Secure Monitor Call. Instead such calls would be trapped to EL2, by setting the HCR_EL2.TSC bit in the Hypervisor Configuration Register.)
Routeing for interrupts to running/stopped guest OS or the hypervisor
