<div style="line-height:1.7;color:#000000;font-size:14px;font-family:arial"><pre>Hi Joel, I am very sorry for making you mistake. That AIR use PMK instand of
POK. PMK is hyper visor kernel which response for scheduling.
</pre><div></div><div id="divNeteaseMailCard"></div><br>ÔÚ 2012-03-16 23:14:29£¬"Joel Sherrill" <joel.sherrill@oarcorp.com> дµÀ£º<br> <blockquote id="isReplyContent" style="PADDING-LEFT: 1ex; MARGIN: 0px 0px 0px 0.8ex; BORDER-LEFT: #ccc 1px solid">
On 03/16/2012 09:14 AM, ÕÅÎÄ½Ü wrote:
<blockquote cite="mid:5fbd9bd2.2c960.1361bdba5fe.Coremail.157724595@163.com" type="cite">
<div style="line-height: 1.7; color: rgb(0, 0, 0); font-size:
14px; font-family: arial;">Hi, all:<br>
I am the student who implement the GSOC2011 project
hypervisor for RTEMS.<br>
In my original proposal i wanted port the linux to the RTEMS
paravirtualization hypervisor<br>
named AIR. But as the progress of project, the plan had changed
into adapt the <br>
lastest RTEMS to the AIR hypervisor. So what i did is make the
lastest RTEMS run <br>
under AIR successfully which contains a paravirtualization RTEMS
kernel named <br>
POK. If you want to know any information please free to contact
me<br>
<br>
</div>
</blockquote>
:) We are very interested. I didn't realize that AIR used Pok. Since
I couldn't<br>
get access to AIR, I was refocusing on Pok. Julien Delange is
responsible for <br>
Pok. <br>
<br>
We would like to see RTEMS as a proper client under Pok and
eventually<br>
support the ARINC-653 API that way. So getting your BSP into proper
shape<br>
on the RTEMS head and making sure others can run it is a BIG deal.<br>
From there, we can begin to support other architectures supported by
Pok<br>
and provide application level ARINC services.<br>
<blockquote cite="mid:5fbd9bd2.2c960.1361bdba5fe.Coremail.157724595@163.com" type="cite">
<div style="line-height:1.7;color:#000000;font-size:14px;font-family:arial">
<pre>At 2012-03-16 06:47:16,"Julien Delange" <a class="moz-txt-link-rfc2396E" href="mailto:julien.delange@gmail.com"><julien.delange@gmail.com></a> wrote:
>On Thu, Mar 15, 2012 at 6:44 PM, WL <a class="moz-txt-link-rfc2396E" href="mailto:jolkaczad@gmail.com"><jolkaczad@gmail.com></a> wrote:
>> This is all valuable stuff, and the topic is getting more interesting
>> by the minute. I see that this would somewhat pick up where a last
>> year's GSoC project left off. Is the student still active in the
>> community? If not ,did he leave his work in a useable state? I'd like
>> to contact him since there's no need to do the same research again and
>> come to conclusions which have already been arrived at.
>
>Hello,
>
>Please have a look the the links below. Also, the whole project has
>several goals :
>1. Implement ARINC653 services in RTEMS. If you consider RTEMS only,
>you can only design intra-partition services (tasks, intra-partition
>comm. , etc ...). This is described in [3].
>2. Implement a prototype of a hypervisor to execute several RTEMS
>instance in different partitions (see proposal [4]). In that case, the
>work consists in (1) design a first prototype to execute RTEMS in
>several partition and (2) adapt RTEMS to call the hypervisor services
>for inter-partitions interactions. Once that is done, we can also
>implement ARINC653 inter-partitions services.
>
>So, implementing full ARINC653 compliance for RTEMS would require to
>do both tasks. The second project is more difficult but has more
>priority since this would be the fundation for building partitions
>using RTEMS. In addition, making the partitioned-bsp of RTEMS would be
>really tricky because it has to be as much generic as possible to fit
>with other separation kernel approaches (as AIR, XtratuM or POK).
>
>As far as I know, the GSOC 2011 project focuses on the second item of
>the work. It was based on AIR but unfortunately, it does not seem
>available (you can check on <a class="moz-txt-link-freetext" href="http://air.di.fc.ul.pt/">http://air.di.fc.ul.pt/</a>). However, the
>report of this work is available as gdoc documents, you have to
>request access to it, links to ask are located on page [2]. Also, Joel
>may have more information about the status of the 2011 GSOC project
>related to this topic.
>
>Hope that helps,
>
>[1] <a class="moz-txt-link-freetext" href="http://wiki.rtems.org/wiki/index.php/RTEMSHyperVisor">http://wiki.rtems.org/wiki/index.php/RTEMSHyperVisor</a>
>[2] <a class="moz-txt-link-freetext" href="http://wiki.rtems.org/wiki/index.php/RTEMSSummerOfCode2011">http://wiki.rtems.org/wiki/index.php/RTEMSSummerOfCode2011</a>
>[3] <a class="moz-txt-link-freetext" href="http://wiki.rtems.org/wiki/index.php/ARINC653API">http://wiki.rtems.org/wiki/index.php/ARINC653API</a>
>[4] <a class="moz-txt-link-freetext" href="http://wiki.rtems.org/wiki/index.php/RTEMS_Paravirtualization">http://wiki.rtems.org/wiki/index.php/RTEMS_Paravirtualization</a>
>_______________________________________________
>rtems-users mailing list
><a class="moz-txt-link-abbreviated" href="mailto:rtems-users@rtems.org">rtems-users@rtems.org</a>
><a class="moz-txt-link-freetext" href="http://www.rtems.org/mailman/listinfo/rtems-users">http://www.rtems.org/mailman/listinfo/rtems-users</a>
</pre>
</div>
<br>
<br>
<span title="neteasefooter"><span id="netease_mail_footer"></span></span>
</blockquote>
<br>
<br>
<pre class="moz-signature" cols="72">--
Joel Sherrill, Ph.D. Director of Research& Development
<a class="moz-txt-link-abbreviated" href="mailto:joel.sherrill@OARcorp.com">joel.sherrill@OARcorp.com</a> On-Line Applications Research
Ask me about RTEMS: a free RTOS Huntsville AL 35805
Support Available (256) 722-9985
</pre>
</blockquote></div><br><br><span title="neteasefooter"><span id="netease_mail_footer"></span></span>