From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from [140.186.70.92] (port=48459 helo=eggs.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1PxGRa-0006qA-Nv for qemu-devel@nongnu.org; Wed, 09 Mar 2011 05:16:39 -0500 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1PxGRZ-0005as-L4 for qemu-devel@nongnu.org; Wed, 09 Mar 2011 05:16:38 -0500 Received: from mx1.redhat.com ([209.132.183.28]:11723) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1PxGRZ-0005an-3Q for qemu-devel@nongnu.org; Wed, 09 Mar 2011 05:16:37 -0500 Date: Wed, 9 Mar 2011 12:16:27 +0200 From: Gleb Natapov Subject: Re: [Qemu-devel] OVMF Google Summer of Code ideas Message-ID: <20110309101627.GF10151@redhat.com> References: <20110308082657.GB2504@redhat.com> MIME-Version: 1.0 Content-Type: text/plain; charset=koi8-r Content-Disposition: inline Content-Transfer-Encoding: quoted-printable In-Reply-To: List-Id: qemu-devel.nongnu.org List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: Jordan Justen Cc: Stefan Hajnoczi , Kevin O'Connor , qemu-devel , Michal Suchanek , Avi Kivity On Tue, Mar 08, 2011 at 09:13:38AM -0800, Jordan Justen wrote: > 2011/3/8 Gleb Natapov : > > On Tue, Mar 08, 2011 at 07:18:09AM +0000, Stefan Hajnoczi wrote: > >> > Regarding the non-volatile variables issue, I have been trying to > >> > develop a proposal for addressing this with a change to QEMU's > >> > hardware support of bios.bin. =9ABut, I don't have the suggestion (or > >> > implementation) ready at this time. > >> > >> Sounds like something to keep discussing with the QEMU and SeaBIOS > >> communities. =9AGleb Natapov and Kevin O'Connor have done a lot of the > >> recent BIOS and firmware interface work. =9AI think persistent CMOS has > >> come up several times and might be similar to non-volatile UEFI > >> storage. > >> > > What kind of information OVMF stores on a persistent storage? >=20 > Non-volatile variables are a general system wide environment variable > storage facility, but one key thing to store (for instance) is the > path to the boot image. >=20 > > CMOS > > memory is less them 512 byte IIRC and this may not be enough. What OVMF > > uses on real HW for non-volatile storage? >=20 > Regarding CMOS, I think qemu exposes 128 bytes of non persistent CMOS > RAM. Many current chipsets provide another bank of 128 bytes, meaning > a total of 256 bytes (minus the RTC registers). >=20 > Regarding UEFI non-volatile variables on real HW: > Most systems today have at least 1MB of flash storage located just > below 4GB. The entire contents can be modified, which is how firmware > updates happen. >=20 How this flash storage is programmed? May be we can emulate something similar. > For a UEFI based system, the non-volatile variables generally occupy > 8KB~64KB of the flash depending on flash space availability. >=20 > -Jordan -- Gleb.