+1
-- Garrett
Michael Corcoran wrote:
> I'm sponsoring the following fast-track on behalf of Geeta Krishna with
> time-out set to 11/06/2009. The project requests minor binding only.
>
> I've provided output from an OPL machine for comparison in the materials
> directory under cfgadm-opl.txt
>
>
> Template Version: @(#)sac_nextcase %I% %G% SMI
> This information is Sun Proprietary: Need-to-Know
>
> 1. Introduction
> 1.1. Project/Component Working Name:
> Attachment Points for hotpluggable x86 systems
>
> 1.2. Name of Document Author/Supplier:
> Author: Geeta Krishna <geetanjali.krishna at intel.com>
> Gerry Liu <jiang.liu at intel.com>
>
> 1.3 Date of This Document:
> October 22nd, 2009
>
> 4. Technical Description
> Name: Attachment point names for x86 hot pluggable systems
> Submitter: Geeta Krishna
> Owner: Geeta Krishna
> Interest:
> Status: waiting fast-track
>
> Background:
>
> Sparc DR systems have two kinds of boards - System board and IO board.
> The corresponding Attachment Points are named as SBx and IOx (where x
> is a numeric value).
>
> On x86 systems, there could be four different kind of boards - CPU only,
> memory only, IO only and system board consisting of CPU, memory and IOH.
>
>
> Proposal:
>
> To accomodate the new board types, we are proposing the following new
> Attachment
> Points to be defined.
>
> CPUx - for CPU only board
>
> CPUx.MEMy - for memory only board attached with CPUx. For x86
> hotpluggable
> systems, memory controller is integrated with the CPU. This
> nomenclature
> clearly states the dependency of the memory board on the CPU.
>
> Note: x and y indicate numeric values
>
> Sample outputs from cfgadm on x86:
>
> cfgadm -l CPU
> Ap_Id Type Receptacle Occupant
> Condition
> CPU0 CPU_Board connected configured ok
> CPU0.MEM0 MemoryBoard connected configured ok
> CPU0.MEM1 MemoryBoard empty unconfigured ok
> CPU2 CPU_Board connected configured ok
> CPU2.MEM0 MemoryBoard connected configured ok
> CPU2.MEM1 MemoryBoard empty unconfigured ok
> CPU3 CPU_Board connected configured ok
> CPU3.MEM0 MemoryBoard empty unconfigured ok
> CPU3.MEM1 MemoryBoard empty unconfigured ok
> CPU4 CPU_Board connected configured ok
> CPU4.MEM0 MemoryBoard empty unconfigured ok
> CPU4.MEM1 MemoryBoard empty unconfigured ok
>
> cfgadm -l IO
> Ap_Id Type Receptacle Occupant
> Condition
> IO0 IO_Board disconnected unconfigured ok
>
> cfgadm -lav CPU
> Ap_Id Receptacle Occupant Condition
> Information
> When Type Busy Phys_Id
> CPU0 connected configured ok
> powered-on, assigned
> Oct 26 19:33 CPU_Board y /devices/fw/acpidr at 0:CPU0
> CPU0::cpu0 connected configured ok
> cpuid 0, 32, 4, 36, 8, 40, 12, 44, 16, 48, 20, 52, 24, 56, 28, and 60,
> speed 1867 MHz, ecache 24 MBytes
> Oct 26 19:33 cpu y /devices/fw/acpidr at 0:CPU0::cpu0
> CPU0.MEM0 connected configured ok
> powered-on, assigned
> Oct 26 19:33 MemoryBoard n /devices/fw/acpidr at 0:CPU0.MEM0
> CPU0.MEM0::memory0 connected configured ok base
> address 0x1000000, 8254284 KBytes total, unconfigurable
> Oct 26 19:33 memory
> n /devices/fw/acpidr at 0:CPU0.MEM0::memory0
> CPU0.MEM1 empty unconfigured ok
> assigned
> Oct 26 19:33 MemoryBoard n /devices/fw/acpidr at 0:CPU0.MEM1
> CPU1 connected configured ok
> powered-on, assigned
> Oct 26 19:33 CPU_Board n /devices/fw/acpidr at 0:CPU1
> CPU1::cpu0 connected configured ok
> cpuid 2, 34, 6, 38, 10, 42, 14, 46, 18, 50, 22, 54, 26, 58, 30, and 62,
> speed 1867 MHz, ecache 24 MBytes
> Oct 26 19:33 cpu n /devices/fw/acpidr at 0:CPU1::cpu0
> CPU1.MEM0 connected configured ok
> powered-on, assigned
> Oct 26 19:33 MemoryBoard n /devices/fw/acpidr at 0:CPU1.MEM0
> CPU1.MEM0::memory0 connected configured ok base
> address 0x280000000, 8388608 KBytes total, unconfigurable
> Oct 26 19:33 memory
> n /devices/fw/acpidr at 0:CPU1.MEM0::memory0
> CPU1.MEM1 empty unconfigured ok
> assigned
> Oct 26 19:33 MemoryBoard n /devices/fw/acpidr at 0:CPU1.MEM1
> CPU2 connected configured ok
> powered-on, assigned
> Oct 26 19:33 CPU_Board n /devices/fw/acpidr at 0:CPU2
> CPU2::cpu0 connected configured ok
> cpuid 1, 33, 5, 37, 9, 41, 13, 45, 17, 49, 21, 53, 25, 57, 29, and 61,
> speed 1867 MHz, ecache 24 MBytes
> Oct 26 19:33 cpu n /devices/fw/acpidr at 0:CPU2::cpu0
> CPU2.MEM0 empty unconfigured ok
> assigned
> Oct 26 19:33 MemoryBoard n /devices/fw/acpidr at 0:CPU2.MEM0
> CPU2.MEM1 empty unconfigured ok
> assigned
> Oct 26 19:33 MemoryBoard n /devices/fw/acpidr at 0:CPU2.MEM1
> CPU3 connected configured ok
> powered-on, assigned
> Oct 26 19:33 CPU_Board n /devices/fw/acpidr at 0:CPU3
> CPU3::cpu0 connected configured ok
> cpuid 3, 35, 7, 39, 11, 43, 15, 47, 19, 51, 23, 55, 27, 59, 31, and 63,
> speed 1867 MHz, ecache 24 MBytes
> Oct 26 19:33 cpu n /devices/fw/acpidr at 0:CPU3::cpu0
> CPU3.MEM0 empty unconfigured ok
> assigned
> Oct 26 19:33 MemoryBoard n /devices/fw/acpidr at 0:CPU3.MEM0
> CPU3.MEM1 empty unconfigured ok
> assigned
> Oct 26 19:33 MemoryBoard n /devices/fw/acpidr at 0:CPU3.MEM1
>
> cfgadm -lav IO
> Ap_Id Receptacle Occupant Condition
> Information
> When Type Busy Phys_Id
> IO0 disconnected unconfigured ok
> powered-on, assigned
> Oct 26 19:33 IO_Board n /devices/fw/acpidr at 0:IO0
>
>
> Interface levels:
> Interface Classification Comments
> ----------------------------------------------------------------------------
> AP Nomenclature Uncommitted Attachment point
> hierarchy and names
> 6. Resources and Schedule
> 6.4. Steering Committee requested information
> 6.4.1. Consolidation C-team Name:
> ON
> 6.5. ARC review type: FastTrack
> 6.6. ARC Exposure: open
>
>
>
