From: Zhu Guihua <zhugh.fnst@cn.fujitsu.com>
To: qemu-devel@nongnu.org
Cc: imammedo@redhat.com, Zhu Guihua <zhugh.fnst@cn.fujitsu.com>,
mst@redhat.com
Subject: [Qemu-devel] [PATCH] pc-dimm: fix checking for backend memory size
Date: Fri, 16 Jan 2015 13:45:06 +0800 [thread overview]
Message-ID: <1421387106-19101-1-git-send-email-zhugh.fnst@cn.fujitsu.com> (raw)
If hot add 100MiB memory like this:
(monitor) object_add memory-backend-ram,id=ram0,size=100M
(monitor) device_add pc-dimm,id=d0,memdev=ram0
The hotplug operation will faile, and the guest will print error message:
Section-unaligned hotplug range: start 0x100000000, size 0x6400000
acpi PNP0C80:00: add_memory failed
acpi PNP0C80:00: acpi_memory_enable_device() error
Then I found that, according to the func check_hotplug_memory_range() in linux
kernel, backend memory size must be multiple of 128MiB, not 2MiB.
So this patch checks whether backend memory size is multiple of 128MiB.
Signed-off-by: Zhu Guihua <zhugh.fnst@cn.fujitsu.com>
---
hw/mem/pc-dimm.c | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/hw/mem/pc-dimm.c b/hw/mem/pc-dimm.c
index d431834..3b8a015 100644
--- a/hw/mem/pc-dimm.c
+++ b/hw/mem/pc-dimm.c
@@ -161,9 +161,9 @@ uint64_t pc_dimm_get_free_addr(uint64_t address_space_start,
goto out;
}
- if (QEMU_ALIGN_UP(size, align) != size) {
+ if (QEMU_ALIGN_UP(size, align * 64) != size) {
error_setg(errp, "backend memory size must be multiple of 0x%"
- PRIx64, align);
+ PRIx64, align * 64);
goto out;
}
--
1.9.3
next reply other threads:[~2015-01-16 5:46 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-01-16 5:45 Zhu Guihua [this message]
2015-01-16 6:00 ` [Qemu-devel] [PATCH] pc-dimm: fix checking for backend memory size Zhu Guihua
2015-01-19 15:55 ` Igor Mammedov
2015-01-20 1:34 ` Zhu Guihua
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=1421387106-19101-1-git-send-email-zhugh.fnst@cn.fujitsu.com \
--to=zhugh.fnst@cn.fujitsu.com \
--cc=imammedo@redhat.com \
--cc=mst@redhat.com \
--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).