From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1Lsgox-0000gn-KM for qemu-devel@nongnu.org; Sat, 11 Apr 2009 13:16:47 -0400 Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1Lsgos-0000eA-JH for qemu-devel@nongnu.org; Sat, 11 Apr 2009 13:16:46 -0400 Received: from [199.232.76.173] (port=38826 helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1Lsgos-0000e4-CW for qemu-devel@nongnu.org; Sat, 11 Apr 2009 13:16:42 -0400 Received: from mx20.gnu.org ([199.232.41.8]:36447) by monty-python.gnu.org with esmtps (TLS-1.0:RSA_AES_256_CBC_SHA1:32) (Exim 4.60) (envelope-from ) id 1Lsgos-0003fq-5Y for qemu-devel@nongnu.org; Sat, 11 Apr 2009 13:16:42 -0400 Received: from mail.codesourcery.com ([65.74.133.4]) by mx20.gnu.org with esmtp (Exim 4.60) (envelope-from ) id 1Lsgon-00078b-HJ for qemu-devel@nongnu.org; Sat, 11 Apr 2009 13:16:37 -0400 From: Paul Brook Date: Sat, 11 Apr 2009 18:16:32 +0100 MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200904111816.32463.paul@codesourcery.com> Subject: [Qemu-devel] Ram allocation changes Reply-To: qemu-devel@nongnu.org List-Id: qemu-devel.nongnu.org List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: qemu-devel@nongnu.org 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