From mboxrd@z Thu Jan  1 00:00:00 1970
From: Bharadwaj Yadavalli <bharadwaj.yadavalli@hp.com>
Subject: [Q] GRUB -> __start_xen?
Date: Fri, 24 Jun 2005 14:25:42 -0400
Message-ID: <20050624182542.GC339769@marburg.zko.dec.com>
Reply-To: Bharadwaj Yadavalli <bharadwaj.yadavalli@hp.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Return-path: <xen-devel-bounces@lists.xensource.com>
Content-Disposition: inline
List-Unsubscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-devel>,
	<mailto:xen-devel-request@lists.xensource.com?subject=unsubscribe>
List-Post: <mailto:xen-devel@lists.xensource.com>
List-Help: <mailto:xen-devel-request@lists.xensource.com?subject=help>
List-Subscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-devel>,
	<mailto:xen-devel-request@lists.xensource.com?subject=subscribe>
Sender: xen-devel-bounces@lists.xensource.com
Errors-To: xen-devel-bounces@lists.xensource.com
To: xen-devel@lists.xensource.com
List-Id: xen-devel@lists.xenproject.org

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