Changes between Version 20 and Version 21 of GSoC/2013/ParavirtualizationOfRTEMS

Timestamp:

04/29/13 16:25:03 (11 years ago)

Author:

Phipse

Comment:

/* Paravirtualization layer */ RTEMS startup as a guest issue

GSoC/2013/ParavirtualizationOfRTEMS

@@ -43 +43 @@
  *  '''faultHandler''' -> is called by POK, when a fault occurrs
  *  tbc
+
+=  RTEMS startup as a guest  =
+
+
+In L4RTEMS the wrapper task loads the RTEMS elf-binary, stores the initial IP and SP in the vCPU registers and starts the vCPU.
+Therefore the binary is passed as a command line argument.
+
+We need to keep in mind, that issue should NOT lead to hacks in the virtualization layer of RTEMS.
+It is more of a hypervisor/host issue and needs to be resolved in this scope and this scope only.
+
+How can we start RTEMS on POK? 
+The closest abstraction to the L4-vCPU I have found in POK is the software partition itself. 
+However, if we can make it, we need to change the partitions SP,IP and EAX register, while running on it. 
+This looks like a hack and not like a careful design. 
+
+But there are other options.
+One I can think of is:
+ *  compiling the library in POK.
+ *  provide the lib to RTEMS and compile the application.
+ *  pass the binary back to POK and combine kernel and binary.
+
+This approach was partly used in the GSoC 2012 project.
+
+Another approach would be :
+ *  compile RTEMS and do a first linking run
+ *  compile POK and pass the partly linked RTEMS file along
+  *  The POK starter function would do the env setup and then call the RTEMS start() (0x10000c)
 =  Virtual CPU Issue  =