WARNING - OLD ARCHIVES

This is an archived copy of the Xen.org mailing list, which we have preserved to ensure that existing links to archives are not broken. The live archive, which contains the latest emails, can be found at http://lists.xen.org/
   
 
 
Xen 
 
Home Products Support Community News
 
   
 

xen-arm

RE: [XenARM] Question about EmbeddedXen's Status

To: Parth Patel <parthvpatel@xxxxxxxxx>, xen-arm <xen-arm@xxxxxxxxxxxxxxxxxxx>
Subject: RE: [XenARM] Question about EmbeddedXen's Status
From: ROSSIER Daniel <Daniel.Rossier@xxxxxxxxxx>
Date: Fri, 31 Oct 2008 18:05:51 +0100
Accept-language: fr-FR, en-US
Acceptlanguage: fr-FR, en-US
Cc:
Delivery-date: Fri, 31 Oct 2008 10:06:00 -0700
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
In-reply-to: <38a53f9a0810300621i77ed8d95j50b30cebb64a8e95@xxxxxxxxxxxxxx>
List-help: <mailto:xen-arm-request@lists.xensource.com?subject=help>
List-id: Xen ARM development <xen-arm.lists.xensource.com>
List-post: <mailto:xen-arm@lists.xensource.com>
List-subscribe: <http://lists.xensource.com/mailman/listinfo/xen-arm>, <mailto:xen-arm-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/mailman/listinfo/xen-arm>, <mailto:xen-arm-request@lists.xensource.com?subject=unsubscribe>
References: <38a53f9a0810290008mb6267c2kb75bf688e68e0bb0@xxxxxxxxxxxxxx> <D39BC4B7B612C6428144D37C54379A2FE0C146345F@xxxxxxxxxxxxxxxxxxxxxxxx> <38a53f9a0810300621i77ed8d95j50b30cebb64a8e95@xxxxxxxxxxxxxx>
Sender: xen-arm-bounces@xxxxxxxxxxxxxxxxxxx
Thread-index: Ack6knCaZ4QK34vXRIKq+6PzDuRP4gA4U0UQ
Thread-topic: [XenARM] Question about EmbeddedXen's Status
> -----Original Message-----
> From: Parth Patel [mailto:parthvpatel@xxxxxxxxx]
> Sent: jeudi, 30. octobre 2008 14:22
> To: ROSSIER Daniel
> Subject: Re: [XenARM] Question about EmbeddedXen's Status
>
> Thank you for you prompt reply. I, too, am looking forward to work on
> this project and keep everybody else updated on my progress.
> I have few more questions, though.
>
> I understand that this initial code is from Mr. Davis (MontaVista). Can
> you let me know which Xen modules have been completed so that I can
> work on other modules for PXA27x?

Right now, we have no modules which are enabled. We will have a bootable Linux 
integrating the Xen code, but
without starting the hypervisor.
I propose that you wait a couple of days while we're solving the last issues so 
that you will be able to help us in enabling step-by-step the different 
functions.

Patrick, on the other hand, is getting the bootstrap code from Samsung (xen-arm 
project) into an original XEN tree (3.1) on i.MX21, before going forward to the 
i.MX31.

> Also, how do I enable the available Xen Hypervisor functions?

Enabling the functions will consist in un-commenting each function call in the 
main setup function provided that the memory has been correctly configured. 
Again, Samsung's port will be essential for this part.

>
> Thank You.
> Parth
> On Wed, Oct 29, 2008 at 12:47 AM, ROSSIER Daniel <Daniel.Rossier@heig-
> vd.ch> wrote:
>
> > -----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

<Prev in Thread] Current Thread [Next in Thread>