[GSoC 2014] Paravirtualization layer in RTEMS

[Youren Shen]

Hi, everyone and Philipp:

I'm really interesting in Paravirtializaion and I have write a proposal[1]
for the project.

I'm trying to design a set of hypercall, i.e. another kind of syscall, to
support the Paravirtualization layer designed by Philipp Eppelt.

Here is my plan:
First, learning the start up steps in POK, especially learning how POK
initial the gdt, idt, and syscall.
Second, learning the work you have already done in POK, then find out the
reason of why we failed to handling interrupt to Guest OS.
Third, design hypercall and give more details.


*Up to now*, I have read the source code about start up in POK, and add
some description in my proposal[1].

What make me confused is the relation between pok_arch_event_register
and pok_meta_handler_init.
It seems you divided the irq vector to two parts in
pok_arch_event_register, Less 32 or more than 32. It looks like you have
already design some hypercall interface. (just like pok_irq_prologue_0 for
clock?)  But what's the meaning​​ of pok_meta_handler_init? I still can't
understand it very clearly.Could you give me some outline about IRQ
handlind in POK which invoke this two functions?

If you can provide me a brief overview about the way how you consider this
Issues and a brief description about your design,  it will be really
helpful to me.

Thank you very much.


[1].
https://docs.google.com/document/d/10ehcM1f2eKNwcNgv5stphGtsVAnYc_K7KLhxmjvE1k8/edit

Best Regards.

Youren Shen.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.rtems.org/pipermail/devel/attachments/20140310/79fea301/attachment.html>