From: Gleb Natapov <gleb@redhat.com>
To: Kevin O'Connor <kevin@koconnor.net>
Cc: qemu-devel@nongnu.org
Subject: [Qemu-devel] Re: [PATCH][SEABIOS] Move qemu config port access functions into separate file.
Date: Tue, 15 Sep 2009 08:43:39 +0300 [thread overview]
Message-ID: <20090915054339.GD30746@redhat.com> (raw)
In-Reply-To: <20090915000824.GA16210@morn.localdomain>
On Mon, Sep 14, 2009 at 08:08:24PM -0400, Kevin O'Connor wrote:
> On Mon, Sep 14, 2009 at 03:51:41PM +0300, Gleb Natapov wrote:
> > Move qemu config code from smbios.c to its own files. Add support for
> > -boot menu=on|off qemu option.
>
> Hi Gleb,
>
> A couple of comments:
>
> > // Allow user to modify BCV/IPL order.
> > - interactive_bootmenu();
> > + if (qemu_cfg_show_boot_menu())
> > + interactive_bootmenu();
>
> Can you move this test into interactive_bootmenu()? (For non-qemu
> users the flow control looks odd otherwise.)
>
OK. The flow control will not go away though just move to other place so
non-qemu user will see odd flow control anyway :)
> > --- /dev/null
> > +++ b/src/pv.c
>
> What is "pv"? How about "qemu-cfg.c"?
>
pv == ParaVirtualization. I want to put non qemu specific thing there
to. For instance I put kvm_para_available() function there that checks
cpuid signature. I want to use it to replace if(CONFIG_KVM) in
ram_probe().
> > +void qemu_cfg_port_probe(void)
> > +{
> > + char *sig = "QEMU";
> > + int i;
> > +
> > + qemu_cfg_present = 1;
> > +
> > + qemu_cfg_select(QEMU_CFG_SIGNATURE);
> > +
> > + for (i = 0; i < 4; i++)
> > + if (inb(QEMU_CFG_DATA_PORT) != sig[i]) {
> > + qemu_cfg_present = 0;
> > + break;
> > + }
> > + dprintf(4, "qemu_cfg_present=%d\n", qemu_cfg_present);
> > +}
>
> This needs to have a "if (! CONFIG_COREBOOT) return;" - as the current
> check for qemu is not safe on real hardware.
>
Will add.
> Otherwise it looks good to me.
>
> As an aside, it would be good to have a conversation on general BIOS
> configuration options. These types of settings are going to be useful
> on real hardware also - it would be nice to come up with a scheme that
> would work on qemu and coreboot. Maybe something like
> get_config_u32("ShowBootMenu") - where on qemu it would get the info
> from the qemu port but on coreboot it would pull the setting from the
> coreboot flash filesystem.
>
Lets have conversation now. Sounds useful to me. Do you want to use
strings as option names though? They add to BIOS image size and it is
limited, no?
--
Gleb.
next prev parent reply other threads:[~2009-09-15 5:43 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-09-14 12:51 [Qemu-devel] [PATCH][SEABIOS] Move qemu config port access functions into separate file Gleb Natapov
2009-09-15 0:08 ` [Qemu-devel] " Kevin O'Connor
2009-09-15 5:43 ` Gleb Natapov [this message]
2009-09-16 2:02 ` Kevin O'Connor
2009-09-17 9:57 ` Gleb Natapov
2009-09-18 1:24 ` Kevin O'Connor
2009-09-18 10:01 ` Gleb Natapov
2009-09-19 15:16 ` Kevin O'Connor
2009-09-19 17:56 ` Gleb Natapov
2009-09-30 1:09 ` Kevin O'Connor
2009-09-30 6:35 ` Gleb Natapov
2009-09-30 17:17 ` Blue Swirl
2009-09-30 17:31 ` Gleb Natapov
2009-10-02 1:08 ` Kevin O'Connor
2009-10-01 16:35 ` Gleb Natapov
2009-10-02 0:51 ` Kevin O'Connor
2009-10-02 14:03 ` Gleb Natapov
2009-10-02 16:52 ` Kevin O'Connor
2009-10-02 18:10 ` Gleb Natapov
2009-10-02 19:31 ` 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=20090915054339.GD30746@redhat.com \
--to=gleb@redhat.com \
--cc=kevin@koconnor.net \
--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 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).