All of lore.kernel.org
 help / color / mirror / Atom feed
From: Gleb Natapov <gleb@redhat.com>
To: "H. Peter Anvin" <hpa@zytor.com>
Cc: Kevin Wolf <kwolf@redhat.com>,
	seabios@seabios.org, qemu-devel@nongnu.org
Subject: Re: [SeaBIOS] [Qemu-devel] [RFC] Passing boot order from qemu to seabios
Date: Tue, 12 Oct 2010 21:06:57 +0200	[thread overview]
Message-ID: <20101012190657.GG5218@redhat.com> (raw)
In-Reply-To: <4CB49ED6.5000202@zytor.com>

On Tue, Oct 12, 2010 at 10:45:58AM -0700, H. Peter Anvin wrote:
> On 10/12/2010 10:41 AM, Gleb Natapov wrote:
> > On Tue, Oct 12, 2010 at 10:35:51AM -0700, H. Peter Anvin wrote:
> >> On real hardware it is shared between BIOS and the OS, actually.
> >>
> > Guest OS can write in qemu CMOS too. But what is it useful for? Most of
> > its content is not standard AFAIK.
> > 
> 
> This is true to some extent -- there is some standard content, and some
> further can be described via ACPI tables.  However, my point was mostly
> that it is an existing model for nonvolatile storage which also works on
> hardware (and is vastly simpler albeit smaller in size than ESCD).
> 
And my point is why would we want nonvolatile storage for BIOS settings
in qemu. It doesn't provide anything that can't be done through command
line and configured nicely by virt-manager and it introduces one more
file to carry around with your VM. And if the idea is to create it on
the fly then it is no longer nonvolatile and is not better then fw_cfg.
If we want nonvolatile storage for some reason I would agree that CMOS
is good candidate for that except of its size. How much can you fit into
128 byte? Less then one tweet.
--
			Gleb.

  reply	other threads:[~2010-10-12 19:07 UTC|newest]

Thread overview: 44+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-10-11 10:18 [Qemu-devel] [RFC] Passing boot order from qemu to seabios Gleb Natapov
2010-10-11 10:32 ` Kevin Wolf
2010-10-11 10:43   ` Gleb Natapov
2010-10-11 11:01     ` Kevin Wolf
2010-10-11 12:07   ` Gerd Hoffmann
2010-10-11 12:16     ` Gleb Natapov
2010-10-11 19:48       ` [SeaBIOS] " Anthony Liguori
2010-10-11 19:59         ` Gleb Natapov
2010-10-11 20:30           ` Anthony Liguori
2010-10-11 20:36             ` Gleb Natapov
2010-10-11 20:50               ` Anthony Liguori
2010-10-11 21:14                 ` Gleb Natapov
2010-10-11 21:15             ` H. Peter Anvin
2010-10-11 21:41               ` Sebastian Herbszt
2010-10-11 21:51                 ` H. Peter Anvin
2010-10-12  8:01               ` Gleb Natapov
2010-10-12 16:33                 ` H. Peter Anvin
2010-10-12 16:56                   ` Gleb Natapov
2010-10-12 17:35                     ` H. Peter Anvin
2010-10-12 17:41                       ` Gleb Natapov
2010-10-12 17:45                         ` H. Peter Anvin
2010-10-12 19:06                           ` Gleb Natapov [this message]
2010-10-13 19:17                             ` H. Peter Anvin
2010-10-13 20:00                               ` H. Peter Anvin
2010-10-13 20:22                                 ` H. Peter Anvin
2010-10-11 19:51     ` Anthony Liguori
2010-10-11 20:02       ` Gleb Natapov
2010-10-11 20:18       ` [SeaBIOS] " H. Peter Anvin
2010-10-11 11:16 ` Bernhard Kohl
2010-10-11 12:08   ` Gleb Natapov
2010-10-11 23:33     ` [SeaBIOS] " Kevin O'Connor
2010-10-11 12:48   ` Stefan Hajnoczi
2010-10-11 14:29     ` Gleb Natapov
2010-10-11 15:52       ` Stefan Hajnoczi
2010-10-11 16:04         ` Gleb Natapov
2010-10-11 17:01         ` Anthony Liguori
2010-10-11 17:04           ` Gleb Natapov
2010-10-11 23:16             ` [SeaBIOS] " Kevin O'Connor
2010-10-12  8:44             ` Stefan Hajnoczi
2010-10-11 15:09 ` [Qemu-devel] Re: [SeaBIOS] " Avi Kivity
2010-10-11 15:39   ` Gleb Natapov
2010-10-11 15:42     ` Avi Kivity
2010-10-11 15:52       ` Gleb Natapov
2010-10-12  0:08 ` Kevin O'Connor

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=20101012190657.GG5218@redhat.com \
    --to=gleb@redhat.com \
    --cc=hpa@zytor.com \
    --cc=kwolf@redhat.com \
    --cc=qemu-devel@nongnu.org \
    --cc=seabios@seabios.org \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.