From mboxrd@z Thu Jan  1 00:00:00 1970
From: Keir Fraser <keir.xen@gmail.com>
Subject: Re: Re: define BOOT_TRAMPOLINE and stack based on result
	of probing EBDA area by INT12
Date: Wed, 31 Aug 2011 20:57:50 +0100
Message-ID: <CA8450CE.20119%keir.xen@gmail.com>
References: <20110831202518.1bc4cf08@lxorguk.ukuu.org.uk>
Mime-Version: 1.0
Content-Type: text/plain;
	charset="ISO-8859-1"
Content-Transfer-Encoding: quoted-printable
Return-path: <xen-devel-bounces@lists.xensource.com>
In-Reply-To: <20110831202518.1bc4cf08@lxorguk.ukuu.org.uk>
List-Unsubscribe: <http://lists.xensource.com/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/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: Alan Cox <alan@lxorguk.ukuu.org.uk>
Cc: "xen-devel@lists.xensource.com" <xen-devel@lists.xensource.com>, Lin-bao Zhang <zhang.linbao@yahoo.com>
List-Id: xen-devel@lists.xenproject.org

On 31/08/2011 20:25, "Alan Cox" <alan@lxorguk.ukuu.org.uk> wrote:

> On Wed, 31 Aug 2011 09:55:10 +0100
> Keir Fraser <keir@xen.org> wrote:
>=20
>> On 31/08/2011 09:47, "Lin-bao Zhang" <zhang.linbao@yahoo.com> wrote:
>>=20
>>> 1,define a variable named "EBDA_bottom".
>>> 2, get EBDA_bottom by above method.
>>> 3, stack should equals EBDA_bottom (or EBDA_bottom -1 safely)
>>> 4, mov     $(EBDA_bottom -1),%esp
>>> in most case , EBDA area is 1K,but we define 0x7c000(this is absolutely
>>> safe),but we will waste too much memory space.
>>>=20
>>> I did test, it can work .Certainly, I am familiar with assembler code, =
I
>>> just
>>> hard code to test:mov     0x903ff , %esp=A0thanks for your corrections , =
I
>>> have
>>> not read over all histories and stories about them, if I am wrong , I a=
m
>>> sorry
>>> first.
>>=20
>> If you actually tried to implement it you'd realise you're stuck.
>=20
> Re-read the original. The EBDA is accessible at BIOS segment offset 0E.
> You don't need to make a BIOS call to read it, just load the location and
> check it against 0.W in which case one isn't present.
>=20
> At that point you know where to put your bits.
>=20
> Obviously once you get into the world of EFI and the like there are
> different ways all this should occur, but for good old BIOS stuff it
> works fine.

Ah, makes sense. And our real-mode code is now relocatable, which was
implemented as part of support for EFI. That could be used to dynamically
relocate below EBDA for legacy BIOS too.

 -- Keir