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


Ignore:
Timestamp:
Oct 27, 2011, 10:24:04 PM (8 years ago)
Author:
Gedare
Comment:

Legend:

Unmodified
Added
Removed
Modified
  • Developer/Projects/Obsolete/Hypervisor

    v13 v14  
    1212
    1313The 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.
     14=  ARINC653  =
    1415
    15 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].
     16I am VERY fond of the idea of a free hypervisor that provides the real-time features required by ARINC 653. --[wiki:User:JoelSherrill Dr. Joel] 23:18, 25 January 2010 (UTC).
     17
     18The implementation of ARINC 653 interface in RTEMS was studied as part of a ESA project named AIR. This study was developed to "study of how the Real-Time Executive for Multiprocessor Systems (RTEMS) can be adapted to fullfill the requirements defined in the ARINC 653 standard". The project provided a proof of concept of the ARINC 553 implementation. The project page can be found [http://air.di.fc.ul.pt/ here].
     19The final report can be found [http://air.di.fc.ul.pt/air/downloads/07-35.pdf here]. "This document:  (i) describes the main issues regarding the AIR architecture specification;(ii) addresses how space and time partitioning could be provided in an abstract processor infrastructure, as well as those requirements can be mapped into both SPARC ERC32/LEON and Intel IA-32 (80x86) architectures;(iii) describes how to achieve the mapping of the ARINC 653 service interface in RTEMS;(iv) identifies the most relevant module dependencies of RTEMS with regard to AIR implementations;(v) identifies a preliminary set of modifications to be introduced in the RTEMS application production chain for the implementation of AIR-based systems (exemplified through a proof of concept prototype)."
     20Quoted from  http://hdl.handle.net/10455/2982 . -- cdcs
     21[http://www.superiorpapers.com/ research paper]
     22
     23This 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].
    1624= L4 =
    1725
     
    2432
    2533RTEMS based RT-VMM (Real-Time Virtual Machine Monitor). Current RTEMS can not support to run another OS (such as Linux or uClinux). We want to add hypervisor (or Virtual Machine Monitor) function on RTEMS, then RTEMS has the power like XEN that can run Linux or other OS, but RTEMS also maintain original hard Real-Time funtions. First, we will try to make RTEMS run uClinux on ARM simulator SkyEye ( http://www.skyeye.org ), then  we will try to make RTEMS run ARM Linux on XSCALE CPU based board or SkyEye simulator. We consider virtualization techs on Embedded RTOS area has potential value.  (from chyyuu@gmail.com)
    26 
    27 I am VERY fond of the idea of a free hypervisor that provides the real-time features required by ARINC 653. --[wiki:User:JoelSherrill Dr. Joel] 23:18, 25 January 2010 (UTC).
    28 
    29 The implementation of ARINC 653 interface in RTEMS was studied as part of a ESA project named AIR. This study was developed to "study of how the Real-Time Executive for Multiprocessor Systems (RTEMS) can be adapted to fullfill the requirements defined in the ARINC 653 standard". The project provided a proof of concept of the ARINC 553 implementation. The project page can be found [http://air.di.fc.ul.pt/ here].
    30 The final report can be found [http://air.di.fc.ul.pt/air/downloads/07-35.pdf here]. "This document:  (i) describes the main issues regarding the AIR architecture specification;(ii) addresses how space and time partitioning could be provided in an abstract processor infrastructure, as well as those requirements can be mapped into both SPARC ERC32/LEON and Intel IA-32 (80x86) architectures;(iii) describes how to achieve the mapping of the ARINC 653 service interface in RTEMS;(iv) identifies the most relevant module dependencies of RTEMS with regard to AIR implementations;(v) identifies a preliminary set of modifications to be introduced in the RTEMS application production chain for the implementation of AIR-based systems (exemplified through a proof of concept prototype)."
    31 Quoted from  http://hdl.handle.net/10455/2982 . -- cdcs
    32 [http://www.superiorpapers.com/ research paper]