x86 Generic FMA Topology Enumerator
The x86 Generic FMA Topology Enumerator project is one part of the larger Generic FMA "Platform Independence" (PI) strategy. Although the name and focus of this project is enumeration of x86 class systems, the architecture derived from this project will include restructuring of the sun4v platform independent enumerator. 1. DESCRIPTION This project will provide FMA topology enumeration for i86pc class systems. The enumeration will contain correct placement of FRUs as well as correct FRU label data. This will allow the correct identification as well as indictment of FRUs. The bulk of the FRU label data will be from the system SMBIOS. There will also be the need to obtain topology data from a dynamic source such as ACPI. This will be crucial in platforms that support hot plug and/or dynamic reconfiguration. This project will publish an SMBIOS requirements specification which will determine if a system meets the requirements for correct enumeration. 2. DETAILS The "platform independent" (PI) enumerator consists of two parts: an architecture specific "topo provider" and a common back-end enumerator. The topo provider will present a Directed Acyclic Graph (DAG), which conforms to FWARC/2008/467, to a back-end enumerator which will produce the FMA topology. 2.1 x86 topo provider The x86 topo provider will build a DAG which describes the i86pc system. It relies on both static (SMBIOS) as well as dynamic (ACPI) sources for building, and proper property identification with the DAG. The existing chip.so enumerator will be relied upon for correct association of chip/core/strand topology; as well as retire methods. It will be altered to provide the correct FRU data. 2.2 sun4v topo provider The sun4v topo provider will obtain the DAG as it currently does from LDOM. 2.3 Common Back-end Enumerator The back-end enumerator is currently part of the sun4v platform independent enumerator. It will be extracted from sun4vpi and become a separate entity that can be called to work on a DAG from any architectural topo provider. 3. X86 EREPORT GENERATION On x86 systems, the fault detector and resource fmri are hard-coded to motherboard/chip/core/strand. This is in contrast to what the the x86 topology enumerator will create (chassis/baseboard/chip/core/strand) utilizing the SMBIOS and ACPI. This project will produce a common set of data where both x86 ereport detectors as well as the x86 topo provider gathers it's data. 4. TOPOLOGY CHANGES The sun4v PI enumerator is installed on a sun4v class system as: $ROOT/usr/platform/sun4v/lib/fm/topo/plugins/sun4vpi.so The common PI enumerator is named fma-pi.so and will be: installed on sun4v class systems as: $ROOT/usr/platform/sun4v/lib/fm/topo/plugins/fma-pi.so installed on i86pc class systems as: $ROOT/usr/platform/i86pc/lib/fm/topo/plugins/fma-pi.so The i86pc XML topology map will be modified to invoke the fma-pi.so enumerator. The existing i86pc XML topology map will be moved to a "legacy" map. The sun4v XML topology map will be modified to invoke the fma-pi.so enumerator. 5. REFERENCES x86 Generic FMA Topology Enumerator http://agares.central.sun.com/twiki/bin/view/X64FMA/I86pcTopo SMBIOS Requirements Doc http://agares.central.sun.com/twiki/pub/X64FMA/I86pcTopo/SMBIOS-Requirements.pdf sun4v FMA Platform Independence http://agares.central/twiki/bin/view/Sun4vpi/Sun4v-pi-fma SMBIOS Specification v2.5 http://www.dmtf.org/standards/published_documents/DSP0134v2.5Final.pdf ACPI Specification v3.0b http://www.acpi.info/DOWNLOADS/ACPIspec30b.pdf
_______________________________________________ fm-discuss mailing list fm-discuss@opensolaris.org
