Tom Pothier wrote:
On 03/03/09 15:34, Cynthia McGuire wrote:
Using the PRI intermediate layer allows us to enumerate a topology that
contains multiple base boards, chassis', or both. With the use of
contained object handles within the SMBIOS we can derive the parent <->
child relationship correctly within the PRI structure. We'll also be
matching ereport generation with the topology even before a topology
proper can be generated (ie: during boot).
You haven't answered my question. What are the current obstacles in
libsmbios and libtopo that prevent you from enumerating the base board
and chassis topology today? And to be clear, you are talking about
OpenSolaris, right?
Cindi
Currently we plan to use the PRI to only enumerate to the base board
level; then call chip.so to enumerate chip/core/strand and memory topology.
-t
Cindi
------------------------------------------------------------------------
_______________________________________________
fm-discuss mailing list
fm-discuss@opensolaris.org
While I'm happy to see some convergence between x86 and SPARC, this
project moves in the wrong direction. If I understand correctly,
you are adopting the SPARC PRI for modeling the FMA topology on
x86. This has been discussed before and it was decided that a
better approach for all Sun platforms is to move toward adopting
SMBIOS. SMBIOS (plus whatever you glean from ACPI) then becomes the
source of FRU and other FMA topology information for things like
libtopo and fmd(1M). Further, Sun needs to draft a SMBIOS standard
for platform vendors wishing to participate in fault management and
diagnosis for their platforms. Included in the standard should be
the required records for the Sun FMA. If a vendor conforms
(including Sun SPARC), diagnosis and FRU location and replacement is
then guaranteed.
Cindi
--
Cynthia McGuire
Sun Microsystems, Inc - Fishworks http://blogs.sun.com/cindi
_______________________________________________
fm-discuss mailing list
fm-discuss@opensolaris.org
