From: Glauber Costa <glommer@redhat.com>
To: qemu-devel@nongnu.org
Cc: bochs-developers@lists.sourceforge.net, kvm@vger.kernel.org
Subject: [Qemu-devel] [PATCH] compute checksum for roms bigger than a segment
Date: Mon, 23 Mar 2009 18:55:01 -0300 [thread overview]
Message-ID: <1237845301-15796-1-git-send-email-glommer@redhat.com> (raw)
Some option roms (e1000 provided by gpxe project as an example)
are bigger than a segment. The current algorithm to compute the
checksum fails in such case. To proper compute the checksum, this
patch deals with the possibility of the rom's size crossing a
segment border.
We don't need to worry about it crossing more than one segment
border, since the option roms format only save one byte to store
the image size (thus, maximum size = 0xff = 128k = 2 segments)
Signed-off-by: Glauber Costa <glommer@redhat.com>
---
bios/rombios.c | 33 +++++++++++++++++++++++++++------
1 files changed, 27 insertions(+), 6 deletions(-)
diff --git a/bios/rombios.c b/bios/rombios.c
index bc43251..6fede17 100644
--- a/bios/rombios.c
+++ b/bios/rombios.c
@@ -10162,22 +10162,43 @@ no_serial:
ret
rom_checksum:
- push ax
- push bx
- push cx
+ pusha
+ push ds
+
xor ax, ax
xor bx, bx
xor cx, cx
+ xor dx, dx
+
mov ch, [2]
shl cx, #1
+
+ jnc checksum_loop
+ mov dx, cx
+ mov cx, #0xffff
+
checksum_loop:
add al, [bx]
inc bx
loop checksum_loop
+
+ cmp dx, #0
+ je checksum_out
+
+ add al, [bx]
+ mov cx, dx
+ mov dx, ds
+ add dx, #0x1000
+ mov ds, dx
+ xor dx, dx
+ xor bx, bx
+
+ jmp checksum_loop
+
+checksum_out:
and al, #0xff
- pop cx
- pop bx
- pop ax
+ pop ds
+ popa
ret
--
1.6.1.2
next reply other threads:[~2009-03-23 21:58 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-03-23 21:55 Glauber Costa [this message]
-- strict thread matches above, loose matches on Subject: below --
2009-03-23 23:23 [Qemu-devel] [PATCH] compute checksum for roms bigger than a segment Glauber Costa
2009-03-24 0:48 ` malc
2009-03-24 1:02 ` Glauber Costa
2009-03-24 1:27 ` malc
2009-03-24 1:53 ` Glauber Costa
2009-03-24 3:14 ` malc
2009-03-25 15:06 Glauber Costa
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=1237845301-15796-1-git-send-email-glommer@redhat.com \
--to=glommer@redhat.com \
--cc=bochs-developers@lists.sourceforge.net \
--cc=kvm@vger.kernel.org \
--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).