Changes between Version 11 and Version 12 of GSoC/2013/ParavirtualizationOfRTEMS


Ignore:
Timestamp:
Apr 26, 2013, 4:28:44 PM (6 years ago)
Author:
Phipse
Comment:

/* ARINC 653 API - GSOC 2012 */

Legend:

Unmodified
Added
Removed
Modified
  • GSoC/2013/ParavirtualizationOfRTEMS

    v11 v12  
    9090The resulting ELF binary, e.g. hello.exe, is passed on to L4Re as a command line argument.
    9191It is loaded into the applications address space and the vcpu is supplied with EIP and ESP.
    92 =  ARINC 653 API - GSOC 2012  =
     92=  ARINC 653 API  =
     93
     94
     95The ARINC 653 standard defines "a software specification for space and time partitioning in Safety-critical avionics Real-time operating systems".<ref>https://en.wikipedia.org/wiki/ARINC_653</ref>
     96These specifications are enforced by an additional layer called APEX (APplication EXecutive).
     97
     98As POK is ARINC compliant and RTEMS is not, a paravirtualized RTEMS on top of POK would be a way to achieve compliance.
     99To make use of this compliance, RTEMS needs to be able to communicate with other partitions on POK by using ''intra-partition communication''.
     100
     101
     102=  GSoC 2012 Project  =
    93103
    94104Source code: [https://github.com/jolkaczad/rtems_hyper by Wiktor Langowski ]