From mboxrd@z Thu Jan  1 00:00:00 1970
Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43)
	id 1L0WpT-0000g7-Td
	for qemu-devel@nongnu.org; Thu, 13 Nov 2008 02:41:27 -0500
Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43)
	id 1L0WpS-0000ft-DM
	for qemu-devel@nongnu.org; Thu, 13 Nov 2008 02:41:26 -0500
Received: from [199.232.76.173] (port=34773 helo=monty-python.gnu.org)
	by lists.gnu.org with esmtp (Exim 4.43) id 1L0WpS-0000fq-5i
	for qemu-devel@nongnu.org; Thu, 13 Nov 2008 02:41:26 -0500
Received: from mx2.redhat.com ([66.187.237.31]:60490)
	by monty-python.gnu.org with esmtp (Exim 4.60)
	(envelope-from <gleb@redhat.com>) id 1L0WpR-0007pZ-I8
	for qemu-devel@nongnu.org; Thu, 13 Nov 2008 02:41:25 -0500
Date: Thu, 13 Nov 2008 09:41:26 +0200
From: Gleb Natapov <gleb@redhat.com>
Message-ID: <20081113074126.GI20617@redhat.com>
References: <20081110091134.11822.34230.stgit@dhcp-1-237.local>
	<20081110091159.11822.26753.stgit@dhcp-1-237.local>
	<16C4151DCE3D406091E6AC948C8CA8A3@FSCPC>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <16C4151DCE3D406091E6AC948C8CA8A3@FSCPC>
Subject: [Qemu-devel] Re: [Bochs-developers] [PATCH v3 5/6] Don't use
	unreserved memory inBIOS.
Reply-To: qemu-devel@nongnu.org
List-Id: qemu-devel.nongnu.org
List-Unsubscribe: <http://lists.nongnu.org/mailman/listinfo/qemu-devel>,
	<mailto:qemu-devel-request@nongnu.org?subject=unsubscribe>
List-Archive: <http://lists.gnu.org/pipermail/qemu-devel>
List-Post: <mailto:qemu-devel@nongnu.org>
List-Help: <mailto:qemu-devel-request@nongnu.org?subject=help>
List-Subscribe: <http://lists.nongnu.org/mailman/listinfo/qemu-devel>,
	<mailto:qemu-devel-request@nongnu.org?subject=subscribe>
To: Sebastian Herbszt <herbszt@gmx.de>
Cc: bochs-developers@lists.sourceforge.net, qemu-devel@nongnu.org

On Thu, Nov 13, 2008 at 01:43:35AM +0100, Sebastian Herbszt wrote:
>> @@ -10032,8 +10032,11 @@ rombios32_05:
>>   mov gs, ax
>>   cld
>>
>> -  ;; init the stack pointer
>> -  mov esp, #0x00080000
>> +  ;; init the stack pointer to point below EBDA
>> +  mov ax, [0x040e]
>> +  shl eax, #4
>> +  mov esp, #-0x10
>> +  add esp, eax
>
> This could be a problem if the OS decides to put the wakeup
> vector just below the EBDA. But as long as the EBDA is located
> above 0x9f000 it should be ok and this can be changed later.
>
The other problem is that extended ROM can relocate EBDA below 0x9f000.
I don't think that should stop us from applying this patch series :)

--
			Gleb.