All of lore.kernel.org
 help / color / mirror / Atom feed
From: Avi Kivity <avi-atKUWr5tajBWk0Htik3J/w@public.gmane.org>
To: Jeremy Katz <katzj-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>
Cc: kvm-devel <kvm-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org>
Subject: Re: [PATCH] Add support for a basic boot menu to the bios
Date: Thu, 20 Sep 2007 08:02:21 +0200	[thread overview]
Message-ID: <46F20CED.3000107@qumranet.com> (raw)
In-Reply-To: <1190232486.10222.37.camel-bi+AKbBUZKY6gyzm1THtWbp2dZbC/Bob@public.gmane.org>

Jeremy Katz wrote:
> On Sun, 2007-09-16 at 22:00 +0200, Avi Kivity wrote:
>   
>>> The attached patch adds support for a relatively basic boot device
>>> selection menu to the bochs bios code.  
>>>       
> [snip]
>   
>> This is nice!  Two comments:
>>
>> - it would be nice for qemu to provide the bios an indication if the 
>> '-boot' parameter was specified to qemu.  if so, the bios should skip 
>> the menu on first bootup, reducing the boot delay.  On subsequent boots 
>> the menu should be offered.  This is primarily useful in managed 
>> environments.
>>     
>
> While this could be nice, at the same time, -boot is going to be getting
> passed for a long time, even when it's no longer needed, just due to
> people not updating their tools.  So I almost think it's better to take
> the 3 second hit since it's going to be there every other time.  We
> could tweak it to be a little bit less, but 3 seems in line with what
> other BIOSes seem to do.
>
>   

I almost agree.  Let people upgrade their tools, they ought to have many
reasons besides the boot menu.


[we could add a -dont-show-boot-menu parameter to make this explicit,
but I don't think we should]

>> - coding this stuff in rombios32.c instead of rombios.c (with its 
>> strange idea of C) is *much* preferable for maintainability.  As far as 
>> i can tell, there is no reason not to do so, especially for code which 
>> is not called from the 16-bit OS.
>>     
>
> The code is called from the 16-bit OS, though.  

No, it's called from the boot code.  We're not returning to DOS after
int 19.

> It needs to be done
> after rom scanning has been done so that we can show network or not as
> appropriate.  And unless I'm missing something, calling into rombios32.c
> outside of rombios32_init() is going to add just as much
> hard-to-maintain code.
>   

Why?  the thunk into 32-bit mode can be shared and is a small piece of
code.  The boot menu is much larger and can potentially grow (to control
other options besides the boot device).

-- 
Do not meddle in the internals of kernels, for they are subtle and quick to panic.


-------------------------------------------------------------------------
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2005.
http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/

      parent reply	other threads:[~2007-09-20  6:02 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-09-12 19:55 [PATCH] Add support for a basic boot menu to the bios Jeremy Katz
     [not found] ` <1189626953.16586.6.camel-bi+AKbBUZKY6gyzm1THtWbp2dZbC/Bob@public.gmane.org>
2007-09-12 20:19   ` Anthony Liguori
     [not found]     ` <46E849DE.3040103-rdkfGonbjUSkNkDKm+mE6A@public.gmane.org>
2007-09-12 20:25       ` Jeremy Katz
2007-09-14 20:14   ` Anthony Liguori
2007-09-16 20:00   ` Avi Kivity
     [not found]     ` <46ED8B5B.40903-atKUWr5tajBWk0Htik3J/w@public.gmane.org>
2007-09-17 15:23       ` Luca
     [not found]         ` <68676e00709170823m3247c3eaj7d268166ecc8c013-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2007-09-17 17:30           ` Avi Kivity
2007-09-19 20:08       ` Jeremy Katz
     [not found]         ` <1190232486.10222.37.camel-bi+AKbBUZKY6gyzm1THtWbp2dZbC/Bob@public.gmane.org>
2007-09-20  6:02           ` Avi Kivity [this message]

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=46F20CED.3000107@qumranet.com \
    --to=avi-atkuwr5tajbwk0htik3j/w@public.gmane.org \
    --cc=katzj-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org \
    --cc=kvm-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.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.