Changes between Version 11 and Version 12 of Developer/Projects/Obsolete/Hypervisor
- Timestamp:
- 10/27/11 22:17:27 (12 years ago)
Legend:
- Unmodified
- Added
- Removed
- Modified
-
Developer/Projects/Obsolete/Hypervisor
v11 v12 21 21 22 22 23 The goal is to provide a [wiki:ARINC653API_ minimal_ARINC653_layer ARINC653APIminimal ARINC653 layer] that support only intra-partition services. As inter-partitions would be managed by an underlying hypervisor, they must be integrated as a second step for ARINC653 services integration. The idea here would be to provide an API that support the first part of ARINC653 services so that ARINC653 application can compile with RTEMS and intra-partition services would work.23 The goal is to provide a [wiki:ARINC653API_ minimal ARINC653 layer] that support only intra-partition services. As inter-partitions would be managed by an underlying hypervisor, they must be integrated as a second step for ARINC653 services integration. The idea here would be to provide an API that support the first part of ARINC653 services so that ARINC653 application can compile with RTEMS and intra-partition services would work. 24 24 This implies to add a new API support in RTEMS. The project would enable the following services to be interfaces with the regular RTEMS API: tasks, intra-partition (blackboard/event/semaphore/buffer) and time service. For inter-partition services (queueing/sampling ports), we expect to provide the definition of the function but leave it blank so that an ARINC653 partition would compile but the behaviour would have to be implemented in the future. 25 25 = RTEMS Virtual Machine Monitor =