2021-08-03 01:29:38 +08:00
|
|
|
# SPDX-License-Identifier: GPL-2.0
|
|
|
|
|
obj-$(CONFIG_CXL_BUS) += cxl_core.o
|
2022-04-23 06:58:11 +08:00
|
|
|
obj-$(CONFIG_CXL_SUSPEND) += suspend.o
|
2021-08-03 01:29:38 +08:00
|
|
|
|
2021-11-13 08:32:58 +08:00
|
|
|
ccflags-y += -I$(srctree)/drivers/cxl
|
2022-01-24 08:29:21 +08:00
|
|
|
cxl_core-y := port.o
|
2021-08-03 01:29:49 +08:00
|
|
|
cxl_core-y += pmem.o
|
2021-08-03 22:25:38 +08:00
|
|
|
cxl_core-y += regs.o
|
2021-08-03 01:30:05 +08:00
|
|
|
cxl_core-y += memdev.o
|
2021-09-09 13:12:32 +08:00
|
|
|
cxl_core-y += mbox.o
|
2022-02-01 10:10:04 +08:00
|
|
|
cxl_core-y += pci.o
|
2022-02-02 04:24:30 +08:00
|
|
|
cxl_core-y += hdm.o
|
cxl/region: Add region creation support
CXL 2.0 allows for dynamic provisioning of new memory regions (system
physical address resources like "System RAM" and "Persistent Memory").
Whereas DDR and PMEM resources are conveyed statically at boot, CXL
allows for assembling and instantiating new regions from the available
capacity of CXL memory expanders in the system.
Sysfs with an "echo $region_name > $create_region_attribute" interface
is chosen as the mechanism to initiate the provisioning process. This
was chosen over ioctl() and netlink() to keep the configuration
interface entirely in a pseudo-fs interface, and it was chosen over
configfs since, aside from this one creation event, the interface is
read-mostly. I.e. configfs supports cases where an object is designed to
be provisioned each boot, like an iSCSI storage target, and CXL region
creation is mostly for PMEM regions which are created usually once
per-lifetime of a server instance. This is an improvement over nvdimm
that pre-created "seed" devices that tended to confuse users looking to
determine which devices are active and which are idle.
Recall that the major change that CXL brings over previous persistent
memory architectures is the ability to dynamically define new regions.
Compare that to drivers like 'nfit' where the region configuration is
statically defined by platform firmware.
Regions are created as a child of a root decoder that encompasses an
address space with constraints. When created through sysfs, the root
decoder is explicit. When created from an LSA's region structure a root
decoder will possibly need to be inferred by the driver.
Upon region creation through sysfs, a vacant region is created with a
unique name. Regions have a number of attributes that must be configured
before the region can be bound to the driver where HDM decoder program
is completed.
An example of creating a new region:
- Allocate a new region name:
region=$(cat /sys/bus/cxl/devices/decoder0.0/create_pmem_region)
- Create a new region by name:
while
region=$(cat /sys/bus/cxl/devices/decoder0.0/create_pmem_region)
! echo $region > /sys/bus/cxl/devices/decoder0.0/create_pmem_region
do true; done
- Region now exists in sysfs:
stat -t /sys/bus/cxl/devices/decoder0.0/$region
- Delete the region, and name:
echo $region > /sys/bus/cxl/devices/decoder0.0/delete_region
Signed-off-by: Ben Widawsky <bwidawsk@kernel.org>
Reviewed-by: Jonathan Cameron <Jonathan.Cameron@huawei.com>
Link: https://lore.kernel.org/r/165784333909.1758207.794374602146306032.stgit@dwillia2-xfh.jf.intel.com
[djbw: simplify locking, reword changelog]
Signed-off-by: Dan Williams <dan.j.williams@intel.com>
2021-06-09 01:28:34 +08:00
|
|
|
cxl_core-$(CONFIG_CXL_REGION) += region.o
|
