Xen 
 
Home About Xen.org Xen Xen Summit Wiki Mailing List Bug Tracker Xen Downloads
 
   
 

xen-devel

Re: [Xen-devel] guest kexec / domU boot loader

To: "Gerd Hoffmann" <kraxel@xxxxxxx>
Subject: Re: [Xen-devel] guest kexec / domU boot loader
From: "Jacob Gorm Hansen" <jacobg@xxxxxxx>
Date: Fri, 10 Mar 2006 15:11:29 +0100
Cc: Xen devel list <xen-devel@xxxxxxxxxxxxxxxxxxx>
Delivery-date: Fri, 10 Mar 2006 14:12:21 +0000
Domainkey-signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:sender:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references; b=B+Zkp9/VOO0iOLy5+ZWCCqwUtA1+57uc7ZUD0WmBGEK3ptjd54pD6sUsr2TgFXZPfPO+SIiVEXKTy7oRMomstxH+kcjzf0GI+l8YoGRZ0LEn/Njbfd6wIGrPwG+PGxiTgQNUNV03CZ2AY4ZNDPjS0F620VJtcoa/nHge6CGZ9+4=
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
In-reply-to: <44115A90.2050303@xxxxxxx>
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>
References: <44115A90.2050303@xxxxxxx>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
On 3/10/06, Gerd Hoffmann <kraxel@xxxxxxx> wrote:
>   Hi,
>
> I have some more few question/problems wrt. kexec.  They are not
> strictly kexec-related, I think any complete control pass-over from one
> kernel to another has them, i.e. if someone wants to combine mini-os and
> grub to build a boot loader the same issues will come up:

> Problem number one are the different "magic" pages: start info, shared
> info, xenstore, console.  Right now they are allocated at a random place
> in guest physical memory (depending on kernel and initrd size).  One
> problem with that is that they are in the area where you might want to
> load a kernel to.  Sure you can map them somewhere else in virtual
> space, but if you want to keep things very simple for a mini-kernel or
> bootloader and create a simple virt==phys identity-mapping it's a nasty
> special case.

I may be repeating myself here, but if you have a look at the file
linux_loader.c in extras/cstrap, in my tree at
http://www.distlab.dk/hg/index.cgi/xen-gfx.hg , you should see a
solution to the problem of these special pages. Since the domU
bootloader sets up the virtual space of the guest (code mostly pasted
from xc_linux_build.c), pointing the relevant virtual addresses to the
correct mfns (from the start info page) by overriding entries in the
page_array[] is fairly trivial.

Best regards,
Jacob

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