From: Paul Brook <paul@codesourcery.com>
To: qemu-devel@nongnu.org
Subject: [Qemu-devel] Ram allocation changes
Date: Sat, 11 Apr 2009 18:16:32 +0100 [thread overview]
Message-ID: <200904111816.32463.paul@codesourcery.com> (raw)
After my recent set of changes, qemu supports dynamic allocations of guest
ram. Previously all guest ram had to be preallocated before device/board
initialization. This provides most of the infrastructure necessary for
memory hotplug, and is a prerequisite for machine config files. There should
be no user visible changes.
I've tested as many targets as I can. If your favourite target dies with "Bad
ram offset" then the most likely cause is that the board needs to allocate
its ram with qemu_ram_alloc, rather than blindly assuming it exists.
Paul
next reply other threads:[~2009-04-11 17:16 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-04-11 17:16 Paul Brook [this message]
2009-04-14 7:42 ` [Qemu-devel] Ram allocation changes Markus Armbruster
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=200904111816.32463.paul@codesourcery.com \
--to=paul@codesourcery.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).