From: Paul Brook <paul@codesourcery.com>
To: qemu-devel@nongnu.org
Cc: Jan Kiszka <jan.kiszka@siemens.com>
Subject: Re: [Qemu-devel] [PATCH] x86: Manage BIOS boot menu via command line
Date: Thu, 18 Dec 2008 16:20:01 +0000 [thread overview]
Message-ID: <200812181620.01572.paul@codesourcery.com> (raw)
In-Reply-To: <494A4A55.2090700@siemens.com>
On Thursday 18 December 2008, Jan Kiszka wrote:
> When booting a guest from the command line, you normally do not need the
> interactive boot menu with its 3 s waiting that someone might press F12.
> So this patch introduces a mechanism to enable the boot menu only on
> demand, ie. when the user provided the command line switch -bootmenu.
> This reduces boot times to their original dimension.
>
> The host-guest interface used here is CMOS RAM byte 0x60. If it is
> non-zero, the guest BIOS will skip the F12 delay, keeping the previous
> behavior in case the host does not support it. -bootmenu was chosen in
> favor of -boot as the syntax of the latter is not easily and cleanly
> extensible.
I'm not sure I believe this. We already support multiple options to -boot so
why not just add another one (e.g. "q") that means include the boot menu?
i.e. -boot qcad would give the current behaviour.
I've no particular preference whether this is communicated to the bios via the
current 0x3d region or via a new byte. It looks like there's a spare bit in
byte 0x38 that could be used.
Paul
next prev parent reply other threads:[~2008-12-18 16:20 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-12-18 13:04 [Qemu-devel] [PATCH] x86: Manage BIOS boot menu via command line Jan Kiszka
2008-12-18 13:30 ` Gleb Natapov
2008-12-18 16:06 ` [Qemu-devel] " Jan Kiszka
2008-12-18 16:20 ` Paul Brook [this message]
2008-12-18 16:28 ` [Qemu-devel] " Anthony Liguori
2008-12-18 16:57 ` Jan Kiszka
2008-12-18 17:23 ` Anthony Liguori
2008-12-18 17:41 ` Gleb Natapov
2008-12-18 18:43 ` Laurent Vivier
2008-12-18 21:28 ` [Qemu-devel] " Jan Kiszka
2008-12-18 16:27 ` [Qemu-devel] " Anthony Liguori
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=200812181620.01572.paul@codesourcery.com \
--to=paul@codesourcery.com \
--cc=jan.kiszka@siemens.com \
--cc=qemu-devel@nongnu.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.