SGI UV platform topology sysfs ABI | Linux 6.18.37

요약·해설과 원문, 전문 번역을 서로 분리했습니다. API 이름, symbol, source path는 원문 표기를 사용합니다.

1. 요약·해설

원문의 핵심 논리와 kernel programming 관점의 보충 설명입니다. 아래의 전문 번역과는 별도로 작성했습니다.

Platform generation and partition identity

sysfs-firmware-sgi_uv:1-53

Root attributes는 UV architecture·generation, hub presence, physical partition과 coherence domain을 식별합니다.

Hub and fabric connectivity

sysfs-firmware-sgi_uv:54-123

BIOS-visible hubs와 ordinal ports의 remote endpoints를 연결해 interconnect fabric topology를 복원할 수 있습니다.

PCI bus physical placement

sysfs-firmware-sgi_uv:124-159

Address-named PCI bus objects가 IO type, hub location, slot, bridge address와 IIO stack을 제공합니다.

2. 영어 원문 전체

번역 기준이 된 Linux v6.18.37 원문입니다. 줄 번호는 이 버전의 파일 좌표입니다.

원문 전체 펼치기

1 What: /sys/firmware/sgi_uv/

2 Date: September 2020

3 Contact: Justin Ernst <justin.ernst@hpe.com>

4 Description:

5 The /sys/firmware/sgi_uv directory contains information

6 about the UV platform.

8 Under that directory are a number of read-only attributes::

10 archtype

11 hub_type

12 hubless

13 partition_id

14 coherence_id

15 uv_type

17 The archtype entry contains the UV architecture type that

18 is used to select arch-dependent addresses and features.

19 It can be set via the OEM_ID in the ACPI MADT table or by

20 UVsystab entry both passed from UV BIOS.

22 The hub_type entry is used to select the type of hub which is

23 similar to uv_type but encoded in a binary format. Include

24 the file uv_hub.h to get the definitions.

26 The hubless entry basically is present and set only if there

27 is no hub. In this case the hub_type entry is not present.

29 The partition_id entry contains the partition id.

30 UV systems can be partitioned into multiple physical

31 machines, which each partition running a unique copy

32 of the operating system. Each partition will have a unique

33 partition id.

35 The coherence_id entry contains the coherence id.

36 A partitioned UV system can have one or more coherence

37 domains. The coherence id indicates which coherence domain

38 this partition is in.

40 The uv_type entry contains the hub revision number.

41 This value can be used to identify the UV system version::

43 "0.*" = Hubless UV ('*' is subtype)

44 "3.0" = UV2

45 "5.0" = UV3

46 "7.0" = UV4

47 "7.1" = UV4a

48 "9.0" = UV5

50 The /sys/firmware/sgi_uv directory also contains two directories::

52 hubs/

53 pcibuses/

55 The hubs directory contains a number of hub objects, each representing

56 a UV Hub visible to the BIOS. Each hub object's name is appended by a

57 unique ordinal value (ex. /sys/firmware/sgi_uv/hubs/hub_5)

59 Each hub object directory contains a number of read-only attributes::

61 cnode

62 location

63 name

64 nasid

65 shared

66 this_partition

68 The cnode entry contains the cnode number of the corresponding hub.

69 If a cnode value is not applicable, the value returned will be -1.

71 The location entry contains the location string of the corresponding hub.

72 This value is used to physically identify a hub within a system.

74 The name entry contains the name of the corresponding hub. This name can

75 be two variants::

77 "UVHub x.x" = A 'node' ASIC, connecting a CPU to the interconnect

78 fabric. The 'x.x' value represents the ASIC revision.

79 (ex. 'UVHub 5.0')

81 "NLxRouter" = A 'router ASIC, only connecting other ASICs to

82 the interconnect fabric. The 'x' value representing

83 the fabric technology version. (ex. 'NL8Router')

85 The nasid entry contains the nasid number of the corresponding hub.

86 If a nasid value is not applicable, the value returned will be -1.

88 The shared entry contains a boolean value describing whether the

89 corresponding hub is shared between system partitions.

91 The this_partition entry contains a boolean value describing whether

92 the corresponding hub is local to the current partition.

94 Each hub object directory also contains a number of port objects,

95 each representing a fabric port on the corresponding hub.

96 A port object's name is appended by a unique ordinal value

97 (ex. /sys/firmware/sgi_uv/hubs/hub_5/port_3)

99 Each port object directory contains a number of read-only attributes::

100

101 conn_hub

102 conn_port

103

104 The conn_hub entry contains a value representing the unique

105 ordinal value of the hub on the other end of the fabric

106 cable plugged into the port. If the port is disconnected,

107 the value returned will be -1.

108

109 The conn_port entry contains a value representing the unique

110 ordinal value of the port on the other end of the fabric cable

111 plugged into the port. If the port is disconnected, the value

112 returned will be -1.

113

114 Ex:

115 A value of '3' is read from:

116 /sys/firmware/sgi_uv/hubs/hub_5/port_3/conn_hub

117

118 and a value of '6' is read from:

119 /sys/firmware/sgi_uv/hubs/hub_5/port_3/conn_port

120

121 representing that this port is connected to:

122 /sys/firmware/sgi_uv/hubs/hub_3/port_6

123

124 The pcibuses directory contains a number of PCI bus objects.

125 Each PCI bus object's name is appended by its PCI bus address.

126 (ex. pcibus_0003:80)

127

128 Each pcibus object has a number of possible read-only attributes::

129

130 type

131 location

132 slot

133 ppb_addr

134 iio_stack

135

136 The type entry contains a value describing the type of IO at

137 the corresponding PCI bus address. Known possible values

138 across all UV versions are::

139

140 BASE IO

141 PCIe IO

142 PCIe SLOT

143 NODE IO

144 Riser

145 PPB

146

147 The location entry contains the location string of the UV Hub

148 of the CPU physically connected to the corresponding PCI bus.

149

150 The slot entry contains the physical slot number of the

151 corresponding PCI bus. This value is used to physically locate

152 PCI cards within a system.

153

154 The ppb_addr entry contains the PCI address string of the

155 bridged PCI bus. This entry is only present when the PCI bus

156 object type is 'PPB'.

157

158 The iio_stack entry contains a value describing the IIO stack

159 number that the corresponding PCI bus object is connected to.

160

3. 한국어 전문 번역

영어 원문의 문단 순서와 의미를 유지한 전체 번역입니다. 코드, 함수명, symbol과 URL은 원문 표기를 유지합니다.

SGI UV platform topology

1-159

항목	한국어 전문 번역
What	/sys/firmware/sgi_uv/
Date	2020년 9월
Contact	Justin Ernst <justin.ernst@hpe.com>
Description	`/sys/firmware/sgi_uv`는 UV platform 정보를 제공합니다. Root의 read-only `archtype`은 architecture-dependent addresses와 features를 고르는 UV architecture type이며 UV BIOS가 전달한 ACPI MADT `OEM_ID` 또는 `UVsystab` entry로 설정할 수 있습니다. `hub_type`은 `uv_type`과 비슷한 hub type을 binary encoding으로 제공하고 definitions는 `uv_hub.h`에 있습니다. `hubless`는 hub가 없을 때만 존재하고 설정되며 이때 `hub_type`은 없습니다. `partition_id`는 UV system을 여러 physical machines로 나눠 각 partition이 독립 OS copy를 실행할 때의 unique ID입니다. `coherence_id`는 partition이 속한 coherence domain을 나타내며 한 partitioned system에는 하나 이상의 domains가 있을 수 있습니다. `uv_type`은 hub revision으로, `0.*`는 Hubless UV, `3.0`은 UV2, `5.0`은 UV3, `7.0`은 UV4, `7.1`은 UV4a, `9.0`은 UV5입니다. Root에는 `hubs/`와 `pcibuses/` directories도 있습니다. `hubs/`의 `hub_<ordinal>`은 BIOS에 보이는 UV Hub를 나타냅니다. Read-only `cnode`와 `nasid`는 적용할 수 없으면 -1, `location`은 physical identification string, `name`은 CPU를 interconnect fabric에 연결하는 node ASIC인 `UVHub x.x`(예: `UVHub 5.0`) 또는 다른 ASICs만 fabric에 연결하는 router ASIC인 `NLxRouter`(예: `NL8Router`)입니다. `shared`는 partitions 사이 공유 여부, `this_partition`은 현재 partition에 local인지 나타내는 booleans입니다. 각 hub에는 `port_<ordinal>` objects가 있으며 `conn_hub`와 `conn_port`가 fabric cable 반대편 hub와 port ordinal을 가리킵니다. 연결이 끊겼으면 각각 -1입니다. `pcibuses/` objects는 `pcibus_0003:80`처럼 PCI bus address를 이름에 붙입니다. 가능한 read-only attributes는 `type`, `location`, `slot`, `ppb_addr`, `iio_stack`입니다. `type`의 known values는 `BASE IO`, `PCIe IO`, `PCIe SLOT`, `NODE IO`, `Riser`, `PPB`입니다. `location`은 bus에 physically connected된 CPU의 UV Hub location, `slot`은 PCI card를 찾는 physical slot number, `ppb_addr`는 bridged PCI bus address이며 type이 `PPB`일 때만 존재하고, `iio_stack`은 bus가 연결된 IIO stack number입니다.
Access	Read-only attributes

SGI UV platform attributes

AttributeMeaning

archtypeUV architecture type for address and feature selection

hub_typeBinary-encoded hub type; absent when hubless

hublessPresent and set only when there is no hub

partition_idUnique physical partition ID

coherence_idPartition coherence-domain ID

uv_typeHub revision and UV generation

Root-level architecture, hub와 partition metadata입니다.

UV type mapping

uv_typeSystem

0.*Hubless UV; * is subtype

3.0UV2

5.0UV3

7.0UV4

7.1UV4a

9.0UV5

uv_type revision strings와 system generations입니다.

UV hub object attributes

AttributeMeaning

cnodeCnode number, or -1 when not applicable

locationPhysical hub location string

nameUVHub x.x node ASIC or NLxRouter

nasidNASID number, or -1 when not applicable

sharedShared between system partitions

this_partitionLocal to the current partition

BIOS-visible hub_<ordinal> objects의 identity와 locality fields입니다.

UV fabric port connection

Read hub_5/port_3/conn_hub = 3Read hub_5/port_3/conn_port = 6Resolve remote endpointhub_3/port_6

hub_5의 port_3이 반대편 hub_3의 port_6을 지시하는 example입니다.

UV PCI bus object attributes

AttributeMeaning

typeIO type

locationLocation of physically connected CPU's UV Hub

slotPhysical PCI slot number

ppb_addrBridged bus address; only for PPB

iio_stackConnected IIO stack number

PCI bus address별 physical placement와 bridge metadata입니다.

Known UV PCI bus types

Type

BASE IO

PCIe IO

PCIe SLOT

NODE IO

Riser

PPB

모든 UV versions에서 알려진 type strings입니다.

/sys/firmware/sgi_uv/hubs/hub_5/port_3/conn_hub = 3
/sys/firmware/sgi_uv/hubs/hub_5/port_3/conn_port = 6

Connected endpoint:
/sys/firmware/sgi_uv/hubs/hub_3/port_6