Changes between Version 12 and Version 13 of Developer/Projects/Obsolete/Hypervisor

Timestamp:

10/27/11 22:21:58 (12 years ago)

Author:

Gedare

Comment:

Developer/Projects/Obsolete/Hypervisor

@@ -13 +13 @@
 The idea of this project is to ease the integration of RTEMS with hypervisor/supervisor/IMA platforms. At this time, some projects already provide software to isolate different RTEMS instance in a virtual machine (for example, Xtratum). It needs to tailor RTEMS for their own needs and adapt it to communicate with the underlying hypervisor. However, this approach requires to tailor RTEMS for each hypervisor, which can be hard, especially because this adaption efforts are not shared and duplicate code. This project aims at defining a generic adaptation layer to ease the tailoring of RTEMS to hypervisor and provide an open-source/free software hypervisor implementation example. So, it consists in two parts : one to design an adaptation layer to ease the tailoring of RTEMS with hypervisors and another that would consist in providing an hypervisor to execute RTEMS instances. For the second part, existing hypervisor/virtual machine can be used (such as POK or Xtratum) but the solution has to be released under free-software license so that everybody can use it at his convenience.
 
-As a result, this project would really use the integration of RTEMS into IMA architectures and would enable the design of ARINC653 systems with inter-partitions services.
+As a result, this project would really use the integration of RTEMS into IMA architectures and would enable the design of ARINC653 systems with inter-partitions services. See the project pages for [wiki:ARINC653API_  ARINC653 compatibility layer] and [wiki:ARINC653VM_  ARINC653 virtual machine].
 = L4 =
 
 
 RTEMS has been run on the L4 hypervisor so that should be a strong foundation for some types of hypervisor work.
-=  ARINC653 API support  =
-
-
-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.
-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.
 = RTEMS Virtual Machine Monitor =