|
|
|
|
|
|
|
|
|
|
xen-arm
RE: [XenARM] Question about EmbeddedXen's Status
> -----Original Message-----
> From: xen-arm-bounces@xxxxxxxxxxxxxxxxxxx [mailto:xen-arm-
> bounces@xxxxxxxxxxxxxxxxxxx] On Behalf Of Parth Patel
> Sent: mercredi, 29. octobre 2008 08:08
> To: xen-arm@xxxxxxxxxxxxxxxxxxx
> Subject: [XenARM] Question about EmbeddedXen's Status
>
> Hello Everyone,
>
> I am a student at UCLA working on a project that involves EmbeddedXen.
> We want to port EmbeddedXen to "iMote 2" which has "PXA271" processor.
> The OS we want to put on the Xen is MicroCOS.
>
> I have gone through all the archives in this message list, but could
> not find out the exact status for the EmbeddedXen project. I know that
> you guys are still working on Linux to put on Xen and the processor you
> have used is PXA270, but is the porting of Xen onto the PXA270
> completely done? If so, is there any documentation that I can use to
Yes that's right; we are currently working on it; actually, we have started
having a look at the
strategy of porting including Samsung's port on i.MX21. But, we are adopting a
different approach:
we are actually considering two approaches, on two different targets:
1) The first approach consists in integrating XEN 3.1 tree within the Linux
(2.6.18) tree. We have solved all conflict issues, but it still remains some
problems we are debugging now. The target is the Colibri/PXA270 platform. We
will then slightly *enable* all functionalities of the hypervisor, putting in
place our porting strategy (regarding MM, IRQ, Timer and syscalls/hypercalls).
So far, we are not working on a more secure layer as Samsung did with their
port. However, we will port a realtime OS - mainly Xenomai/Linux - replacing
the Adeos/I-pipe nanokernel by some enhancements of our hypervisor.
2) The second approach is more close to Samsung's work: we start from the
original XEN tree and we migrate all arch-/CPU-specific code issued from the
Linux 2.6.18 tree in it. This approach is currently based on a i.MX31 platform;
we aim at investigating to what extend the armv6 instruction can improve the
virtualization mechanisms. We are still at the beginning of this work.
We plan the work on 1-Year project and will appreciate all contributions to
these two approaches. So please do not hesitate to report your work process in
this mailing list, and we also keep all informed about our progress.
> port EmbeddedXen to different processor? Also, what specific files I
> need to port to any processor?
>
> Please let me know.
>
> Thank you.
>
> Parth
Daniel
_______________________________________________
Xen-arm mailing list
Xen-arm@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/mailman/listinfo/xen-arm
|
|
|
|
|