From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from eggs.gnu.org ([140.186.70.92]:37709) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1QkmzF-0005XL-Lj for qemu-devel@nongnu.org; Sat, 23 Jul 2011 20:56:06 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1QkmzE-0006G2-Cd for qemu-devel@nongnu.org; Sat, 23 Jul 2011 20:56:05 -0400 Received: from mail-yw0-f45.google.com ([209.85.213.45]:46987) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1QkmzE-0006Fy-6U for qemu-devel@nongnu.org; Sat, 23 Jul 2011 20:56:04 -0400 Received: by ywb3 with SMTP id 3so2119692ywb.4 for ; Sat, 23 Jul 2011 17:56:03 -0700 (PDT) Message-ID: <4E2B6DA1.2050805@codemonkey.ws> Date: Sat, 23 Jul 2011 19:56:01 -0500 From: Anthony Liguori MIME-Version: 1.0 References: <1310153845-4373-1-git-send-email-jordan.l.justen@intel.com> <4E2AEE1E.8030904@codemonkey.ws> <4E2B3C33.3050400@codemonkey.ws> <4E2B4A9A.5080005@codemonkey.ws> In-Reply-To: Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Subject: Re: [Qemu-devel] [PATCH v4] hw/pc: Support system flash memory with -pflash parameter List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: Jordan Justen Cc: Kevin Wolf , Jordan Justen , qemu-devel@nongnu.org On 07/23/2011 07:18 PM, Jordan Justen wrote: >> In terms of other flash devices, I don't think it's that simple. Flash is >> tied to the mobo layout so I don't think index> 0 really makes sense unless >> you allow a specific mapping address. I doubt that's terribly useful. > > I think VM's have a different situation than real hardware. I'm not > sure an all ROM or all flash decision will work well for qemu. In > most cases it may work better to make a ROM image available just below > 4GB, and add a flash image below this ROM. > > This allows the qemu's firmware to be updated as usual in > ${prefix}/share/bios.bin, but still allows a flash memory to be > available below this. (The flash below the ROM could be used only for > storing UEFI variables.) > > Otherwise when a new qemu is released along with a new firmware image, > the VM instance using writable flash will continue to use the old > firmware image. Yes, that's a feature. We could have a second nvram for other purposes of course. That could be defined as index=1. Regards, Anthony Liguori