From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1MoDkA-0005xf-Ed for qemu-devel@nongnu.org; Thu, 17 Sep 2009 05:57:38 -0400 Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1MoDk4-0005t0-W5 for qemu-devel@nongnu.org; Thu, 17 Sep 2009 05:57:37 -0400 Received: from [199.232.76.173] (port=51537 helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1MoDk4-0005sq-Mm for qemu-devel@nongnu.org; Thu, 17 Sep 2009 05:57:32 -0400 Received: from mx1.redhat.com ([209.132.183.28]:1524) by monty-python.gnu.org with esmtp (Exim 4.60) (envelope-from ) id 1MoDk4-0002jK-4c for qemu-devel@nongnu.org; Thu, 17 Sep 2009 05:57:32 -0400 Date: Thu, 17 Sep 2009 12:57:28 +0300 From: Gleb Natapov Message-ID: <20090917095728.GN23157@redhat.com> References: <20090914125141.GB30746@redhat.com> <20090915000824.GA16210@morn.localdomain> <20090915054339.GD30746@redhat.com> <20090916020259.GA18131@morn.localdomain> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20090916020259.GA18131@morn.localdomain> Subject: [Qemu-devel] Re: [PATCH][SEABIOS] Move qemu config port access functions into separate file. List-Id: qemu-devel.nongnu.org List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: Kevin O'Connor Cc: qemu-devel@nongnu.org On Tue, Sep 15, 2009 at 10:02:59PM -0400, Kevin O'Connor wrote: > On Tue, Sep 15, 2009 at 08:43:39AM +0300, Gleb Natapov wrote: > > On Mon, Sep 14, 2009 at 08:08:24PM -0400, Kevin O'Connor wrote: > > > 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? > > My preference is strings - I think the long-term flexibility they > provide is worth the slight additional overhead they require. > > Currently, SeaBIOS is just under 64K -- if features continue to get > added (eg, usb keyboard/boot) then it will likely creep into the > e-segment. I don't foresee any hard limits on space coming up. > Fine by me. The configuration interface should be able to read streams of data though. Qemu uses it to pass additional ACPI tables for instance. So it not just simple key->value interface. get_config_u32("ShowBootMenu") will work for simple cases but how can we express stream semantic? May be: table_count = get_config_u16("AdditionalAcpiCount") select_config("AdditionalAcpiTables"); for (i=0; i