[lkml]   [2021]   [Feb]   [9]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
Messages in this thread
Subject[PATCH v2 0/8] CXL 2.0 Support
# Changes since v1 [1]

* Squash together several other patches (Ben)
* Make register locator only search the DVSEC size. Bug fix. (Ben)
* Get rid of anonymous structs in send UAPI (Ben)
* Rename "MB" to "MBOX" in defines (Ben)
* Dynamically allocate enable_cmds bitmask (Ben)
* Async probe (Dan)
* Remove get_live_device() (Dan)
* CXL_MAILBOX_TIMEOUT_MS 2*HZ instead of runtime conversion (Dan)
* Reword RAW Kconfig help (Dan)
* Move IOCTL handlers to their own functions (Dan)
* Remove HIDDEN flag (Dan)
* Remove MUTEX flag (Dan)
* Get rid of const info in mem_command (Dan)
* Remove useless mbox initialiazation in user commands (Dan)
* Remove dev_info of enabled commands (Dan)
* Get rid of MANDATORY and PSEUDO flags (Dan)
* Clarify cmd vs. mbox_cmd in send by removing cmd (Dan)
* This results in removal of some very unlikely debug messages.
* Reword Kconfig (David)
* Cap payload size max to 1M to match spec (David)
* * Driver still binds, but IOCTls fail if too large.
* s/US/MS for timeout (David)
* Fix comment indenting to denote, not part of spec (David)
* Use struct initializer for mailbox command (David)
* Add units to sysfs ABI documentation (David)
* Use FIELD_GET for register locator parsing (hch)
* Use FIELD_GET/SET directly instead of wrappers (hch)
* Remove cpp guards (hch)
* Drop register read/write helpers (hch)
* Squash together device capability patches (hch)
* Move PCI_CLASS_MEMORY_CXL to pci_ids.h (hch)
* Use file_inode instead of file->private_data (hch)
* Hide RAW commands behind CONFIG option (Konrad)
* Include security_locked_down() check (Konrad)
* Extend past 80 characters in certain places (Konrad)
* Remove magic numbers of register locator enumeration (Konrad)
* Fix packing for send UAPI (Konrad)


In addition to the mailing list, please feel free to use #cxl on oftc IRC for


# Summary

Introduce support for “type-3” memory devices defined in the Compute Express
Link (CXL) 2.0 specification [2]. Specifically, these are the memory devices
defined by section of the CXL 2.0 spec. A reference implementation
emulating these devices has been submitted to the QEMU mailing list [3] and is
available on gitlab [4], but will move to a shared tree on after
initial acceptance. “Type-3” is a CXL device that acts as a memory expander for
RAM or Persistent Memory. The device might be interleaved with other CXL devices
in a given physical address range.

In addition to the core functionality of discovering the spec defined registers
and resources, introduce a CXL device model that will be the foundation for
translating CXL capabilities into existing Linux infrastructure for Persistent
Memory and other memory devices. For now, this only includes support for the
management command mailbox the surfacing of type-3 devices. These control
devices fill the role of “DIMMs” / nmemX memory-devices in LIBNVDIMM terms.

## Userspace Interaction

Interaction with the driver and type-3 devices via the CXL drivers is introduced
in this patch series and considered stable ABI. They include

* sysfs - Documentation/ABI/testing/sysfs-bus-cxl
* IOCTL - Documentation/driver-api/cxl/memory-devices.rst
* debugfs - Documentation/ABI/testing/debugfs-debug

Work is in process to add support for CXL interactions to the ndctl project [5]

### Development plans

One of the unique challenges that CXL imposes on the Linux driver model is that
it requires the operating system to perform physical address space management
interleaved across devices and bridges. Whereas LIBNVDIMM handles a list of
established static persistent memory address ranges (for example from the ACPI
NFIT), CXL introduces hotplug and the concept of allocating address space to
instantiate persistent memory ranges. This is similar to PCI in the sense that
the platform establishes the MMIO range for PCI BARs to be allocated, but it is
significantly complicated by the fact that a given device can optionally be
interleaved with other devices and can participate in several interleave-sets at
once. LIBNVDIMM handled something like this with the aliasing between PMEM and
BLOCK-WINDOW mode, but CXL adds flexibility to alias DEVICE MEMORY through up to
10 decoders per device.

All of the above needs to be enabled with respect to PCI hotplug events on
Type-3 memory device which needs hooks to determine if a given device is
contributing to a "System RAM" address range that is unable to be unplugged. In
other words CXL ties PCI hotplug to Memory Hotplug and PCI hotplug needs to be
able to negotiate with memory hotplug. In the medium term the implications of
CXL hotplug vs ACPI SRAT/SLIT/HMAT need to be reconciled. One capability that
seems to be needed is either the dynamic allocation of new memory nodes, or
default initializing extra pgdat instances beyond what is enumerated in ACPI
SRAT to accommodate hot-added CXL memory.

Patches welcome, questions welcome as the development effort on the post v5.12
capabilities proceeds.

## Running in QEMU

The incantation to get CXL support in QEMU [4] is considered unstable at this
time. Future readers of this cover letter should verify if any changes are
needed. For the novice QEMU user, the following can be copy/pasted into a
working QEMU commandline. It is enough to make the simplest topology possible.
The topology would consist of a single memory window, single type3 device,
single root port, and single host bridge.

| |
| +-------+ |<----------+
| |CXL RP | | |
+--+-------+--+ v
| +----------+
| | "window" |
| +----------+
v ^
+-------------+ |
| CXL Type 3 | |
| Device |<----------+

// Memory backend for "window"
-object memory-backend-file,id=cxl-mem1,share,mem-path=cxl-type3,size=512M

// Memory backend for LSA
-object memory-backend-file,id=cxl-mem1-lsa,share,mem-path=cxl-mem1-lsa,size=1K

// Host Bridge
-device pxb-cxl id=cxl.0,bus=pcie.0,bus_nr=52,uid=0 len-window-base=1,window-base[0]=0x4c0000000 memdev[0]=cxl-mem1

// Single root port
-device cxl rp,id=rp0,bus=cxl.0,addr=0.0,chassis=0,slot=0,memdev=cxl-mem1

// Single type3 device
-device cxl-type3,bus=rp0,memdev=cxl-mem1,id=cxl-pmem0,size=256M -device cxl-type3,bus=rp1,memdev=cxl-mem1,id=cxl-pmem1,size=256M,lsa=cxl-mem1-lsa




Ben Widawsky (6):
cxl/mem: Find device capabilities
cxl/mem: Add basic IOCTL interface
cxl/mem: Add a "RAW" send command
cxl/mem: Enable commands via CEL
cxl/mem: Add set of informational commands
MAINTAINERS: Add maintainers of the CXL driver

Dan Williams (2):
cxl/mem: Introduce a driver for CXL-2.0-Type-3 endpoints
cxl/mem: Register CXL memX devices

.clang-format | 1 +
Documentation/ABI/testing/sysfs-bus-cxl | 26 +
Documentation/driver-api/cxl/index.rst | 12 +
.../driver-api/cxl/memory-devices.rst | 46 +
Documentation/driver-api/index.rst | 1 +
.../userspace-api/ioctl/ioctl-number.rst | 1 +
drivers/Kconfig | 1 +
drivers/Makefile | 1 +
drivers/cxl/Kconfig | 67 +
drivers/cxl/Makefile | 7 +
drivers/cxl/bus.c | 29 +
drivers/cxl/cxl.h | 99 ++
drivers/cxl/mem.c | 1544 +++++++++++++++++
drivers/cxl/pci.h | 31 +
include/linux/pci_ids.h | 1 +
include/uapi/linux/cxl_mem.h | 168 ++
include/uapi/linux/pci_regs.h | 1 +
18 files changed, 2047 insertions(+)
create mode 100644 Documentation/ABI/testing/sysfs-bus-cxl
create mode 100644 Documentation/driver-api/cxl/index.rst
create mode 100644 Documentation/driver-api/cxl/memory-devices.rst
create mode 100644 drivers/cxl/Kconfig
create mode 100644 drivers/cxl/Makefile
create mode 100644 drivers/cxl/bus.c
create mode 100644 drivers/cxl/cxl.h
create mode 100644 drivers/cxl/mem.c
create mode 100644 drivers/cxl/pci.h
create mode 100644 include/uapi/linux/cxl_mem.h

Cc: Bjorn Helgaas <>
Cc: Chris Browy <>
Cc: Christoph Hellwig <>
Cc: Dan Williams <>
Cc: David Hildenbrand <>
Cc: David Rientjes <>
Cc: Ira Weiny <>
Cc: Jon Masters <>
Cc: Jonathan Cameron <>
Cc: Rafael Wysocki <>
Cc: Randy Dunlap <>
Cc: Vishal Verma <>
Cc: "John Groves (jgroves)" <>
Cc: "Kelley, Sean V" <>


 \ /
  Last update: 2021-02-10 02:51    [W:0.426 / U:1.744 seconds]
©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site