diff options
author | Linus Torvalds <torvalds@linux-foundation.org> | 2012-10-11 23:32:43 -0400 |
---|---|---|
committer | Linus Torvalds <torvalds@linux-foundation.org> | 2012-10-11 23:32:43 -0400 |
commit | 5cea24c5899a81abf59706d69580dd5c734effa8 (patch) | |
tree | c080ec6b1c6cf27b50f00b2980068fb563b6f7ec /Documentation | |
parent | 2fc07efa2241afe08de136c061b3baa103fb286c (diff) | |
parent | a0f0dd57f4a85310d9936f1770a0424b49fef876 (diff) |
Merge branch 'for-linus' of git://git.linaro.org/people/rmk/linux-arm
Pull second set of ARM updates from Russell King:
"This is the second set of ARM updates for this merge window.
Contained within are changes to allow the kernel to boot in hypervisor
mode on CPUs supporting virtualization, and cache flushing support to
the point of inner sharable unification, which are used by the
suspend/resume code to avoid having to do a full cache flush.
Also included is one fix for VFP code identified by Michael Olbrich."
* 'for-linus' of git://git.linaro.org/people/rmk/linux-arm:
ARM: vfp: fix saving d16-d31 vfp registers on v6+ kernels
ARM: 7549/1: HYP: fix boot on some ARM1136 cores
ARM: 7542/1: mm: fix cache LoUIS API for xscale and feroceon
ARM: mm: update __v7_setup() to the new LoUIS cache maintenance API
ARM: kernel: update __cpu_disable to use cache LoUIS maintenance API
ARM: kernel: update cpu_suspend code to use cache LoUIS operations
ARM: mm: rename jump labels in v7_flush_dcache_all function
ARM: mm: implement LoUIS API for cache maintenance ops
ARM: virt: arch_timers: enable access to physical timers
ARM: virt: Add CONFIG_ARM_VIRT_EXT option
ARM: virt: Add boot-time diagnostics
ARM: virt: Update documentation for hyp mode entry support
ARM: zImage/virt: hyp mode entry support for the zImage loader
ARM: virt: allow the kernel to be entered in HYP mode
ARM: opcodes: add __ERET/__MSR_ELR_HYP instruction encoding
Diffstat (limited to 'Documentation')
-rw-r--r-- | Documentation/arm/Booting | 22 |
1 files changed, 21 insertions, 1 deletions
diff --git a/Documentation/arm/Booting b/Documentation/arm/Booting index a341d87d276e..0c1f475fdf36 100644 --- a/Documentation/arm/Booting +++ b/Documentation/arm/Booting | |||
@@ -154,13 +154,33 @@ In either case, the following conditions must be met: | |||
154 | 154 | ||
155 | - CPU mode | 155 | - CPU mode |
156 | All forms of interrupts must be disabled (IRQs and FIQs) | 156 | All forms of interrupts must be disabled (IRQs and FIQs) |
157 | The CPU must be in SVC mode. (A special exception exists for Angel) | 157 | |
158 | For CPUs which do not include the ARM virtualization extensions, the | ||
159 | CPU must be in SVC mode. (A special exception exists for Angel) | ||
160 | |||
161 | CPUs which include support for the virtualization extensions can be | ||
162 | entered in HYP mode in order to enable the kernel to make full use of | ||
163 | these extensions. This is the recommended boot method for such CPUs, | ||
164 | unless the virtualisations are already in use by a pre-installed | ||
165 | hypervisor. | ||
166 | |||
167 | If the kernel is not entered in HYP mode for any reason, it must be | ||
168 | entered in SVC mode. | ||
158 | 169 | ||
159 | - Caches, MMUs | 170 | - Caches, MMUs |
160 | The MMU must be off. | 171 | The MMU must be off. |
161 | Instruction cache may be on or off. | 172 | Instruction cache may be on or off. |
162 | Data cache must be off. | 173 | Data cache must be off. |
163 | 174 | ||
175 | If the kernel is entered in HYP mode, the above requirements apply to | ||
176 | the HYP mode configuration in addition to the ordinary PL1 (privileged | ||
177 | kernel modes) configuration. In addition, all traps into the | ||
178 | hypervisor must be disabled, and PL1 access must be granted for all | ||
179 | peripherals and CPU resources for which this is architecturally | ||
180 | possible. Except for entering in HYP mode, the system configuration | ||
181 | should be such that a kernel which does not include support for the | ||
182 | virtualization extensions can boot correctly without extra help. | ||
183 | |||
164 | - The boot loader is expected to call the kernel image by jumping | 184 | - The boot loader is expected to call the kernel image by jumping |
165 | directly to the first instruction of the kernel image. | 185 | directly to the first instruction of the kernel image. |
166 | 186 | ||