RE: [SFI-devel] [RFC/PATCH 2.6.32] Simple Firmware Interface (SFI):initial support

[Len Brown]

On Tue, 23 Jun 2009, Justen, Jordan L wrote:

> > Should a platform require them, any and all of the ACPI
> > defined/reserved tables can be accessed on an SFI system
> > if needed.  Today, the PCI MCFG is the only ACPI table
> > implemented in the known universe of SFI systems.
> 
> When for ACPI tables are used in SFI, they retain the common
> ACPI header format, including the OEM Revision, Creator ID and
> Creator Revision fields  unlike the other SFI structure, correct?

Yes.  ACPI tables are real ACPI tables, per their spec.

> Regarding stripping those fields from the SFI structures,
> how much space does it save in a typical system versus if they
> had retained the common header format that ACPI defines?

While we do save 12-bytes per table, I don't think that is material,
even if firmware folks claim they turn backflips to save every byte...

(Though it is sort of snappy that an SFI table with
 a single 64-bit pointer fits exactly into 32-bytes;
 if density were the primary goal, we'd pack everything in the
 system into a single table with one shared header...)

So the motivation to remove unused fields was not part of
an effort to reduce total memory footprint.
They were removed because it was not possible
to justify their existence.

The benefit of the SFI header being a proper sub-set of
the ACPI header is that it allows the SFI-OS to not have a
special case to parse the XSDT.  It is both a valid SFI table
and a valid ACPI table...

However, as I've had to answer this question multiple
times, I'm thinking that it might have been less total effort
to use a table header that was arbitrarliy different
and have a special case for finding the ACPI XSDT:-)

cheers,
-Len Brown, Intel Open Source Technology Center

--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/