OpenSolaris

Printable Version Enter a New Search
Bug ID 6800878
Synopsis CMI_MAX_{CHIPS,CORES_PER_CHIP,STRANDS_PER_CORE} should be dynamic
State 10-Fix Delivered (Fix available in build)
Category:Subcategory fma:cpu
Keywords spsw-s10u8-goal
Responsible Engineer Vuong Nguyen
Reported Against
Duplicate Of
Introduced In solaris_nevada
Commit to Fix snv_112
Fixed In snv_112
Release Fixed solaris_nevada(snv_112) , solaris_10u8(s10u8_01) (Bug ID:2175620)
Related Bugs 6801362 , 6809513 , 6819941
Submit Date 3-February-2009
Last Update Date 9-June-2009
Description
The current static definitions for the following are too limiting:

#define CMI_MAX_CHIPS_NBITS             4       /* 16 chips packages max */
#define CMI_MAX_CORES_PER_CHIP_NBITS    3       /* 8 cores per chip max */
#define CMI_MAX_STRANDS_PER_CORE_NBITS  1       /* 2 strands per core max */

#define CMI_MAX_CHIPS                   (1 << CMI_MAX_CHIPS_NBITS)
#define CMI_MAX_CORES_PER_CHIP          (1 << CMI_MAX_CORES_PER_CHIP_NBITS)
#define CMI_MAX_STRANDS_PER_CORE        (1 << CMI_MAX_STRANDS_PER_CORE_NBITS)

These are static because they're needed early in boot, before mp_startup.
The information is available from the MADT which is what we're already
effectively iterating over in mp_startup, so we should be able to
make this dynamic.
Work Around
N/A
Comments
N/A