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] Re: xen-kernel and EDD

To: "Keir Fraser-5 [via Xen]" <ml-node+4714940-222445260-235647@xxxxxxxxxxxxx>, xen-devel@xxxxxxxxxxxxxxxxxxx
Subject: [Xen-devel] Re: xen-kernel and EDD
From: Lin-Bao Zhang <2004.zhang@xxxxxxxxx>
Date: Fri, 19 Aug 2011 17:51:31 +0800
Cc:
Delivery-date: Fri, 19 Aug 2011 02:52:20 -0700
Dkim-signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :content-type; bh=F9YJZu5LkakiEWhIpy3AeNhZ7/pQfbeO4GMUU/DDcok=; b=HQ08pvebzIz6iDIneqoEJFoD23tBbwKDKUVNyoWHZCcWPqQANEte7q0kOVnLispXui KlZipogjMtdMi4MoFtPwKlkvwb0LZZt7XlnXDJY+8CJM/5TaXhvnyEoIdoVl5+5topQZ 4xI31bIHw4/LA9NEmSKSQcuuuzoabT86nmz1o=
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
In-reply-to: <CA73E212.1F72B%keir.xen@xxxxxxxxx>
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/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=unsubscribe>
References: <CANuKePnjCwAePneoAKxXu453naxYVwPTt0hVwtML9KzHBLvS4g@xxxxxxxxxxxxxx> <CA727251.1F62E%keir.xen@xxxxxxxxx> <CANuKePmurLWCEEJVzbQv2hSzccUiE-NHDkuVddgyRyXapb9Znw@xxxxxxxxxxxxxx> <CA72B048.30827%keir@xxxxxxx> <CANuKePmOd7h2qiG=8AmyXqza805sEeg-o6csHpTM5fE+XK-6pA@xxxxxxxxxxxxxx> <CANuKePm+UHOaVU2c5DbTL2qcRRCssU-PZHbT_2c-86YqSMHhpw@xxxxxxxxxxxxxx> <CA73E212.1F72B%keir.xen@xxxxxxxxx>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
2011/8/19 Keir Fraser-5 [via Xen]
<ml-node+4714940-222445260-235647@xxxxxxxxxxxxx>
>
> > it seems that direct number is not very compatible .
> I was just suggesting a minimal patch for you to try.
>
yes, I understand, thanks so much!
it seems that this stack indeed overlap my EBDA area wrongly.
any arbitrary or fixed value for this stack will cause un-expect error.

from higher xen-4.1.0 :
 mov     $bootsym_phys(early_stack),%esp
call    cmdline_parse_early
I guess , the author want to setup stack after trampoline code, from
symbols , we can see early_stack value is same as trampoline_end(from
sles11, I think rhel5.7 should be same).
the key points are stack beginning address and its length can't
overlap BIOS conventional area, i.e. EBDA.

how can we think out the length of this stack ?  xen developer must
make sure the length can't overlap EBDA? how to make sure it by method
?
I suppose xen-kernel should pre-know EBDA 's beginning address
,because xen can know space reserved by e820 output.

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