[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

FW: [XenARM] Release of xen-pxa270-qemu


  • To: "xen-arm@xxxxxxxxxxxxxxxxxxx" <xen-arm@xxxxxxxxxxxxxxxxxxx>
  • From: ROSSIER Daniel <Daniel.Rossier@xxxxxxxxxx>
  • Date: Tue, 5 May 2009 12:46:55 +0200
  • Accept-language: fr-FR, en-US
  • Acceptlanguage: fr-FR, en-US
  • Delivery-date: Tue, 05 May 2009 03:47:01 -0700
  • List-id: Xen ARM development <xen-arm.lists.xensource.com>
  • Thread-index: AcnNZAlF6vQQARZ3QX+Rq+R1CsXQTQACj6BAAAAgM+A=
  • Thread-topic: [XenARM] Release of xen-pxa270-qemu

> -----Original Message-----
> From: kernel cross [mailto:crosskernel@xxxxxxxxx]
> Sent: mardi, 5. mai 2009 11:30
> To: ROSSIER Daniel
> Subject: Re: [XenARM] Release of xen-pxa270-qemu
> 
> where does Xen jump into the dom0's start_kernel()?

Ok, right now only miniOS is used as dom0; the start_kernel_miniOS() function 
located in minios/kernel.c
is called at the end of XEN's bootstrap. Actually, there is a first context 
switch initiated by the XEN scheduler
which passes the control to the domain0 (see construct_dom0()).

I will upload a new release (1.1) which sets up the virtual memory layout 
correctly since we have moved all XEN-related data (heap, frametable, 
mach-to-phys table, etc.) at 0xff000000. I will also send a pdf which shows how 
the memory layout looks like.


> 
> thanks!!!
> 
> 
> 

Daniel


_______________________________________________
Xen-arm mailing list
Xen-arm@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/mailman/listinfo/xen-arm


 


Rackspace

Lists.xenproject.org is hosted with RackSpace, monitoring our
servers 24x7x365 and backed by RackSpace's Fanatical Support®.