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-devel

[Xen-devel] [Q] GRUB -> __start_xen?

To: xen-devel@xxxxxxxxxxxxxxxxxxx
Subject: [Xen-devel] [Q] GRUB -> __start_xen?
From: Bharadwaj Yadavalli <bharadwaj.yadavalli@xxxxxx>
Date: Fri, 24 Jun 2005 14:25:42 -0400
Delivery-date: Fri, 24 Jun 2005 18:24:46 +0000
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
List-help: <mailto:xen-devel-request@lists.xensource.com?subject=help>
List-id: Xen developer discussion <xen-devel.lists.xensource.com>
List-post: <mailto:xen-devel@lists.xensource.com>
List-subscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=unsubscribe>
Mail-followup-to: xen-devel@xxxxxxxxxxxxxxxxxxx
Reply-to: Bharadwaj Yadavalli <bharadwaj.yadavalli@xxxxxx>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
User-agent: Mutt/1.3.99i
I am trying to understand the internals of Xen.

On x86 (and may be other architectures), it appears to me 
that xen's entry point is 

         void __init __start_xen(multiboot_info_t *mbi)

that lives in xeno-unstable.bk/xen/arch/x86/setup.c.

1. Who builds the structure mbi and calls __start_xen?
2. How is __satrt_xen registered as the entry point?

Is there a place that I can read to understand the transfer
of control from multiboot GRUB to xen's entry point?

Thanks,

Bharadwaj

_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-devel

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