From: Alexander Graf <agraf@suse.de>
To: qemu-devel@nongnu.org
Subject: [Qemu-devel] [PATCH] Make -kernel for linux work with bochsbios
Date: Tue, 17 Nov 2009 17:49:16 +0100 [thread overview]
Message-ID: <1258476556-32472-1-git-send-email-agraf@suse.de> (raw)
While trying to run -kernel with -bios pc-bios/pcbios.bin, I realized
that I was actually writing data to %es, but only set up %ds to a 32-bit
segment we want to write to.
So at the end of the day the data hasn't actually been copied. Oops.
So here's a fix to set ES instead of DS, which makes -kernel work with
BOCHS bios again (and actually makes the code do the correct thing)!
Signed-off-by: Alexander Graf <agraf@suse.de>
---
pc-bios/optionrom/linuxboot.S | 10 +++++-----
1 files changed, 5 insertions(+), 5 deletions(-)
diff --git a/pc-bios/optionrom/linuxboot.S b/pc-bios/optionrom/linuxboot.S
index 08c1ca6..ecd9cf2 100644
--- a/pc-bios/optionrom/linuxboot.S
+++ b/pc-bios/optionrom/linuxboot.S
@@ -102,11 +102,11 @@ copy_kernel:
mov $1, %eax
mov %eax, %cr0
- /* So we can set DS to a 32-bit segment */
+ /* So we can set ES to a 32-bit segment */
mov $0x10, %eax
- mov %eax, %ds
+ mov %eax, %es
- /* We're now running in 16-bit CS, but 32-bit DS! */
+ /* We're now running in 16-bit CS, but 32-bit ES! */
/* Load kernel and initrd */
read_fw_blob(FW_CFG_KERNEL)
@@ -118,9 +118,9 @@ copy_kernel:
mov $0, %eax
mov %eax, %cr0
- /* DS = CS */
+ /* ES = CS */
mov %cs, %ax
- mov %ax, %ds
+ mov %ax, %es
jmp boot_kernel
--
1.6.0.2
next reply other threads:[~2009-11-17 16:49 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-11-17 16:49 Alexander Graf [this message]
2009-11-30 13:10 ` [Qemu-devel] [PATCH] Make -kernel for linux work with bochsbios Alexander Graf
2009-11-30 13:50 ` [Qemu-devel] " Paolo Bonzini
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1258476556-32472-1-git-send-email-agraf@suse.de \
--to=agraf@suse.de \
--cc=qemu-devel@nongnu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).