Based on kernel version 6.13
. Page generated on 2025-01-21 08:21 EST
.
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 59 60 61 62 63 64 65 66 67 68 69 70 71 72 73 74 75 76 77 78 79 80 81 82 83 84 85 86 87 88 89 90 91 92 93 94 95 96 97 98 99 100 101 102 103 104 105 106 107 108 109 110 111 112 113 114 115 116 117 118 119 120 121 122 123 124 125 126 127 128 129 130 131 132 133 134 135 136 137 138 139 140 141 142 143 144 145 146 147 148 149 150 151 152 153 154 155 156 157 158 159 160 161 162 163 164 165 166 167 168 169 170 171 172 173 174 175 176 177 178 179 180 181 182 183 184 185 186 187 188 189 190 191 192 193 194 195 196 197 198 199 200 201 202 203 204 205 206 207 208 209 210 211 212 213 214 215 216 217 218 219 220 221 222 223 224 225 226 227 228 229 230 231 232 233 234 235 236 237 238 239 240 241 242 243 244 245 246 247 248 249 250 251 252 253 254 255 256 257 258 259 260 261 262 263 264 265 266 267 268 269 270 271 272 273 274 275 276 277 278 279 280 281 282 283 284 285 286 287 288 289 290 291 292 293 294 295 296 297 298 299 300 301 302 303 304 305 306 307 308 309 310 311 312 313 314 315 316 317 318 319 320 321 322 323 324 325 326 327 328 329 330 331 332 333 334 335 336 337 338 339 340 341 342 343 344 345 346 347 348 349 350 351 352 353 354 355 356 357 358 359 360 361 362 363 364 365 366 367 368 369 370 371 372 373 374 375 376 377 378 379 380 381 382 383 384 385 386 387 388 389 390 391 392 393 394 395 396 397 398 | .. SPDX-License-Identifier: GPL-2.0 .. include:: <isonum.txt> =================================== Compute Express Link Memory Devices =================================== A Compute Express Link Memory Device is a CXL component that implements the CXL.mem protocol. It contains some amount of volatile memory, persistent memory, or both. It is enumerated as a PCI device for configuration and passing messages over an MMIO mailbox. Its contribution to the System Physical Address space is handled via HDM (Host Managed Device Memory) decoders that optionally define a device's contribution to an interleaved address range across multiple devices underneath a host-bridge or interleaved across host-bridges. CXL Bus: Theory of Operation ============================ Similar to how a RAID driver takes disk objects and assembles them into a new logical device, the CXL subsystem is tasked to take PCIe and ACPI objects and assemble them into a CXL.mem decode topology. The need for runtime configuration of the CXL.mem topology is also similar to RAID in that different environments with the same hardware configuration may decide to assemble the topology in contrasting ways. One may choose performance (RAID0) striping memory across multiple Host Bridges and endpoints while another may opt for fault tolerance and disable any striping in the CXL.mem topology. Platform firmware enumerates a menu of interleave options at the "CXL root port" (Linux term for the top of the CXL decode topology). From there, PCIe topology dictates which endpoints can participate in which Host Bridge decode regimes. Each PCIe Switch in the path between the root and an endpoint introduces a point at which the interleave can be split. For example platform firmware may say at a given range only decodes to 1 one Host Bridge, but that Host Bridge may in turn interleave cycles across multiple Root Ports. An intervening Switch between a port and an endpoint may interleave cycles across multiple Downstream Switch Ports, etc. Here is a sample listing of a CXL topology defined by 'cxl_test'. The 'cxl_test' module generates an emulated CXL topology of 2 Host Bridges each with 2 Root Ports. Each of those Root Ports are connected to 2-way switches with endpoints connected to those downstream ports for a total of 8 endpoints:: # cxl list -BEMPu -b cxl_test { "bus":"root3", "provider":"cxl_test", "ports:root3":[ { "port":"port5", "host":"cxl_host_bridge.1", "ports:port5":[ { "port":"port8", "host":"cxl_switch_uport.1", "endpoints:port8":[ { "endpoint":"endpoint9", "host":"mem2", "memdev":{ "memdev":"mem2", "pmem_size":"256.00 MiB (268.44 MB)", "ram_size":"256.00 MiB (268.44 MB)", "serial":"0x1", "numa_node":1, "host":"cxl_mem.1" } }, { "endpoint":"endpoint15", "host":"mem6", "memdev":{ "memdev":"mem6", "pmem_size":"256.00 MiB (268.44 MB)", "ram_size":"256.00 MiB (268.44 MB)", "serial":"0x5", "numa_node":1, "host":"cxl_mem.5" } } ] }, { "port":"port12", "host":"cxl_switch_uport.3", "endpoints:port12":[ { "endpoint":"endpoint17", "host":"mem8", "memdev":{ "memdev":"mem8", "pmem_size":"256.00 MiB (268.44 MB)", "ram_size":"256.00 MiB (268.44 MB)", "serial":"0x7", "numa_node":1, "host":"cxl_mem.7" } }, { "endpoint":"endpoint13", "host":"mem4", "memdev":{ "memdev":"mem4", "pmem_size":"256.00 MiB (268.44 MB)", "ram_size":"256.00 MiB (268.44 MB)", "serial":"0x3", "numa_node":1, "host":"cxl_mem.3" } } ] } ] }, { "port":"port4", "host":"cxl_host_bridge.0", "ports:port4":[ { "port":"port6", "host":"cxl_switch_uport.0", "endpoints:port6":[ { "endpoint":"endpoint7", "host":"mem1", "memdev":{ "memdev":"mem1", "pmem_size":"256.00 MiB (268.44 MB)", "ram_size":"256.00 MiB (268.44 MB)", "serial":"0", "numa_node":0, "host":"cxl_mem.0" } }, { "endpoint":"endpoint14", "host":"mem5", "memdev":{ "memdev":"mem5", "pmem_size":"256.00 MiB (268.44 MB)", "ram_size":"256.00 MiB (268.44 MB)", "serial":"0x4", "numa_node":0, "host":"cxl_mem.4" } } ] }, { "port":"port10", "host":"cxl_switch_uport.2", "endpoints:port10":[ { "endpoint":"endpoint16", "host":"mem7", "memdev":{ "memdev":"mem7", "pmem_size":"256.00 MiB (268.44 MB)", "ram_size":"256.00 MiB (268.44 MB)", "serial":"0x6", "numa_node":0, "host":"cxl_mem.6" } }, { "endpoint":"endpoint11", "host":"mem3", "memdev":{ "memdev":"mem3", "pmem_size":"256.00 MiB (268.44 MB)", "ram_size":"256.00 MiB (268.44 MB)", "serial":"0x2", "numa_node":0, "host":"cxl_mem.2" } } ] } ] } ] } In that listing each "root", "port", and "endpoint" object correspond a kernel 'struct cxl_port' object. A 'cxl_port' is a device that can decode CXL.mem to its descendants. So "root" claims non-PCIe enumerable platform decode ranges and decodes them to "ports", "ports" decode to "endpoints", and "endpoints" represent the decode from SPA (System Physical Address) to DPA (Device Physical Address). Continuing the RAID analogy, disks have both topology metadata and on device metadata that determine RAID set assembly. CXL Port topology and CXL Port link status is metadata for CXL.mem set assembly. The CXL Port topology is enumerated by the arrival of a CXL.mem device. I.e. unless and until the PCIe core attaches the cxl_pci driver to a CXL Memory Expander there is no role for CXL Port objects. Conversely for hot-unplug / removal scenarios, there is no need for the Linux PCI core to tear down switch-level CXL resources because the endpoint ->remove() event cleans up the port data that was established to support that Memory Expander. The port metadata and potential decode schemes that a give memory device may participate can be determined via a command like:: # cxl list -BDMu -d root -m mem3 { "bus":"root3", "provider":"cxl_test", "decoders:root3":[ { "decoder":"decoder3.1", "resource":"0x8030000000", "size":"512.00 MiB (536.87 MB)", "volatile_capable":true, "nr_targets":2 }, { "decoder":"decoder3.3", "resource":"0x8060000000", "size":"512.00 MiB (536.87 MB)", "pmem_capable":true, "nr_targets":2 }, { "decoder":"decoder3.0", "resource":"0x8020000000", "size":"256.00 MiB (268.44 MB)", "volatile_capable":true, "nr_targets":1 }, { "decoder":"decoder3.2", "resource":"0x8050000000", "size":"256.00 MiB (268.44 MB)", "pmem_capable":true, "nr_targets":1 } ], "memdevs:root3":[ { "memdev":"mem3", "pmem_size":"256.00 MiB (268.44 MB)", "ram_size":"256.00 MiB (268.44 MB)", "serial":"0x2", "numa_node":0, "host":"cxl_mem.2" } ] } ...which queries the CXL topology to ask "given CXL Memory Expander with a kernel device name of 'mem3' which platform level decode ranges may this device participate". A given expander can participate in multiple CXL.mem interleave sets simultaneously depending on how many decoder resource it has. In this example mem3 can participate in one or more of a PMEM interleave that spans to Host Bridges, a PMEM interleave that targets a single Host Bridge, a Volatile memory interleave that spans 2 Host Bridges, and a Volatile memory interleave that only targets a single Host Bridge. Conversely the memory devices that can participate in a given platform level decode scheme can be determined via a command like the following:: # cxl list -MDu -d 3.2 [ { "memdevs":[ { "memdev":"mem1", "pmem_size":"256.00 MiB (268.44 MB)", "ram_size":"256.00 MiB (268.44 MB)", "serial":"0", "numa_node":0, "host":"cxl_mem.0" }, { "memdev":"mem5", "pmem_size":"256.00 MiB (268.44 MB)", "ram_size":"256.00 MiB (268.44 MB)", "serial":"0x4", "numa_node":0, "host":"cxl_mem.4" }, { "memdev":"mem7", "pmem_size":"256.00 MiB (268.44 MB)", "ram_size":"256.00 MiB (268.44 MB)", "serial":"0x6", "numa_node":0, "host":"cxl_mem.6" }, { "memdev":"mem3", "pmem_size":"256.00 MiB (268.44 MB)", "ram_size":"256.00 MiB (268.44 MB)", "serial":"0x2", "numa_node":0, "host":"cxl_mem.2" } ] }, { "root decoders":[ { "decoder":"decoder3.2", "resource":"0x8050000000", "size":"256.00 MiB (268.44 MB)", "pmem_capable":true, "nr_targets":1 } ] } ] ...where the naming scheme for decoders is "decoder<port_id>.<instance_id>". Driver Infrastructure ===================== This section covers the driver infrastructure for a CXL memory device. CXL Memory Device ----------------- .. kernel-doc:: drivers/cxl/pci.c :doc: cxl pci .. kernel-doc:: drivers/cxl/pci.c :internal: .. kernel-doc:: drivers/cxl/mem.c :doc: cxl mem .. kernel-doc:: drivers/cxl/cxlmem.h :internal: .. kernel-doc:: drivers/cxl/core/memdev.c :identifiers: CXL Port -------- .. kernel-doc:: drivers/cxl/port.c :doc: cxl port CXL Core -------- .. kernel-doc:: drivers/cxl/cxl.h :doc: cxl objects .. kernel-doc:: drivers/cxl/cxl.h :internal: .. kernel-doc:: drivers/cxl/core/hdm.c :doc: cxl core hdm .. kernel-doc:: drivers/cxl/core/hdm.c :identifiers: .. kernel-doc:: drivers/cxl/core/cdat.c :identifiers: .. kernel-doc:: drivers/cxl/core/port.c :doc: cxl core .. kernel-doc:: drivers/cxl/core/port.c :identifiers: .. kernel-doc:: drivers/cxl/core/pci.c :doc: cxl core pci .. kernel-doc:: drivers/cxl/core/pci.c :identifiers: .. kernel-doc:: drivers/cxl/core/pmem.c :doc: cxl pmem .. kernel-doc:: drivers/cxl/core/regs.c :doc: cxl registers .. kernel-doc:: drivers/cxl/core/mbox.c :doc: cxl mbox CXL Regions ----------- .. kernel-doc:: drivers/cxl/core/region.c :doc: cxl core region .. kernel-doc:: drivers/cxl/core/region.c :identifiers: External Interfaces =================== CXL IOCTL Interface ------------------- .. kernel-doc:: include/uapi/linux/cxl_mem.h :doc: UAPI .. kernel-doc:: include/uapi/linux/cxl_mem.h :internal: |