From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from eggs.gnu.org ([2001:4830:134:3::10]:41872) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1aTqs5-0005cw-3X for qemu-devel@nongnu.org; Thu, 11 Feb 2016 08:01:22 -0500 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1aTqs4-0000A2-B6 for qemu-devel@nongnu.org; Thu, 11 Feb 2016 08:01:21 -0500 Received: from mail-vk0-x22d.google.com ([2607:f8b0:400c:c05::22d]:34850) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1aTqs4-00009y-6q for qemu-devel@nongnu.org; Thu, 11 Feb 2016 08:01:20 -0500 Received: by mail-vk0-x22d.google.com with SMTP id e6so35568385vkh.2 for ; Thu, 11 Feb 2016 05:01:20 -0800 (PST) MIME-Version: 1.0 In-Reply-To: References: From: Peter Maydell Date: Thu, 11 Feb 2016 13:01:00 +0000 Message-ID: Content-Type: text/plain; charset=UTF-8 Subject: Re: [Qemu-devel] Memory on stellaris board List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: Aurelio Remonda Cc: QEMU Developers On 11 February 2016 at 12:46, Aurelio Remonda wrote: > On Fri, Feb 5, 2016 at 2:00 PM, Peter Maydell wrote: >> The right way to do this is to set the MachineClass default_ram_size >> to what you want your default value to be. Then you should calculate >> the dc0 etc values to expose to the guest based on the ram size >> (which might be the default or might be user specified). > > But stellaris board has a hardcoded dc0 value, when you place the -m flag > with for example 256M you shouldn't calculate any sram_size from dc0, you > just assign that as your ram size. What I am suggesting is that dc0 should not be hardcoded, but that you should work out what dc0 to use based on the user provided RAM size. thanks -- PMM