요약·해설과 원문, 전문 번역을 서로 분리했습니다. API 이름, symbol, source path는 원문 표기를 사용합니다.
1. 요약·해설
원문의 핵심 논리와 kernel programming 관점의 보충 설명입니다. 아래의 전문 번역과는 별도로 작성했습니다.
2. 영어 원문 전체
번역 기준이 된 Linux v6.18.37 원문입니다. 줄 번호는 이 버전의 파일 좌표입니다.
원문 전체 펼치기
1
.. SPDX-License-Identifier: (GPL-2.0+ OR MIT)
3
=========================
4
FWSEC (Firmware Security)
5
=========================
6
This document briefly/conceptually describes the FWSEC (Firmware Security) image
7
and its role in the GPU boot sequence. As such, this information is subject to
8
change in the future and is only current as of the Ampere GPU family. However,
9
hopefully the concepts described will be useful for understanding the kernel code
10
that deals with it. All the information is derived from publicly available
11
sources such as public drivers and documentation.
13
The role of FWSEC is to provide a secure boot process. It runs in
14
'Heavy-secure' mode, and performs firmware verification after a GPU reset
15
before loading various ucode images onto other microcontrollers on the GPU,
16
such as the PMU and GSP.
18
FWSEC itself is an application stored in the VBIOS ROM in the FWSEC partition of
19
ROM (see vbios.rst for more details). It contains different commands like FRTS
20
(Firmware Runtime Services) and SB (Secure Booting other microcontrollers after
21
reset and loading them with other non-FWSEC ucode). The kernel driver only needs
22
to perform FRTS, since Secure Boot (SB) has already completed by the time the driver
23
is loaded.
25
The FRTS command carves out the WPR2 region (Write protected region) which contains
26
data required for power management. Once setup, only HS mode ucode can access it
27
(see falcon.rst for privilege levels).
29
The FWSEC image is located in the VBIOS ROM in the partition of the ROM that contains
30
various ucode images (also known as applications) -- one of them being FWSEC. For how
31
it is extracted, see vbios.rst and the vbios.rs source code.
33
The Falcon data for each ucode images (including the FWSEC image) is a combination
34
of headers, data sections (DMEM) and instruction code sections (IMEM). All these
35
ucode images are stored in the same ROM partition and the PMU table is used to look
36
up the application to load it based on its application ID (see vbios.rs).
38
For the nova-core driver, the FWSEC contains an 'application interface' called
39
DMEMMAPPER. This interface is used to execute the 'FWSEC-FRTS' command, among others.
40
For Ampere, FWSEC is running on the GSP in Heavy-secure mode and runs FRTS.
42
FWSEC Memory Layout
43
-------------------
44
The memory layout of the FWSEC image is as follows::
46
+---------------------------------------------------------------+
47
| FWSEC ROM image (type 0xE0) |
48
| |
49
| +---------------------------------+ |
50
| | PMU Falcon Ucode Table | |
51
| | (PmuLookupTable) | |
52
| | +-------------------------+ | |
53
| | | Table Header | | |
54
| | | - version: 0x01 | | |
55
| | | - header_size: 6 | | |
56
| | | - entry_size: 6 | | |
57
| | | - entry_count: N | | |
58
| | | - desc_version:3(unused)| | |
59
| | +-------------------------+ | |
60
| | ... | |
61
| | +-------------------------+ | |
62
| | | Entry for FWSEC (0x85) | | |
63
| | | (PmuLookupTableEntry) | | |
64
| | | - app_id: 0x85 (FWSEC) |----|----+ |
65
| | | - target_id: 0x01 (PMU) | | | |
66
| | | - data: offset ---------|----|----|---+ look up FWSEC |
67
| | +-------------------------+ | | | |
68
| +---------------------------------+ | | |
69
| | | |
70
| | | |
71
| +---------------------------------+ | | |
72
| | FWSEC Ucode Component |<---+ | |
73
| | (aka Falcon data) | | |
74
| | +-------------------------+ | | |
75
| | | FalconUCodeDescV3 |<---|--------+ |
76
| | | - hdr | | |
77
| | | - stored_size | | |
78
| | | - pkc_data_offset | | |
79
| | | - interface_offset -----|----|----------------+ |
80
| | | - imem_phys_base | | | |
81
| | | - imem_load_size | | | |
82
| | | - imem_virt_base | | | |
83
| | | - dmem_phys_base | | | |
84
| | | - dmem_load_size | | | |
85
| | | - engine_id_mask | | | |
86
| | | - ucode_id | | | |
87
| | | - signature_count | | look up sig | |
88
| | | - signature_versions --------------+ | |
89
| | +-------------------------+ | | | |
90
| | (no gap) | | | |
91
| | +-------------------------+ | | | |
92
| | | Signatures Section |<---|-----+ | |
93
| | | (384 bytes per sig) | | | |
94
| | | - RSA-3K Signature 1 | | | |
95
| | | - RSA-3K Signature 2 | | | |
96
| | | ... | | | |
97
| | +-------------------------+ | | |
98
| | | | |
99
| | +-------------------------+ | | |
100
| | | IMEM Section (Code) | | | |
101
| | | | | | |
102
| | | Contains instruction | | | |
103
| | | code etc. | | | |
104
| | +-------------------------+ | | |
105
| | | | |
106
| | +-------------------------+ | | |
107
| | | DMEM Section (Data) | | | |
108
| | | | | | |
109
| | | +---------------------+ | | | |
110
| | | | Application | |<---|----------------+ |
111
| | | | Interface Table | | | |
112
| | | | (FalconAppifHdrV1) | | | |
113
| | | | Header: | | | |
114
| | | | - version: 0x01 | | | |
115
| | | | - header_size: 4 | | | |
116
| | | | - entry_size: 8 | | | |
117
| | | | - entry_count: N | | | |
118
| | | | | | | |
119
| | | | Entries: | | | |
120
| | | | +-----------------+ | | | |
121
| | | | | DEVINIT (ID 1) | | | | |
122
| | | | | - id: 0x01 | | | | |
123
| | | | | - dmemOffset X -|-|-|----+ |
124
| | | | +-----------------+ | | | |
125
| | | | +-----------------+ | | | |
126
| | | | | DMEMMAPPER(ID 4)| | | | |
127
| | | | | - id: 0x04 | | | | Used only for DevInit |
128
| | | | | (NVFW_FALCON_ | | | | application (not FWSEC) |
129
| | | | | APPIF_ID_DMEMMAPPER) | |
130
| | | | | - dmemOffset Y -|-|-|----|-----+ |
131
| | | | +-----------------+ | | | | |
132
| | | +---------------------+ | | | |
133
| | | | | | |
134
| | | +---------------------+ | | | |
135
| | | | DEVINIT Engine |<|----+ | Used by FWSEC |
136
| | | | Interface | | | | app. |
137
| | | +---------------------+ | | | |
138
| | | | | | |
139
| | | +---------------------+ | | | |
140
| | | | DMEM Mapper (ID 4) |<|----+-----+ |
141
| | | | (FalconAppifDmemmapperV3) | |
142
| | | | - signature: "DMAP" | | | |
143
| | | | - version: 0x0003 | | | |
144
| | | | - Size: 64 bytes | | | |
145
| | | | - cmd_in_buffer_off | |----|------------+ |
146
| | | | - cmd_in_buffer_size| | | | |
147
| | | | - cmd_out_buffer_off| |----|------------|-----+ |
148
| | | | - cmd_out_buffer_sz | | | | | |
149
| | | | - init_cmd | | | | | |
150
| | | | - features | | | | | |
151
| | | | - cmd_mask0/1 | | | | | |
152
| | | +---------------------+ | | | | |
153
| | | | | | | |
154
| | | +---------------------+ | | | | |
155
| | | | Command Input Buffer|<|----|------------+ | |
156
| | | | - Command data | | | | |
157
| | | | - Arguments | | | | |
158
| | | +---------------------+ | | | |
159
| | | | | | |
160
| | | +---------------------+ | | | |
161
| | | | Command Output |<|----|------------------+ |
162
| | | | Buffer | | | |
163
| | | | - Results | | | |
164
| | | | - Status | | | |
165
| | | +---------------------+ | | |
166
| | +-------------------------+ | |
167
| +---------------------------------+ |
168
| |
169
+---------------------------------------------------------------+
171
.. note::
172
This is using an GA-102 Ampere GPU as an example and could vary for future GPUs.
174
.. note::
175
The FWSEC image also plays a role in memory scrubbing (ECC initialization) and VPR
176
(Video Protected Region) initialization as well. Before the nova-core driver is even
177
loaded, the FWSEC image is running on the GSP in heavy-secure mode. After the devinit
178
sequence completes, it does VRAM memory scrubbing (ECC initialization). On consumer
179
GPUs, it scrubs only part of memory and then initiates 'async scrubbing'. Before this
180
async scrubbing completes, the unscrubbed VRAM cannot be used for allocation (thus DRM
181
memory allocators need to wait for this scrubbing to complete).
3. 한국어 전문 번역
영어 원문의 문단 순서와 의미를 유지한 전체 번역입니다. 코드, 함수명, symbol과 URL은 원문 표기를 유지합니다.
FWSEC image와 secure boot
1-41이 문서는 FWSEC(Firmware Security) image와 GPU boot sequence에서의 역할을 개념적으로 설명합니다. Ampere GPU family 시점의 공개 driver·documentation을 바탕으로 하며 미래에는 바뀔 수 있지만, 관련 kernel code를 이해하는 데 필요한 개념을 제공합니다. 원문 SPDX 라이선스는 `(GPL-2.0+ OR MIT)`입니다.
FWSEC의 역할은 secure boot를 제공하는 것입니다. GPU reset 뒤 heavy-secure mode로 실행되어 firmware를 검증하고 PMU·GSP 같은 다른 GPU microcontroller에 여러 ucode image를 load합니다.
FWSEC application은 VBIOS ROM의 FWSEC partition에 저장됩니다. `vbios.rst`가 자세한 위치를 설명합니다. FWSEC에는 FRTS(Firmware Runtime Services)와 SB(reset 뒤 다른 microcontroller를 secure boot하고 non-FWSEC ucode를 load) 같은 command가 있습니다.
Driver가 load될 때는 Secure Boot(SB)가 이미 끝났으므로 kernel driver는 FRTS만 수행하면 됩니다. FRTS command는 power management data를 담는 write-protected `WPR2` region을 carve out합니다. 설정 뒤에는 HS mode ucode만 WPR2에 접근할 수 있으며 privilege level은 `falcon.rst`를 참고합니다.
FWSEC를 포함한 여러 ucode application은 VBIOS ROM의 같은 partition에 있습니다. 추출 방법은 `vbios.rst`와 `vbios.rs`가 설명합니다. 각 Falcon ucode image는 header, DMEM data section, IMEM instruction code section을 조합한 형태입니다.
PMU table은 application ID로 load할 image를 찾습니다. `nova-core`에서 FWSEC는 `DMEMMAPPER`라는 application interface를 제공하며, 이 interface로 `FWSEC-FRTS` command 등을 실행합니다. Ampere에서는 GSP의 heavy-secure mode로 FWSEC를 실행하여 FRTS를 수행합니다.
GPU reset→VBIOS ROM partition에서 FWSEC application 조회→GSP heavy-secure mode로 FWSEC 실행→SB가 다른 microcontroller의 ucode를 secure boot→Kernel load 뒤 DMEMMAPPER로 FWSEC-FRTS 실행→Power management용 WPR2 carve-out
Reset부터 보호 영역 설정까지의 secure path입니다.
Command역할Kernel 시점
SB다른 microcontroller secure boot·ucode loadDriver load 전에 완료
FRTSWPR2 power-management region 설정Kernel driver가 수행
Boot 시점에 수행되는 command와 kernel 책임입니다.
.. SPDX-License-Identifier: (GPL-2.0+ OR MIT)
=========================
FWSEC (Firmware Security)
=========================
This document briefly/conceptually describes the FWSEC (Firmware Security) image
and its role in the GPU boot sequence. As such, this information is subject to
change in the future and is only current as of the Ampere GPU family. However,
hopefully the concepts described will be useful for understanding the kernel code
that deals with it. All the information is derived from publicly available
sources such as public drivers and documentation.
The role of FWSEC is to provide a secure boot process. It runs in
'Heavy-secure' mode, and performs firmware verification after a GPU reset
before loading various ucode images onto other microcontrollers on the GPU,
such as the PMU and GSP.
FWSEC itself is an application stored in the VBIOS ROM in the FWSEC partition of
ROM (see vbios.rst for more details). It contains different commands like FRTS
(Firmware Runtime Services) and SB (Secure Booting other microcontrollers after
reset and loading them with other non-FWSEC ucode). The kernel driver only needs
to perform FRTS, since Secure Boot (SB) has already completed by the time the driver
is loaded.
The FRTS command carves out the WPR2 region (Write protected region) which contains
data required for power management. Once setup, only HS mode ucode can access it
(see falcon.rst for privilege levels).
The FWSEC image is located in the VBIOS ROM in the partition of the ROM that contains
various ucode images (also known as applications) -- one of them being FWSEC. For how
it is extracted, see vbios.rst and the vbios.rs source code.
The Falcon data for each ucode images (including the FWSEC image) is a combination
of headers, data sections (DMEM) and instruction code sections (IMEM). All these
ucode images are stored in the same ROM partition and the PMU table is used to look
up the application to load it based on its application ID (see vbios.rs).
For the nova-core driver, the FWSEC contains an 'application interface' called
DMEMMAPPER. This interface is used to execute the 'FWSEC-FRTS' command, among others.
For Ampere, FWSEC is running on the GSP in Heavy-secure mode and runs FRTS.
FWSEC ROM image memory layout
42-170원문 구조도는 type `0xE0`의 FWSEC ROM image를 보여 줍니다. `PmuLookupTable` header는 `version 0x01`, `header_size 6`, `entry_size 6`, `entry_count N`, 사용하지 않는 `desc_version 3`을 기록합니다.
FWSEC lookup entry는 `app_id 0x85`, `target_id 0x01 (PMU)`, component를 가리키는 data offset을 갖습니다. 이 entry가 FWSEC ucode component, 즉 Falcon data를 찾습니다.
`FalconUCodeDescV3` descriptor에는 header·stored size·public-key cryptography data offset, application interface offset, IMEM physical/load/virtual address, DMEM physical/load size, engine ID mask, ucode ID, signature count와 versions가 있습니다.
Descriptor 바로 뒤에는 gap 없이 signature section이 오며 signature 하나당 384 bytes의 RSA-3K signature를 저장합니다. 이어서 IMEM code section과 DMEM data section이 배치됩니다.
DMEM의 `FalconAppifHdrV1` application interface table header는 `version 0x01`, `header_size 4`, `entry_size 8`, `entry_count N`을 가집니다. Entry에는 `DEVINIT (ID 1)`과 `DMEMMAPPER (ID 4)`가 있고 각각 interface의 DMEM offset을 가리킵니다.
도식의 주석에 따르면 DMEMMAPPER ID 4 entry는 DevInit application에서만 사용하지만, DEVINIT engine interface는 FWSEC application이 사용합니다. `FalconAppifDmemmapperV3`는 signature `DMAP`, version `0x0003`, size 64 bytes이며 command input/output buffer offset·size, `init_cmd`, `features`, `cmd_mask0/1`을 정의합니다.
Command Input Buffer에는 command data와 argument가 들어가고, Command Output Buffer에는 result와 status가 기록됩니다. Descriptor의 `interface_offset`이 application table을 찾고, 각 entry의 `dmemOffset`이 실제 interface structure로 이어지며, mapper의 buffer offset이 input/output buffer를 찾습니다.
FWSEC ROM image type 0xE0→PmuLookupTable → FWSEC entry app_id 0x85→data offset → FWSEC Ucode Component→FalconUCodeDescV3 → signatures·IMEM·DMEM→interface_offset → FalconAppifHdrV1 entries→DMEMMAPPER → command input/output buffers
ROM table에서 command buffer까지 이어지는 구조입니다.
Field값·의미
version0x01
header_size·entry_size6·6
entry_countN
FWSEC app_id0x85
target_id0x01, PMU
dataFWSEC component offset
FWSEC component를 찾는 table metadata입니다.
Field group내용
Storagehdr·stored_size·pkc_data_offset
Interfaceinterface_offset
IMEMphys_base·load_size·virt_base
DMEMphys_base·load_size
Identityengine_id_mask·ucode_id
Signaturesignature_count·signature_versions
Ucode section과 signature·interface 위치를 기술합니다.
구조핵심 field
FalconAppifHdrV1version 0x01·header 4·entry 8·count N
DEVINITID 1·dmemOffset X
DMEMMAPPERID 4·dmemOffset Y
FalconAppifDmemmapperV3DMAP·v0x0003·64 bytes
Command inputCommand data·arguments
Command outputResults·status
Command interface와 buffer field입니다.
FWSEC Memory Layout
-------------------
The memory layout of the FWSEC image is as follows::
+---------------------------------------------------------------+
| FWSEC ROM image (type 0xE0) |
| |
| +---------------------------------+ |
| | PMU Falcon Ucode Table | |
| | (PmuLookupTable) | |
| | +-------------------------+ | |
| | | Table Header | | |
| | | - version: 0x01 | | |
| | | - header_size: 6 | | |
| | | - entry_size: 6 | | |
| | | - entry_count: N | | |
| | | - desc_version:3(unused)| | |
| | +-------------------------+ | |
| | ... | |
| | +-------------------------+ | |
| | | Entry for FWSEC (0x85) | | |
| | | (PmuLookupTableEntry) | | |
| | | - app_id: 0x85 (FWSEC) |----|----+ |
| | | - target_id: 0x01 (PMU) | | | |
| | | - data: offset ---------|----|----|---+ look up FWSEC |
| | +-------------------------+ | | | |
| +---------------------------------+ | | |
| | | |
| | | |
| +---------------------------------+ | | |
| | FWSEC Ucode Component |<---+ | |
| | (aka Falcon data) | | |
| | +-------------------------+ | | |
| | | FalconUCodeDescV3 |<---|--------+ |
| | | - hdr | | |
| | | - stored_size | | |
| | | - pkc_data_offset | | |
| | | - interface_offset -----|----|----------------+ |
| | | - imem_phys_base | | | |
| | | - imem_load_size | | | |
| | | - imem_virt_base | | | |
| | | - dmem_phys_base | | | |
| | | - dmem_load_size | | | |
| | | - engine_id_mask | | | |
| | | - ucode_id | | | |
| | | - signature_count | | look up sig | |
| | | - signature_versions --------------+ | |
| | +-------------------------+ | | | |
| | (no gap) | | | |
| | +-------------------------+ | | | |
| | | Signatures Section |<---|-----+ | |
| | | (384 bytes per sig) | | | |
| | | - RSA-3K Signature 1 | | | |
| | | - RSA-3K Signature 2 | | | |
| | | ... | | | |
| | +-------------------------+ | | |
| | | | |
| | +-------------------------+ | | |
| | | IMEM Section (Code) | | | |
| | | | | | |
| | | Contains instruction | | | |
| | | code etc. | | | |
| | +-------------------------+ | | |
| | | | |
| | +-------------------------+ | | |
| | | DMEM Section (Data) | | | |
| | | | | | |
| | | +---------------------+ | | | |
| | | | Application | |<---|----------------+ |
| | | | Interface Table | | | |
| | | | (FalconAppifHdrV1) | | | |
| | | | Header: | | | |
| | | | - version: 0x01 | | | |
| | | | - header_size: 4 | | | |
| | | | - entry_size: 8 | | | |
| | | | - entry_count: N | | | |
| | | | | | | |
| | | | Entries: | | | |
| | | | +-----------------+ | | | |
| | | | | DEVINIT (ID 1) | | | | |
| | | | | - id: 0x01 | | | | |
| | | | | - dmemOffset X -|-|-|----+ |
| | | | +-----------------+ | | | |
| | | | +-----------------+ | | | |
| | | | | DMEMMAPPER(ID 4)| | | | |
| | | | | - id: 0x04 | | | | Used only for DevInit |
| | | | | (NVFW_FALCON_ | | | | application (not FWSEC) |
| | | | | APPIF_ID_DMEMMAPPER) | |
| | | | | - dmemOffset Y -|-|-|----|-----+ |
| | | | +-----------------+ | | | | |
| | | +---------------------+ | | | |
| | | | | | |
| | | +---------------------+ | | | |
| | | | DEVINIT Engine |<|----+ | Used by FWSEC |
| | | | Interface | | | | app. |
| | | +---------------------+ | | | |
| | | | | | |
| | | +---------------------+ | | | |
| | | | DMEM Mapper (ID 4) |<|----+-----+ |
| | | | (FalconAppifDmemmapperV3) | |
| | | | - signature: "DMAP" | | | |
| | | | - version: 0x0003 | | | |
| | | | - Size: 64 bytes | | | |
| | | | - cmd_in_buffer_off | |----|------------+ |
| | | | - cmd_in_buffer_size| | | | |
| | | | - cmd_out_buffer_off| |----|------------|-----+ |
| | | | - cmd_out_buffer_sz | | | | | |
| | | | - init_cmd | | | | | |
| | | | - features | | | | | |
| | | | - cmd_mask0/1 | | | | | |
| | | +---------------------+ | | | | |
| | | | | | | |
| | | +---------------------+ | | | | |
| | | | Command Input Buffer|<|----|------------+ | |
| | | | - Command data | | | | |
| | | | - Arguments | | | | |
| | | +---------------------+ | | | |
| | | | | | |
| | | +---------------------+ | | | |
| | | | Command Output |<|----|------------------+ |
| | | | Buffer | | | |
| | | | - Results | | | |
| | | | - Status | | | |
| | | +---------------------+ | | |
| | +-------------------------+ | |
| +---------------------------------+ |
| |
+---------------------------------------------------------------+
GA-102 예와 VRAM scrubbing
171-181이 memory layout은 GA-102 Ampere GPU를 예로 든 것이며 미래 GPU에서는 달라질 수 있습니다.
FWSEC image는 memory scrubbing(ECC initialization)과 VPR(Video Protected Region) initialization에도 관여합니다. `nova-core` driver가 load되기 전부터 FWSEC는 GSP의 heavy-secure mode로 실행되고 있습니다.
Devinit sequence가 끝나면 FWSEC가 VRAM memory scrubbing을 수행합니다. Consumer GPU에서는 memory 일부를 먼저 scrub한 뒤 `async scrubbing`을 시작합니다. 이 작업이 끝나기 전에는 아직 scrub하지 않은 VRAM을 allocation에 사용할 수 없으므로 DRM memory allocator는 완료를 기다려야 합니다.
FWSEC heavy-secure가 driver load 전에 실행→Devinit sequence 완료→VRAM ECC memory scrubbing→Consumer GPU는 일부 scrub 뒤 async scrubbing 시작→DRM allocator가 완료를 기다린 뒤 unscrubbed 영역 사용
Devinit 완료 뒤 VRAM allocation이 가능해지는 순서입니다.
기능효과
ECC scrubbingVRAM error-correction state 초기화
VPR initializationVideo Protected Region 준비
Async scrubbing gate완료 전 unscrubbed VRAM allocation 금지
Secure boot 외 memory 초기화 역할입니다.
.. note::
This is using an GA-102 Ampere GPU as an example and could vary for future GPUs.
.. note::
The FWSEC image also plays a role in memory scrubbing (ECC initialization) and VPR
(Video Protected Region) initialization as well. Before the nova-core driver is even
loaded, the FWSEC image is running on the GSP in heavy-secure mode. After the devinit
sequence completes, it does VRAM memory scrubbing (ECC initialization). On consumer
GPUs, it scrubs only part of memory and then initiates 'async scrubbing'. Before this
async scrubbing completes, the unscrubbed VRAM cannot be used for allocation (thus DRM
memory allocators need to wait for this scrubbing to complete).
요약·해설
fwsec.rst:1-181FWSEC secure boot, FRTS·WPR2, ROM image layout과 VRAM scrubbing을 설명합니다.
문서의 중심 개념과 연결 지점입니다.