[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[Qemu-devel] [Bug 1273944] Re: multiboot header has 0 in mem_upper field
From: |
Peter Chubb |
Subject: |
[Qemu-devel] [Bug 1273944] Re: multiboot header has 0 in mem_upper field |
Date: |
Wed, 29 Jan 2014 04:27:49 -0000 |
This change fixes it.
diff --git a/exec.c b/exec.c
index 2435d9e..b387d28 100644
--- a/exec.c
+++ b/exec.c
@@ -1070,7 +1070,7 @@ static void *file_ram_alloc(RAMBlock *block,
}
/* MAP_POPULATE silently ignores failures */
- for (i = 0; i < (memory/hpagesize); i++) {
+ for (i = 0; i < (memory/hpagesize)-1; i++) {
memset(area + (hpagesize*i), 0, 1);
}
address@hidden:/usr/src/qemu/tests/m
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bugs/1273944
Title:
multiboot header has 0 in mem_upper field
Status in QEMU:
New
Bug description:
When booting a multiboot image,. mem_upper is now always zero.
To test, build qemu from current git head, then do
cd tests/multiboot
./run_test.sh
You will see the test fail. In each case mem_upper is 0k.
git-bisect says the bad commit is
0169c511554cb0014a00290b0d3d26c31a49818f in qemu.git
To manage notifications about this bug go to:
https://bugs.launchpad.net/qemu/+bug/1273944/+subscriptions
[Prev in Thread] |
Current Thread |
[Next in Thread] |