From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1JnTUc-0004fV-AD for qemu-devel@nongnu.org; Sun, 20 Apr 2008 02:57:42 -0400 Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1JnTUa-0004fJ-Tk for qemu-devel@nongnu.org; Sun, 20 Apr 2008 02:57:41 -0400 Received: from [199.232.76.173] (helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1JnTUa-0004fG-Oc for qemu-devel@nongnu.org; Sun, 20 Apr 2008 02:57:40 -0400 Received: from mx20.gnu.org ([199.232.41.8]) by monty-python.gnu.org with esmtps (TLS-1.0:RSA_AES_256_CBC_SHA1:32) (Exim 4.60) (envelope-from ) id 1JnTUa-00032y-9F for qemu-devel@nongnu.org; Sun, 20 Apr 2008 02:57:40 -0400 Received: from fk-out-0910.google.com ([209.85.128.186]) by mx20.gnu.org with esmtp (Exim 4.60) (envelope-from ) id 1JnTUZ-0006HX-B0 for qemu-devel@nongnu.org; Sun, 20 Apr 2008 02:57:39 -0400 Received: by fk-out-0910.google.com with SMTP id 18so1644946fkq.2 for ; Sat, 19 Apr 2008 23:57:36 -0700 (PDT) Message-ID: Date: Sun, 20 Apr 2008 09:57:35 +0300 From: "Blue Swirl" Subject: Re: [Qemu-devel] [PATCH] Set memory size per machine In-Reply-To: MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Content-Disposition: inline References: 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 On 4/20/08, andrzej zaborowski wrote: > This patch lets a machine decide on the amount of space it'll use in > phys_ram_base in addition to that specified with "-m", default is > zero. Currently that amount was the maximum of BIOS size + VGA RAM > size over all machines of all archs, and that was not enough for the > MusicPal and even if extended it may be not enough for a machine > supported in the future. > > This also lets a machine OR the specified value with a RAMSIZE_FIXED > flag to indicate that it ignores the value given with "-m" (true for > almost half of the machines in qemu). In addition to minimum, higher level code could handle the maximum memory size supported, like sun4m.c does currently. Then I'd use ram_min and ram_max or something similar. > +#define RAMSIZE_FIXED (1 << 0) > + size_t ram_require; > + const char *boot_letters; boot_letters?