GSoC RTEMS compilation issues

[Cláudio Silva]

> Counterquestion: Which steps are required to make a BSP "para-virtualized"
> and how is such a BSP different from an "ordinary BSP".

I think the question is that the functions available on
cpukit/score/cpu/* are not required for a paravirtualized BSP (e.g.
Context_Switch, Interrupt Handling).

You can maybe protect those files with an "#ifdef
BSP_PROVIDES_CONTEXT_SWITCH" or something like that.
If these functions can be cpu independent system calls to the
hypervisor maybe defining an cpukit/score/cpu/paravirt is the best
option. You can think of it as an "virtual CPU" provided by the
hypervisor that is independent from the real architecture.

Regards,
Cláudio


On Thu, Jun 21, 2012 at 9:47 AM, Ralf Corsepius
<ralf.corsepius at rtems.org> wrote:
> On 06/21/2012 10:09 AM, Julien Delange wrote:
>>
>>
>> So that it builds and install the pc386 adapted for virtualisation.
>
>
> Counterquestion: Which steps are required to make a BSP "para-virtualized"
> and how is such a BSP different from an "ordinary BSP".
>
> Ralf
>
> _______________________________________________
> rtems-devel mailing list
> rtems-devel at rtems.org
> http://www.rtems.org/mailman/listinfo/rtems-devel