Paravirtualization project - GSOC 2013

Philipp Eppelt philipp.eppelt at
Tue May 14 07:30:31 UTC 2013

On 05/14/2013 06:48 AM, Aaron J. Grier wrote:
> (late to the party)
> On Tue, Apr 16, 2013 at 09:54:11AM -0400, Gedare Bloom wrote:
>> It seems to me that there would only need to be one para-virtualized
>> CPU model and BSP for each architecture? I think it would be better to
>> add a single paravirt CPU and one BSP for that CPU to each
>> architecture. We can make the name unique by doing something like...
>> ${arch}virt.
> how would this accomodate multiple hypervisors per platform?  on amd64 I
> can run Xen, KVM, L4, VMware, and potentially others...  each has a
> different hypervisor interface.

The introduced layer defines a set of functions. The host/hypervisor is 
required to implement these functions and to provide them to RTEMS in 
the form of a library.

Therefore the interface inside RTEMS doesn't change and one BSP per 
architecture is enough.


More information about the users mailing list