- Timestamp:
-
09/18/13 18:35:18 (11 years ago)
- Author:
-
Phipse
- Comment:
-
L4Re as a hypervisor to RTEMS
Legend:
- Unmodified
- Added
- Removed
- Modified
-
v44
|
v45
|
|
440 | 440 | For instance a time_warp function for the clock interrupt is needed. |
441 | 441 | Claudio da Silva has provided one [https://gist.github.com/cdcs/5874932 here]. |
| 442 | |
| 443 | = More Hypervisors (L4Re) = |
| 444 | |
| 445 | |
| 446 | The concept of the virtualization layer should be portable. |
| 447 | I write should be, because I haven't tested it. |
| 448 | From my point of view, it should be an easy task to port the virtualpok BSP to L4Re. |
| 449 | L4Re provides a full vCPU interface and library functions to control it. |
| 450 | Compared to POK this is heaven. |
| 451 | |
| 452 | In my previous attempt to virtualize RTEMS on L4Re, before this project, I made L4Re load the RTEMS binary and then configure the vCPU to start at the binaries entry point, etc. . |
| 453 | This approach required the RTEMS binary to be analysed at compile-time of the L4Re application. |
| 454 | Also RTEMS was modified. Back then I introduced a new CPU target called l4vcpu, which was mostly a copy of the i386 CPU target. |
| 455 | The L4RTEMS project can be found on [https://github.com/phipse/L4RTEMS github] |
| 456 | |
| 457 | With the virtualization layer this changes. |
| 458 | RTEMS needs a library provided by L4Re to compile and then the binary can be loaded the same way. |
| 459 | So it doesn't need to be present at compile time. |
| 460 | Furthermore, it we should be able to reuse the virtualpok BSP, provided we replace libpart.a with a library provided by L4Re. |
| 461 | |
442 | 462 | = References = |
443 | 463 | |