ehmry/genode
ehmry/genode
1
0
Fork 0
Code Issues Pull Requests Releases Wiki Activity
c13fbff8c1
genode/repos/base-hw/src/core/include/trustzone.h

26 lines
477 B
C
Raw Normal View History

base-hw: implement vm_session for TrustZone * Introduces Schedule_context * Use fast-interrupts or normal interrupts * Add mode-transition between secure/non-secure world * Limit system resources for Genode apps due to non-secure world This commit implements the newly introduced Vm session interface to be used on top of TrustZone capable Armv7 CPUs. Therefore a new Schedule_context is introduced in the kernel. Threads and Vms are both Schedule_contexts used by the scheduler. In contrast to a thread a vm uses a different assembler mode switch to the non-secure, virtual world, as well as another exception is used, when the non-secure world is left. For both worlds to co-exist the interrupt-controller needs to be configured, so that the secure (Genode) world uses fast-interrupts only, and the non-secure world only legacy interrupts. The only TrustZone capable platform the base-hw kernel works on top of is the CoreTile Express 9x4 for the Versatile Express motherboard. For a virtual machine working properly on top some platform resources must be reserved. Therefore there exist two flavours of this platform now, one with the 'trustzone' spec-variable enabled, and one without. If 'trustzone' is specified most platform resources (DDR-RAM, and most IRQs) are reserved for the Vm and not available to the secure Genode world.
2012-10-02 14:27:32 +02:00
/*
* \brief TrustZone specific functions
* \author Stefan Kalkowski
* \date 2012-10-10
*/
/*
Update copyright headers to 2013
2013-01-10 21:44:47 +01:00
* Copyright (C) 2012-2013 Genode Labs GmbH
base-hw: implement vm_session for TrustZone * Introduces Schedule_context * Use fast-interrupts or normal interrupts * Add mode-transition between secure/non-secure world * Limit system resources for Genode apps due to non-secure world This commit implements the newly introduced Vm session interface to be used on top of TrustZone capable Armv7 CPUs. Therefore a new Schedule_context is introduced in the kernel. Threads and Vms are both Schedule_contexts used by the scheduler. In contrast to a thread a vm uses a different assembler mode switch to the non-secure, virtual world, as well as another exception is used, when the non-secure world is left. For both worlds to co-exist the interrupt-controller needs to be configured, so that the secure (Genode) world uses fast-interrupts only, and the non-secure world only legacy interrupts. The only TrustZone capable platform the base-hw kernel works on top of is the CoreTile Express 9x4 for the Versatile Express motherboard. For a virtual machine working properly on top some platform resources must be reserved. Therefore there exist two flavours of this platform now, one with the 'trustzone' spec-variable enabled, and one without. If 'trustzone' is specified most platform resources (DDR-RAM, and most IRQs) are reserved for the Vm and not available to the secure Genode world.
2012-10-02 14:27:32 +02:00
*
* This file is part of the Genode OS framework, which is distributed
* under the terms of the GNU General Public License version 2.
*/
#ifndef _CORE__INCLUDE__TRUSTZONE_H_
#define _CORE__INCLUDE__TRUSTZONE_H_
namespace Kernel {
class Pic;
hw_arndale: idle threads on secondary processors fix #1006
2013-12-17 18:10:02 +01:00
void init_trustzone(Pic * pic);
base-hw: implement vm_session for TrustZone * Introduces Schedule_context * Use fast-interrupts or normal interrupts * Add mode-transition between secure/non-secure world * Limit system resources for Genode apps due to non-secure world This commit implements the newly introduced Vm session interface to be used on top of TrustZone capable Armv7 CPUs. Therefore a new Schedule_context is introduced in the kernel. Threads and Vms are both Schedule_contexts used by the scheduler. In contrast to a thread a vm uses a different assembler mode switch to the non-secure, virtual world, as well as another exception is used, when the non-secure world is left. For both worlds to co-exist the interrupt-controller needs to be configured, so that the secure (Genode) world uses fast-interrupts only, and the non-secure world only legacy interrupts. The only TrustZone capable platform the base-hw kernel works on top of is the CoreTile Express 9x4 for the Versatile Express motherboard. For a virtual machine working properly on top some platform resources must be reserved. Therefore there exist two flavours of this platform now, one with the 'trustzone' spec-variable enabled, and one without. If 'trustzone' is specified most platform resources (DDR-RAM, and most IRQs) are reserved for the Vm and not available to the secure Genode world.
2012-10-02 14:27:32 +02:00
}
#endif /* _CORE__INCLUDE__TRUSTZONE_H_ */
Reference in New Issue Copy Permalink