mirror of
https://gitlab.com/qemu-project/qemu
synced 2024-11-05 20:35:44 +00:00
hw/arm/virt: Default to not providing TrustZone support
Switch the default for the 'virt' board to not providing TrustZone support in either the CPU or the GIC. This is primarily for the benefit of UEFI, which currently assumes there is no TrustZone support, and does not set the GIC up correctly if it is TZ-aware. It also means the board is consistent about its behaviour whether we're using KVM or TCG (KVM never has TrustZone support). If TrustZone support is required (for instance for running test suites or TZ-aware firmware) it can be enabled with the "-machine secure=on" command line option. Signed-off-by: Peter Maydell <peter.maydell@linaro.org> Reviewed-by: Peter Crosthwaite <crosthwaite.peter@gmail.com> Reviewed-by: Peter Maydell <peter.maydell@linaro.org> Reviewed-by: Edgar E. Iglesias <edgar.iglesias@xilinx.com> Tested-by: Edgar E. Iglesias <edgar.iglesias@xilinx.com> Message-id: 1441383782-24378-6-git-send-email-peter.maydell@linaro.org
This commit is contained in:
parent
4182bbb19d
commit
2d710006a0
1 changed files with 5 additions and 2 deletions
|
@ -1044,8 +1044,11 @@ static void virt_instance_init(Object *obj)
|
|||
{
|
||||
VirtMachineState *vms = VIRT_MACHINE(obj);
|
||||
|
||||
/* EL3 is enabled by default on virt */
|
||||
vms->secure = true;
|
||||
/* EL3 is disabled by default on virt: this makes us consistent
|
||||
* between KVM and TCG for this board, and it also allows us to
|
||||
* boot UEFI blobs which assume no TrustZone support.
|
||||
*/
|
||||
vms->secure = false;
|
||||
object_property_add_bool(obj, "secure", virt_get_secure,
|
||||
virt_set_secure, NULL);
|
||||
object_property_set_description(obj, "secure",
|
||||
|
|
Loading…
Reference in a new issue