From: "Gabriel L. Somlo" <gsomlo@gmail.com>
To: Kevin O'Connor <kevin@koconnor.net>
Cc: seabios@seabios.org, Laszlo Ersek <lersek@redhat.com>,
Gerd Hoffmann <kraxel@redhat.com>,
qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] E820 (Re: [v4 PATCH 00/12] SMBIOS: build full tables in QEMU)
Date: Fri, 4 Apr 2014 21:15:14 -0400 [thread overview]
Message-ID: <20140405011513.GB31429@foober.ini.cmu.edu> (raw)
In-Reply-To: <20140405003410.GA13086@morn.localdomain>
On Fri, Apr 04, 2014 at 08:34:11PM -0400, Kevin O'Connor wrote:
> >
> > IMO 'dmidecode -t0' should show what firmware you are running
> > (seabios/ovmf/coreboot/whatever), not something made up by qemu.
>
> Ultimately my preference would be to make a clean break from the
> existing smbios fw_cfg system as it is too complex, too confusing, and
> too inflexible. We could implement the above as you suggest, but I
> fear it would require keeping much of the complexity of the current
> fw_cfg interface. (It's also a new feature as SeaBIOS doesn't
> currently put any useful info in type 0.)
I like this idea too: older/current versions of qemu just do what they
do, and work with SeaBIOS the way they always have. Future versions
just send a completely new fw_cfg message type, which, when
encountered by SeaBIOS, causes it to only add in (or edit) type 0, and
leave everything else as is.
> I don't see anything in the spec that would prohibit it, but I don't
> think it's done in practice. Given how many different OS parsers
> there are and their dubious quality, I think we'd want to be as simple
> as possible and continue to put table 0 at the start.
>...
> The already existing romfile_loader interface seems to provide a
> nearly complete solution to replace the smbios fw_cfg system. If
> there is really demand for more firmware info in the type 0 table, why
> don't we use romfile_loader, have qemu put together a dummy type 0
> table, and then have seabios update it in place? Sure, that's ugly,
> but I'm pretty sure it would be less ugly then keeping the existing
> smbios fw_cfg system around.
The only fly in this ointment may be that type 0 doesn't have a fixed
length that could be edited in place, if you consider the various
strings that get tacked on to the end of it. So you'd still have to
slide the rest of the smbios payload left or right to shrink or
enlarge the type 0 blob, depending on how you modify the various
strings it contains...
--Gabriel
next prev parent reply other threads:[~2014-04-05 1:15 UTC|newest]
Thread overview: 50+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-03-18 23:23 [Qemu-devel] [v4 PATCH 00/12] SMBIOS: build full tables in QEMU Gabriel L. Somlo
2014-03-18 23:23 ` [Qemu-devel] [v4 PATCH 01/12] SMBIOS: Rename smbios_set_type1_defaults() for more general use Gabriel L. Somlo
2014-03-18 23:23 ` [Qemu-devel] [v4 PATCH 02/12] SMBIOS: Use macro to set smbios defaults Gabriel L. Somlo
2014-03-18 23:23 ` [Qemu-devel] [v4 PATCH 03/12] SMBIOS: Use bitmaps to check for smbios table collisions Gabriel L. Somlo
2014-03-18 23:23 ` [Qemu-devel] [v4 PATCH 04/12] SMBIOS: Add code to build full smbios tables; build type 2 table Gabriel L. Somlo
2014-03-18 23:23 ` [Qemu-devel] [v4 PATCH 05/12] SMBIOS: Build full tables for types 0 and 1 Gabriel L. Somlo
2014-03-18 23:23 ` [Qemu-devel] [v4 PATCH 06/12] SMBIOS: Remove unused code for passing individual fields to bios Gabriel L. Somlo
2014-03-18 23:23 ` [Qemu-devel] [v4 PATCH 07/12] SMBIOS: Build full type 3 table Gabriel L. Somlo
2014-03-18 23:23 ` [Qemu-devel] [v4 PATCH 08/12] SMBIOS: Build full type 4 tables Gabriel L. Somlo
2014-03-18 23:23 ` [Qemu-devel] [v4 PATCH 09/12] SMBIOS: Build full smbios memory tables (type 16, 17, 19, and 20) Gabriel L. Somlo
2014-03-18 23:23 ` [Qemu-devel] [v4 PATCH 10/12] SMBIOS: Build full tables for type 32 and 127 Gabriel L. Somlo
2014-03-18 23:23 ` [Qemu-devel] [v4 PATCH 11/12] SMBIOS: Update all table definitions to smbios spec v2.3 Gabriel L. Somlo
2014-03-18 23:23 ` [Qemu-devel] [v4 PATCH 12/12] SMBIOS: Remove SeaBIOS compatibility quirks Gabriel L. Somlo
2014-03-26 19:58 ` [Qemu-devel] E820 (Re: [v4 PATCH 00/12] SMBIOS: build full tables in QEMU) Gabriel L. Somlo
2014-03-26 22:36 ` Kevin O'Connor
2014-03-31 20:18 ` Gabriel L. Somlo
2014-04-01 8:40 ` Laszlo Ersek
2014-04-01 14:39 ` Kevin O'Connor
2014-04-01 15:47 ` Laszlo Ersek
2014-04-01 18:47 ` Gabriel L. Somlo
2014-04-01 20:28 ` Kevin O'Connor
2014-04-01 21:28 ` Gabriel L. Somlo
2014-04-01 21:44 ` Laszlo Ersek
2014-04-01 22:00 ` Kevin O'Connor
2014-04-01 22:35 ` Laszlo Ersek
2014-04-02 12:38 ` Gabriel L. Somlo
2014-04-02 13:39 ` Laszlo Ersek
2014-04-05 2:48 ` Kevin O'Connor
2014-04-02 15:07 ` Gerd Hoffmann
2014-04-02 17:01 ` Gabriel L. Somlo
2014-04-03 1:57 ` Gabriel L. Somlo
2014-04-03 9:42 ` Laszlo Ersek
2014-04-03 13:32 ` Gabriel L. Somlo
2014-04-03 13:56 ` Laszlo Ersek
2014-04-07 6:50 ` Gerd Hoffmann
2014-04-07 6:47 ` Gerd Hoffmann
2014-04-01 21:48 ` Kevin O'Connor
2014-04-02 15:04 ` Gerd Hoffmann
2014-04-05 0:34 ` Kevin O'Connor
2014-04-05 1:15 ` Gabriel L. Somlo [this message]
2014-04-05 2:26 ` Kevin O'Connor
2014-04-07 7:09 ` Gerd Hoffmann
2014-04-07 14:14 ` Kevin O'Connor
2014-04-07 14:33 ` Laszlo Ersek
2014-04-07 14:49 ` Gabriel L. Somlo
2014-04-07 15:23 ` Kevin O'Connor
2014-04-07 18:05 ` Gabriel L. Somlo
2014-04-07 18:57 ` Kevin O'Connor
2014-04-08 13:51 ` Gabriel L. Somlo
2014-03-27 2:45 ` Gabriel L. Somlo
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=20140405011513.GB31429@foober.ini.cmu.edu \
--to=gsomlo@gmail.com \
--cc=kevin@koconnor.net \
--cc=kraxel@redhat.com \
--cc=lersek@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 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).