[SeaBIOS] [PATCH 2/2] accept MADT over fw_cfg
Michael S. Tsirkin
mst at redhat.com
Sun Mar 24 20:14:47 CET 2013
On Sun, Mar 24, 2013 at 01:17:38PM -0400, Kevin O'Connor wrote:
> On Sun, Mar 24, 2013 at 03:07:40PM +0200, Michael S. Tsirkin wrote:
> > On Thu, Mar 21, 2013 at 08:04:38PM -0400, Kevin O'Connor wrote:
> > > So, I see two ways to do this:
> > >
> > > 1 - update SeaBIOS with a patch series that makes it capable of
> > > handling all tables via existing and new fw_cfg entries (including
> > > flags to disable all internal tables), update QEMU to use that SeaBIOS
> > > rev, and then apply a patch series to QEMU that has it create all the
> > > tables (with the final patch flagging to seabios that it should no
> > > longer create any internal tables).
> > >
> > > or, 2 - apply a patch series to QEMU that has it create all the tables
> > > via new fw_cfg entries, then apply a patch series to seabios that
> > > updates it to use the new fw_cfg entries instead of its existing
> > > internal tables, and then apply that new rev of seabios to qemu.
> > >
> > > Were you proposing one of the above paths, or did you have something
> > > else in mind?
> > Exactly, I'm proposing 1, on top of this, a set of compile-time flags to
> > optionally stip unused tables from the bios binary.
> What do you think about using approach 2 as I outline at:
> http://www.seabios.org/pipermail/seabios/2013-March/006020.html ?
> The existing fw_cfg acpi table passing mechanism is pretty hokey, and
> new fw_cfg entries will be needed for smbios, pir, and mptable anyway.
> Converting to all new fw_cfg tables may make the transition simpler
> and provide both forward and backwards compatibility.
I don't exactly understand what do you mean by "file".
More information about the SeaBIOS