I would like to make one other suggestion, which is: RTEMS_PARAVIRT, and --enable-paravirt. This option is consistent with the language already used to describe what is being done, i.e. paravirtualization of some pieces of RTEMS. All in favor?
-Gedare On Tue, Sep 17, 2013 at 4:26 PM, Joel Sherrill <[email protected]> wrote: > On 9/17/2013 3:21 PM, Chris Johns wrote: >> Gedare Bloom wrote: >>>> >>>> RTEMS_HYPERVISOR or RTEMS_VIRTUAL >>>> >>> I'm preferential to this high-level switch. I would avoid >>> RTEMS_HYPERVISOR, because RTEMS is not the hypervisor, it is the guest >>> VM. >>> >> >> And RTEMS_VIRTUAL could be taken to mean RTEMS supports virtual memory. >> >> What about RTEMS_HYPERVISOR_GUEST ? > > That's a better name. What would the configure option be? > --enable-hypervisor-guest? > >> Chris >> _______________________________________________ >> rtems-devel mailing list >> [email protected] >> http://www.rtems.org/mailman/listinfo/rtems-devel >> > > > > -- > Joel Sherrill, Ph.D. Director of Research & Development > [email protected] On-Line Applications Research > Ask me about RTEMS: a free RTOS Huntsville AL 35805 > Support Available (256) 722-9985 _______________________________________________ rtems-devel mailing list [email protected] http://www.rtems.org/mailman/listinfo/rtems-devel
