Tom Pothier wrote:
On 03/05/09 12:37, Cynthia A. McGuire wrote:
+1 with some additional questions and comments to be addressed as this project develops.

I'll take a stab at these, though some may progress as the project does.
- Is a Sun standard for SMBIOS a product of this project?

We will publish an SMBIOS requirements document for Solaris x86 FMA Topology Enumeration. I don't want to say it's a "Sun standard for SMBIOS" because we do want inclusion of other i86pc vendors. This doc will outline additional value offered by vendors following it.

Other vendors are not bound to following the SMBIOS standard. There are currently plenty who don't today. Within Sun, however, this is an opportunity to direct future platform conformance for FMA. Mike has already indicated that he is willing and waiting for something to be brought forward. If this project has worked out the requirements, why not proceed with the DMTF and in parallel the platform teams inside of Sun?

This is also a chance to offer platform vendors who are serious about FMA on their systems running OpenSolaris something concrete in terms of FMA conformance.

- The scope of this project needs to narrowed to just the topology that the enumerator will address. You surely are not suggesting to enumerate every FRU for every x86 platform from a single enumerator.

No, not at all. Basically in one form or another, we'll enumerate: chassis // base board // chip/core/strand // memory-controller/memory-device // I/O.

For chip/core/strand and memory-controller/memory-device we'll be modifying the i86pc chip.so enumerator and calling it. For I/O we'll be calling the hostbridge/pcibus enumerator(s). We still need to work this out.

My point is that this project does not address an entire x86 topology and the need for static .xml files elsewhere (e.g. the storage subsystem). Further, the PCI enumerator (and others) already exist and this project is merely a consumer of its topology.

- With the above in mind, what portion of the x86 topology do you propose to enumerate? Going forward, I'd like to see some sample fmtopo output (hierarchy, names, etc...).

We'll enumerate in the hc scheme. Here's an example of a cpu strand:
hc://:product-id=SUN-FIRE-XXX:chassis-id=0838SUN032:server-id=sunw-03/chassis=0/motherboard=0/chip=0/core=0/strand=0

You can address the entire namespace and hc scheme changes once you are further along.

- Where will your code repository be located?
The plan is to putback to Solaris Nevada. It's an fmd plugin module so will live in $SRC/lib/fm/topo/modules/i86pc/x86pi/

Since you're making this an OpenSolaris project, I'd like to see a code review in this forum before your Nevada putback.

Cindi

--
Cynthia McGuire
Sun Microsystems, Inc - Fishworks       http://blogs.sun.com/cindi
_______________________________________________
fm-discuss mailing list
fm-discuss@opensolaris.org

Reply via email to