From: Gleb Natapov <gleb@redhat.com>
To: Stefan Hajnoczi <stefanha@gmail.com>
Cc: Kevin O'Connor <kevin@koconnor.net>,
Jordan Justen <jljusten@gmail.com>,
qemu-devel <qemu-devel@nongnu.org>,
Michal Suchanek <hramrach@centrum.cz>,
Avi Kivity <avi@redhat.com>
Subject: Re: [Qemu-devel] OVMF Google Summer of Code ideas
Date: Tue, 8 Mar 2011 10:26:57 +0200 [thread overview]
Message-ID: <20110308082657.GB2504@redhat.com> (raw)
In-Reply-To: <AANLkTinMGXaAi95PC9V+2x9N6j6JMmxH17OKTEoc88zi@mail.gmail.com>
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. But, I don't have the suggestion (or
> > implementation) ready at this time.
>
> Sounds like something to keep discussing with the QEMU and SeaBIOS
> communities. Gleb Natapov and Kevin O'Connor have done a lot of the
> recent BIOS and firmware interface work. I 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? CMOS
memory is less them 512 byte IIRC and this may not be enough. What OVMF
uses on real HW for non-volatile storage?
--
Gleb.
next prev parent reply other threads:[~2011-03-08 8:27 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-03-06 4:12 [Qemu-devel] OVMF Google Summer of Code ideas Jordan Justen
2011-03-06 15:29 ` Michal Suchanek
2011-03-06 21:15 ` Jordan Justen
2011-03-07 9:48 ` Stefan Hajnoczi
2011-03-08 0:54 ` Jordan Justen
2011-03-08 7:18 ` Stefan Hajnoczi
2011-03-08 8:26 ` Gleb Natapov [this message]
2011-03-08 17:13 ` Jordan Justen
2011-03-09 10:16 ` Gleb Natapov
2011-03-09 18:34 ` Jordan Justen
2011-03-08 17:00 ` Jordan Justen
2011-03-09 2:23 ` Kevin O'Connor
2011-03-09 5:34 ` Jordan Justen
2011-03-09 13:43 ` Natalia Portillo
2011-03-09 18:44 ` Jordan Justen
2011-03-09 23:20 ` Natalia Portillo
2011-03-07 10:22 ` Peter Maydell
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20110308082657.GB2504@redhat.com \
--to=gleb@redhat.com \
--cc=avi@redhat.com \
--cc=hramrach@centrum.cz \
--cc=jljusten@gmail.com \
--cc=kevin@koconnor.net \
--cc=qemu-devel@nongnu.org \
--cc=stefanha@gmail.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).