summaryrefslogtreecommitdiff
path: root/include/sja1000.h
diff options
context:
space:
mode:
authorAndre Przywara <andre.przywara@linaro.org>2013-09-19 18:06:45 +0200
committerAlbert ARIBAUD <albert.u.boot@aribaud.net>2013-10-03 21:28:55 +0200
commitd4296887544ddf95808bfb62f312008f519efb7b (patch)
treee06b4b3f187ae101f6c4aa4d6ac8695518d40ab1 /include/sja1000.h
parentba6a1698116da272f14c53a3ae41467cb7fc4372 (diff)
downloadu-boot-imx-d4296887544ddf95808bfb62f312008f519efb7b.zip
u-boot-imx-d4296887544ddf95808bfb62f312008f519efb7b.tar.gz
u-boot-imx-d4296887544ddf95808bfb62f312008f519efb7b.tar.bz2
ARM: extend non-secure switch to also go into HYP mode
For the KVM and XEN hypervisors to be usable, we need to enter the kernel in HYP mode. Now that we already are in non-secure state, HYP mode switching is within short reach. While doing the non-secure switch, we have to enable the HVC instruction and setup the HYP mode HVBAR (while still secure). The actual switch is done by dropping back from a HYP mode handler without actually leaving HYP mode, so we introduce a new handler routine in our new secure exception vector table. In the assembly switching routine we save and restore the banked LR and SP registers around the hypercall to do the actual HYP mode switch. The C routine first checks whether we are in HYP mode already and also whether the virtualization extensions are available. It also checks whether the HYP mode switch was finally successful. The bootm command part only calls the new function after the non-secure switch. Signed-off-by: Andre Przywara <andre.przywara@linaro.org>
Diffstat (limited to 'include/sja1000.h')
0 files changed, 0 insertions, 0 deletions