Implement initial CXL Timeout & Isolation support
Subsystems (3)
cover Implement initial CXL Timeout & Isolation support
Implement initial support for CXL.mem Timeout & Isolation (CXL 3.0 12.3.2). This series implements support for CXL.mem enabling and programming CXL.mem transaction timeout, CXL.mem error isolation, and error isolation interrupts for CXL-enabled PCIe root ports that implement the CXL Timeout & Isolation capability.
I am operating under the assumption that recovery from error isolation will be more involved than just resetting the port and turning off isolation, so that flow is not implemented here. There is also no support for CXL.cache, but I plan to eventually implement both.
The series also introduces a PCIe port bus driver dependency on the CXL core. I expect to be able to remove that when when my team submits patches for a future rework of the PCIe port bus driver.
I have done some testing using QEMU by adding the isolation registers and a hacked-up QMP command to test the interrupt flow, but I *DID NOT* implement the actual isolation feature and the subsequent device behavior. I'd be willing to share these changes (and my config) if anyone is interested in testing this.
Any thoughts/comments would be greatly appreciated!
Ben Cheatham (6):
cxl/core: Add CXL Timeout & Isolation capability parsing pcie/cxl_timeout: Add CXL Timeout & Isolation service driver pcie/cxl_timeout: Add CXL.mem timeout range programming pcie/cxl_timeout: Add CXL.mem error isolation support pcie/portdrv: Add CXL MSI/-X allocation pcie/cxl_timeout: Add CXL.mem Timeout & Isolation interrupt support
drivers/cxl/core/pci.c | 5 + drivers/cxl/core/port.c | 80 +++++ drivers/cxl/core/region.c | 9 + drivers/cxl/core/regs.c | 7 + drivers/cxl/cxl.h | 37 +++ drivers/cxl/cxlpci.h | 9 + drivers/pci/pcie/Kconfig | 10 + drivers/pci/pcie/Makefile | 1 + drivers/pci/pcie/cxl_timeout.c | 592 +++++++++++++++++++++++++++++++++ drivers/pci/pcie/portdrv.c | 36 +- drivers/pci/pcie/portdrv.h | 17 +- 11 files changed, 799 insertions(+), 4 deletions(-) create mode 100644 drivers/pci/pcie/cxl_timeout.c
Signature · 1 line
2.34.1
RFC PATCH 1/6 cxl/core: Add CXL Timeout & Isolation capability parsing
Add parsing and mapping of the CXL Timeout & Isolation capability structure (CXL 3.1 8.2.4.24) to regs.c.
--- drivers/cxl/core/regs.c | 7 +++++++ drivers/cxl/cxl.h | 6 ++++++ 2 files changed, 13 insertions(+)
drivers/cxl/core/regs.c +7 -0
@@ -92,6 +92,12 @@ void cxl_probe_component_regs(struct device *dev, void __iomem *base, length =CXL_RAS_CAPABILITY_LENGTH ; rmap = &map->ras;break ; +case CXL_CM_CAP_CAP_ID_TIMEOUT : +dev_dbg (dev,"found Isolation & Timeout capability (0x%x)\n" , + offset); + length =CXL_TIMEOUT_CAPABILITY_LENGTH ; + rmap = &map->timeout; +break ;default :dev_dbg (dev,"Unknown CM cap ID: %d (0x%x)\n" , cap_id, offset);
@@ -211,6 +217,7 @@ int cxl_map_component_regs(const struct cxl_register_map *map, } mapinfo[] = { { &map->component_map.hdm_decoder, ®s->hdm_decoder }, { &map->component_map.ras, ®s->ras }, + { &map->component_map.timeout, ®s->timeout }, }; int i;
drivers/cxl/cxl.h +6 -0
@@ -36,6 +36,7 @@#define CXL_CM_CAP_CAP_ID_RAS 0x2#define CXL_CM_CAP_CAP_ID_HDM 0x5 +#define CXL_CM_CAP_CAP_ID_TIMEOUT 0x9#define CXL_CM_CAP_CAP_HDM_VERSION 1/* HDM decoders CXL 2.0 8.2.5.12 CXL HDM Decoder Capability Structure */
@@ -126,6 +127,9 @@ static inline int ways_to_eiw(unsigned int ways, u8 *eiw)return 0 ; } +/* CXL 3.0 8.2.4.23 CXL Timeout and Isolation Capability Structure */ +#define CXL_TIMEOUT_CAPABILITY_OFFSET 0x0 +#define CXL_TIMEOUT_CAPABILITY_LENGTH 0x10/* RAS Registers CXL 2.0 8.2.5.9 CXL RAS Capability Structure */ #define CXL_RAS_UNCORRECTABLE_STATUS_OFFSET 0x0#define CXL_RAS_UNCORRECTABLE_STATUS_MASK (GENMASK(16, 14) | GENMASK(11, 0))
@@ -208,6 +212,7 @@ struct cxl_regs {struct_group_tagged (cxl_component_regs, component, void __iomem *hdm_decoder;void __iomem *ras; +void __iomem *timeout; );/* * Common set of CXL Device register block base pointers
@@ -242,6 +247,7 @@ struct cxl_reg_map {struct cxl_component_reg_map {struct cxl_reg_map hdm_decoder;struct cxl_reg_map ras; +struct cxl_reg_map timeout; };struct cxl_device_reg_map {
Signature · 1 line
2.34.1
RFC PATCH 2/6 pcie/cxl_timeout: Add CXL Timeout & Isolation service driver
In reply to Ben CheathamAdd a CXL Timeout & Isolation (CXL 3.0 12.3) service driver to the PCIe port bus driver for CXL root ports. The service will support enabling/programming CXL.mem transaction timeout, error isolation, and interrupt handling.
Add code to find and map CXL Timeout & Isolation capability register (CXL 3.0 8.2.4.23.1) from service driver. Then use capability register mapping to enable CXL.mem transaction timeout with the default value.
--- drivers/cxl/cxl.h | 4 + drivers/pci/pcie/Kconfig | 10 ++ drivers/pci/pcie/Makefile | 1 + drivers/pci/pcie/cxl_timeout.c | 197 +++++++++++++++++++++++++++++++++ drivers/pci/pcie/portdrv.c | 1 + drivers/pci/pcie/portdrv.h | 10 +- 6 files changed, 222 insertions(+), 1 deletion(-) create mode 100644 drivers/pci/pcie/cxl_timeout.c
drivers/cxl/cxl.h +4 -0
@@ -129,7 +129,11 @@ static inline int ways_to_eiw(unsigned int ways, u8 *eiw)/* CXL 3.0 8.2.4.23 CXL Timeout and Isolation Capability Structure */ #define CXL_TIMEOUT_CAPABILITY_OFFSET 0x0 +#define CXL_TIMEOUT_CAP_MEM_TIMEOUT_SUPP BIT(4) +#define CXL_TIMEOUT_CONTROL_OFFSET 0x8 +#define CXL_TIMEOUT_CONTROL_MEM_TIMEOUT_ENABLE BIT(4)#define CXL_TIMEOUT_CAPABILITY_LENGTH 0x10 +/* RAS Registers CXL 2.0 8.2.5.9 CXL RAS Capability Structure */ #define CXL_RAS_UNCORRECTABLE_STATUS_OFFSET 0x0#define CXL_RAS_UNCORRECTABLE_STATUS_MASK (GENMASK(16, 14) | GENMASK(11, 0))
drivers/pci/pcie/Kconfig +10 -0
@@ -58,6 +58,16 @@ config PCIEAER_CXL If unsure, say Y. +config PCIE_CXL_TIMEOUT + bool "PCI Express CXL.mem Timeout & Isolation Interrupt support" + depends on PCIEPORTBUS + depends on CXL_BUS=PCIEPORTBUS && CXL_PORT + help + Enables the CXL.mem Timeout & Isolation PCIE port service driver. This + driver, in combination with the CXL driver core, is responsible for + handling CXL capable PCIE root ports that undergo CXL.mem error isolation + due to either a CXL.mem transaction timeout or uncorrectable device error. + # # PCI Express ECRC #
drivers/pci/pcie/Makefile +1 -0
@@ -13,3 +13,4 @@ obj-$(CONFIG_PCIE_PME) += pme.o obj-$(CONFIG_PCIE_DPC) += dpc.o obj-$(CONFIG_PCIE_PTM) += ptm.o obj-$(CONFIG_PCIE_EDR) += edr.o +obj-$(CONFIG_PCIE_CXL_TIMEOUT) += cxl_timeout.o
drivers/pci/pcie/cxl_timeout.c new file +197 -0
197 lines not on this page · raw message
drivers/pci/pcie/portdrv.c +1 -0
@@ -829,6 +829,7 @@ static void __init pcie_init_services(void)pcie_pme_init ();pcie_dpc_init ();pcie_hp_init (); +pcie_cxlt_init (); }static int __init pcie_portdrv_init (void )
drivers/pci/pcie/portdrv.h +9 -1
@@ -22,8 +22,10 @@#define PCIE_PORT_SERVICE_DPC (1 << PCIE_PORT_SERVICE_DPC_SHIFT)#define PCIE_PORT_SERVICE_BWNOTIF_SHIFT 4/* Bandwidth notification */ #define PCIE_PORT_SERVICE_BWNOTIF (1 << PCIE_PORT_SERVICE_BWNOTIF_SHIFT) +#define PCIE_PORT_SERVICE_CXLT_SHIFT 5/* CXL Timeout & Isolation */ +#define PCIE_PORT_SERVICE_CXLT (1 << PCIE_PORT_SERVICE_CXLT_SHIFT) -#define PCIE_PORT_DEVICE_MAXSERVICES 5 +#define PCIE_PORT_DEVICE_MAXSERVICES 6extern bool pcie_ports_dpc_native;
@@ -51,6 +53,12 @@ int pcie_dpc_init(void);static inline int pcie_dpc_init (void ) {return 0 ; }#endif +#ifdef CONFIG_PCIE_CXL_TIMEOUT +int pcie_cxlt_init (void ); +#else +static inline int pcie_cxlt_init (void ) {return 0 ; } +#endif +/* Port Type */ #define PCIE_ANY_PORT (~0)
Signature · 1 line
2.34.1
Re: [RFC PATCH 2/6] pcie/cxl_timeout: Add CXL Timeout & Isolation service driver
Follow drivers/pci/ subject line convention. Suggest
PCI/CXL: Add CXL Timeout & Isolation service driver
drivers/cxl/cxl.h static inline int ways_to_eiw(unsigned int ways, u8 *eiw) · line 135
Quoted 12 lines · Ben Cheatham
Add a CXL Timeout & Isolation (CXL 3.0 12.3) service driver to the PCIe port bus driver for CXL root ports. The service will support enabling/programming CXL.mem transaction timeout, error isolation, and interrupt handling.
.../* CXL 3.0 8.2.4.23 CXL Timeout and Isolation Capability Structure */ #define
CXL_TIMEOUT_CAPABILITY_OFFSET0x0drivers/cxl/cxl.h +3
-0+#define CXL_TIMEOUT_CAP_MEM_TIMEOUT_SUPP BIT(4) +#define CXL_TIMEOUT_CONTROL_OFFSET 0x8 +#define CXL_TIMEOUT_CONTROL_MEM_TIMEOUT_ENABLE BIT(4)#define CXL_TIMEOUT_CAPABILITY_LENGTH 0x10
Weird lack of alignment makes these #defines hard to read, but kudos for following the local style ;)
Quoted 1 line
/* RAS Registers CXL 2.0 8.2.5.9 CXL RAS Capability Structure */
Update to current CXL spec, please. In r3.0, it looks like this is sec 8.2.4.16. Updating everything to r3.1 references would be even better.
drivers/pci/pcie/Kconfig config PCIEAER_CXL · line 69
Quoted 9 lines
drivers/pci/pcie/Kconfig +9
-0+config PCIE_CXL_TIMEOUT + bool "PCI Express CXL.mem Timeout & Isolation Interrupt support" + depends on PCIEPORTBUS + depends on CXL_BUS=PCIEPORTBUS && CXL_PORT + help + Enables the CXL.mem Timeout & Isolation PCIE port service driver. This + driver, in combination with the CXL driver core, is responsible for + handling CXL capable PCIE root ports that undergo CXL.mem error isolation + due to either a CXL.mem transaction timeout or uncorrectable device error.
When running menuconfig, it seems like both PCIEAER_CXL and PCIE_CXL_TIMEOUT would fit more logically in the drivers/cxl/Kconfig menu along with the rest of the CXL options.
Rewrap to fit in 78 columns.
s/PCIE/PCIe/ (also below)
Quoted 4 lines
+ * Implements CXL Timeout & Isolation (CXL 3.0 12.3.2) interrupt support as a
+ * PCIE port service driver. The driver is set up such that near all of the
+ * work for setting up and handling interrupts are in this file, while the
+ * CXL core enables the interrupts during port enumeration.
Seems like sec 12.3.2 is slightly too specific here. Maybe 12.3?
drivers/pci/pcie/cxl_timeout.c line 31
Quoted 3 lines
drivers/pci/pcie/cxl_timeout.c new file +3
-0+struct pcie_cxlt_data { +struct cxl_timeout *cxlt; +struct cxl_dport *dport;
"dport" is not used here. Would be better to add it in the patch that needs it.
drivers/pci/pcie/cxl_timeout.c line 38
Quoted 5 lines
drivers/pci/pcie/cxl_timeout.c new file +5
-0+static int cxl_map_timeout_regs (struct pci_dev *port, +struct cxl_register_map *map, +struct cxl_component_regs *regs) +{ +int rc =0 ;
Unnecessary initialization.
drivers/pci/pcie/cxl_timeout.c line 104
Quoted 8 lines
drivers/pci/pcie/cxl_timeout.c new file +6
-0+ rc =cxl_find_regblock (port,CXL_REGLOC_RBI_COMPONENT , map); +int cxl_find_timeout_cap (struct pci_dev *dev,u32 *cap) +{ +struct cxl_component_regs regs; +struct cxl_register_map map; +int rc =0 ;
Unnecessary initialization.
drivers/pci/pcie/cxl_timeout.c line 113
Quoted 8 lines
drivers/pci/pcie/cxl_timeout.c new file +8
-0+ rc =cxl_map_timeout_regs (dev, &map, ®s); +if (rc) +return rc; + + *cap =readl (regs.timeout +CXL_TIMEOUT_CAPABILITY_OFFSET ); +cxl_unmap_timeout_regs (dev, &map, ®s); + +return rc;
Since we already know the value:
return 0;
Quoted 1 line
+}
Move cxl_find_timeout_cap() to the patch that needs it. It's unused in this one.
drivers/pci/pcie/cxl_timeout.c line 162
Quoted 6 lines
drivers/pci/pcie/cxl_timeout.c new file +6
-0+static int cxl_timeout_probe (struct pcie_device *dev) +{ +struct pci_dev *port = dev->port; +struct pcie_cxlt_data *pdata; +struct cxl_timeout *cxlt; +int rc =0 ;
Unnecessary initialization.
Quoted 6 lines
drivers/pci/pcie/cxl_timeout.c new file +6
-0+/* Limit to CXL root ports */ +if (!pci_find_dvsec_capability (port,PCI_DVSEC_VENDOR_ID_CXL , +CXL_DVSEC_PORT_EXTENSIONS )) +return -ENODEV ; + + pdata =cxlt_create_pdata (dev);
drivers/pci/pcie/cxl_timeout.c line 179
Quoted 10 lines
drivers/pci/pcie/cxl_timeout.c new file +10
-0+if (IS_ERR_OR_NULL (pdata)) +return PTR_ERR (pdata); + +set_service_data (dev, pdata); + cxlt = pdata->cxlt; + + rc =cxl_enable_timeout (dev, cxlt); +if (rc) +pci_dbg (dev->port,"Failed to enable CXL.mem timeout: %d\n" , + rc);
"(%pe)" (similar in subsequent patches)
drivers/pci/pcie/cxl_timeout.c static void __init pcie_init_services(void) · line 832
Quoted 9 lines
drivers/pci/pcie/cxl_timeout.c new file +4
-0+return rc; +} +@@ -829,6 +829,7 @@ static void __init pcie_init_services(void)pcie_pme_init ();pcie_dpc_init ();pcie_hp_init (); +pcie_cxlt_init ();
"cxlt" seems slightly too generic outside cxl_timeout.c, since there might be other CXL things that start with "t" someday.
drivers/pci/pcie/portdrv.h line 26
Quoted 2 lines
drivers/pci/pcie/portdrv.h +2
-0+#define PCIE_PORT_SERVICE_CXLT_SHIFT 5/* CXL Timeout & Isolation */ +#define PCIE_PORT_SERVICE_CXLT (1 << PCIE_PORT_SERVICE_CXLT_SHIFT)
I hate having to add this to the portdrv, but I see why you need to (so we can deal with the weirdness of PCIe feature interrupts).
Bjorn
Re: [RFC PATCH 2/6] pcie/cxl_timeout: Add CXL Timeout & Isolation service driver
Hi Bjorn, thanks for the comments! Responses inline.
Quoted 21 lines · Bjorn Helgaas
Follow
drivers/pci/subject line convention. SuggestPCI/CXL: Add CXL Timeout & Isolation service driver
drivers/cxl/cxl.h static inline int ways_to_eiw(unsigned int ways, u8 *eiw) · line 135
Quoted 12 lines · Ben Cheatham
Add a CXL Timeout & Isolation (CXL 3.0 12.3) service driver to the PCIe port bus driver for CXL root ports. The service will support enabling/programming CXL.mem transaction timeout, error isolation, and interrupt handling.
.../* CXL 3.0 8.2.4.23 CXL Timeout and Isolation Capability Structure */ #define
CXL_TIMEOUT_CAPABILITY_OFFSET0x0drivers/cxl/cxl.h +3
-0+#define CXL_TIMEOUT_CAP_MEM_TIMEOUT_SUPP BIT(4) +#define CXL_TIMEOUT_CONTROL_OFFSET 0x8 +#define CXL_TIMEOUT_CONTROL_MEM_TIMEOUT_ENABLE BIT(4)#define CXL_TIMEOUT_CAPABILITY_LENGTH 0x10Weird lack of alignment makes these #defines hard to read, but kudos for following the local style ;)
Quoted 6 lines
Quoted 1 line
/* RAS Registers CXL 2.0 8.2.5.9 CXL RAS Capability Structure */
Update to current CXL spec, please. In r3.0, it looks like this is sec 8.2.4.16. Updating everything to r3.1 references would be even better.
Yeah a lot of the spec references in cxl.h are out of date, I'll update them where I touch them. And I didn't realize 3.1 was out yet, I'll update the references to that revision as well.
Quoted 5 lines
Quoted 5 lines
drivers/pci/pcie/Kconfig +5
-0+config PCIE_CXL_TIMEOUT + bool "PCI Express CXL.mem Timeout & Isolation Interrupt support" + depends on PCIEPORTBUS + depends on CXL_BUS=PCIEPORTBUS && CXL_PORT + help
Quoted 9 lines
drivers/pci/pcie/Kconfig config PCIEAER_CXL · line 69
Quoted 4 lines
drivers/pci/pcie/Kconfig +4
-0+ Enables the CXL.mem Timeout & Isolation PCIE port service driver. This + driver, in combination with the CXL driver core, is responsible for + handling CXL capable PCIE root ports that undergo CXL.mem error isolation + due to either a CXL.mem transaction timeout or uncorrectable device error.When running menuconfig, it seems like both
PCIEAER_CXLandPCIE_CXL_TIMEOUTwould fit more logically in thedrivers/cxl/Kconfigmenu along with the rest of the CXL options.
Will do.
Quoted 4 lines
Rewrap to fit in 78 columns.
s/PCIE/PCIe/ (also below)
Will do both above.
Quoted 7 lines
Quoted 4 lines
+ * Implements CXL Timeout & Isolation (CXL 3.0 12.3.2) interrupt support as a
+ * PCIE port service driver. The driver is set up such that near all of the
+ * work for setting up and handling interrupts are in this file, while the
+ * CXL core enables the interrupts during port enumeration.Seems like sec 12.3.2 is slightly too specific here. Maybe 12.3?
12.3.2 is the CXL.mem portion of the section, which is the only section implemented in the patch set. That being said, I don't mind changing it to 12.3 instead.
Quoted 7 lines
drivers/pci/pcie/cxl_timeout.c line 31
Quoted 3 lines
drivers/pci/pcie/cxl_timeout.c new file +3
-0+struct pcie_cxlt_data { +struct cxl_timeout *cxlt; +struct cxl_dport *dport;"dport" is not used here. Would be better to add it in the patch that needs it.
Will do.
Quoted 30 lines
drivers/pci/pcie/cxl_timeout.c line 38
Quoted 5 lines
drivers/pci/pcie/cxl_timeout.c new file +5
-0+static int cxl_map_timeout_regs (struct pci_dev *port, +struct cxl_register_map *map, +struct cxl_component_regs *regs) +{ +int rc =0 ;Unnecessary initialization.
drivers/pci/pcie/cxl_timeout.c line 104
Quoted 8 lines
drivers/pci/pcie/cxl_timeout.c new file +6
-0+ rc =cxl_find_regblock (port,CXL_REGLOC_RBI_COMPONENT , map); +int cxl_find_timeout_cap (struct pci_dev *dev,u32 *cap) +{ +struct cxl_component_regs regs; +struct cxl_register_map map; +int rc =0 ;Unnecessary initialization.
drivers/pci/pcie/cxl_timeout.c line 113
Quoted 8 lines
drivers/pci/pcie/cxl_timeout.c new file +8
-0+ rc =cxl_map_timeout_regs (dev, &map, ®s); +if (rc) +return rc; + + *cap =readl (regs.timeout +CXL_TIMEOUT_CAPABILITY_OFFSET ); +cxl_unmap_timeout_regs (dev, &map, ®s); + +return rc;Since we already know the value:
Quoted 7 lines
return 0;
Quoted 1 line
+}
Move
cxl_find_timeout_cap()to the patch that needs it. It's unused in this one.
Will do to all 4 above.
Quoted 19 lines
drivers/pci/pcie/cxl_timeout.c line 162
Quoted 6 lines
drivers/pci/pcie/cxl_timeout.c new file +6
-0+static int cxl_timeout_probe (struct pcie_device *dev) +{ +struct pci_dev *port = dev->port; +struct pcie_cxlt_data *pdata; +struct cxl_timeout *cxlt; +int rc =0 ;Unnecessary initialization.
Quoted 10 lines
drivers/pci/pcie/cxl_timeout.c new file +10
-0+/* Limit to CXL root ports */ +if (!pci_find_dvsec_capability (port,PCI_DVSEC_VENDOR_ID_CXL , +CXL_DVSEC_PORT_EXTENSIONS )) +return -ENODEV ; + + pdata =cxlt_create_pdata (dev); +if (IS_ERR_OR_NULL (pdata)) +return PTR_ERR (pdata); + +set_service_data (dev, pdata);
Quoted 9 lines
drivers/pci/pcie/cxl_timeout.c line 179
Quoted 6 lines
drivers/pci/pcie/cxl_timeout.c new file +6
-0+ cxlt = pdata->cxlt; + + rc =cxl_enable_timeout (dev, cxlt); +if (rc) +pci_dbg (dev->port,"Failed to enable CXL.mem timeout: %d\n" , + rc);"(%pe)" (similar in subsequent patches)
I wasn't aware of that, I'll change it.
Quoted 20 lines
drivers/pci/pcie/cxl_timeout.c static void __init pcie_init_services(void) · line 832
Quoted 9 lines
drivers/pci/pcie/cxl_timeout.c new file +4
-0+return rc; +} +@@ -829,6 +829,7 @@ static void __init pcie_init_services(void)pcie_pme_init ();pcie_dpc_init ();pcie_hp_init (); +pcie_cxlt_init ();"cxlt" seems slightly too generic outside
cxl_timeout.c, since there might be other CXL things that start with "t" someday.drivers/pci/pcie/portdrv.h line 26
Quoted 2 lines
drivers/pci/pcie/portdrv.h +2
-0+#define PCIE_PORT_SERVICE_CXLT_SHIFT 5/* CXL Timeout & Isolation */ +#define PCIE_PORT_SERVICE_CXLT (1 << PCIE_PORT_SERVICE_CXLT_SHIFT)I hate having to add this to the portdrv, but I see why you need to (so we can deal with the weirdness of PCIe feature interrupts).
Bjorn
Re: [RFC PATCH 2/6] pcie/cxl_timeout: Add CXL Timeout & Isolation service driver
Quoted 11 lines · Ben Cheatham
Quoted 7 lines · Bjorn Helgaas
drivers/pci/pcie/cxl_timeout.c line 179
Quoted 4 lines
drivers/pci/pcie/cxl_timeout.c new file +4
-0+ rc =cxl_enable_timeout (dev, cxlt); +if (rc) +pci_dbg (dev->port,"Failed to enable CXL.mem timeout: %d\n" , + rc);"(%pe)" (similar in subsequent patches)
I wasn't aware of that, I'll change it.
I wasn't either, but I'm getting patches to change them, and it does seem a little bit easier than looking up the errnos when debugging, so ...
RFC PATCH 3/6 pcie/cxl_timeout: Add CXL.mem timeout range programming
In reply to Ben CheathamAdd programming of CXL.mem transaction timeout range (CXL 3.0 8.2.4.23.1 bits 4 & 11:8) through sysfs. To program the device, read the ranges supported from "available_timeout_ranges" in the PCIe service device directory, then write the desired value to "timeout_range". The current value can be found by reading from "timeout_range".
Example for CXL-enabled PCIe port 0000:0c:00.0, with CXL timeout service as 020:
# cd /sys/bus/pci_express/devices/0000:0c:00.0:pcie020 # cat available_timeout_ranges 0x0 Default range (50us-10ms) 0x1 Range A (50us-100us) 0x2 Range A (1ms-10ms) # cat timeout_range 0 # echo 0x2 > timeout_range # cat timeout_range 2
--- drivers/cxl/cxl.h | 13 +++ drivers/pci/pcie/cxl_timeout.c | 185 +++++++++++++++++++++++++++++++++ 2 files changed, 198 insertions(+)
drivers/cxl/cxl.h +13 -0
@@ -129,11 +129,24 @@ static inline int ways_to_eiw(unsigned int ways, u8 *eiw)/* CXL 3.0 8.2.4.23 CXL Timeout and Isolation Capability Structure */ #define CXL_TIMEOUT_CAPABILITY_OFFSET 0x0 +#define CXL_TIMEOUT_CAP_MEM_TIMEOUT_MASK GENMASK(3, 0)#define CXL_TIMEOUT_CAP_MEM_TIMEOUT_SUPP BIT(4)#define CXL_TIMEOUT_CONTROL_OFFSET 0x8 +#define CXL_TIMEOUT_CONTROL_MEM_TIMEOUT_MASK GENMASK(3, 0)#define CXL_TIMEOUT_CONTROL_MEM_TIMEOUT_ENABLE BIT(4)#define CXL_TIMEOUT_CAPABILITY_LENGTH 0x10 +/* CXL 3.0 8.2.4.23.2 CXL Timeout and Isolation Control Register, bits 3:0 */ +#define CXL_TIMEOUT_TIMEOUT_RANGE_DEFAULT 0x0 +#define CXL_TIMEOUT_TIMEOUT_RANGE_A1 0x1 +#define CXL_TIMEOUT_TIMEOUT_RANGE_A2 0x2 +#define CXL_TIMEOUT_TIMEOUT_RANGE_B1 0x5 +#define CXL_TIMEOUT_TIMEOUT_RANGE_B2 0x6 +#define CXL_TIMEOUT_TIMEOUT_RANGE_C1 0x9 +#define CXL_TIMEOUT_TIMEOUT_RANGE_C2 0xA +#define CXL_TIMEOUT_TIMEOUT_RANGE_D1 0xD +#define CXL_TIMEOUT_TIMEOUT_RANGE_D2 0xE +/* RAS Registers CXL 2.0 8.2.5.9 CXL RAS Capability Structure */ #define CXL_RAS_UNCORRECTABLE_STATUS_OFFSET 0x0#define CXL_RAS_UNCORRECTABLE_STATUS_MASK (GENMASK(16, 14) | GENMASK(11, 0))
drivers/pci/pcie/cxl_timeout.c +185 -0
209 lines not on this page · raw message
Signature · 1 line
2.34.1
Re: [RFC PATCH 3/6] pcie/cxl_timeout: Add CXL.mem timeout range programming
Quoted 9 lines · Ben Cheatham
Add programming of CXL.mem transaction timeout range (CXL 3.0 8.2.4.23.1 bits 4 & 11:8) through sysfs. To program the device, read the ranges supported from "
available_timeout_ranges" in the PCIe service device directory, then write the desired value to "timeout_range". The current value can be found by reading from "timeout_range".Example for CXL-enabled PCIe port 0000:0c:00.0, with CXL timeout service as 020:
# cd /sys/bus/pci_express/devices/0000:0c:00.0:pcie020
I would really, really like to avoid adding sysfs dependences on portdrv. Is there any chance these files could go in the normal /sys/bus/pci/devices/ hierarchy instead?
drivers/cxl/cxl.h static inline int ways_to_eiw(unsigned int ways, u8 *eiw) · line 148
Quoted 4 lines
drivers/cxl/cxl.h +3
-0+/* CXL 3.0 8.2.4.23.2 CXL Timeout and Isolation Control Register, bits 3:0 */ +#define CXL_TIMEOUT_TIMEOUT_RANGE_DEFAULT 0x0 +#define CXL_TIMEOUT_TIMEOUT_RANGE_D2 0xE
Looks like the single other example in this file of hex constants using A-F uses lower-case.
Does "TIMEOUT_TIMEOUT" add information over just "TIMEOUT"?
Quoted 1 line
+#define
NUM_CXL_TIMEOUT_RANGES9
I don't think we actually need this constant, do we?
Quoted 1 line
+static bool
cxl_validate_timeout_range(struct cxl_timeout *cxlt, u8 range)
"validate" is not a very name for a function returning "bool" because you can't tell what true/false means from the name. "valid" would be fine.
drivers/pci/pcie/cxl_timeout.c static struct pcie_cxlt_data *cxlt_create_pdata(struct pcie_device *dev) · line 182
Quoted 2 lines
drivers/pci/pcie/cxl_timeout.c +2
-0+pci_dbg (cxlt->dev->port, +"Timeout & isolation timeout set to range 0x%x\n" , range);
I don't know CXL, but "timeout ... timeout" reads sort of strange. Is it actually a timeout for a timeout? Maybe it was supposed to be "transaction timeout"?
drivers/pci/pcie/cxl_timeout.c static int cxl_enable_timeout(struct pcie_device *dev, struct cxl_timeout *cxlt) · line 253
Quoted 4 lines
drivers/pci/pcie/cxl_timeout.c +4
-0+const struct cxl_timeout_range { +const char *str; +u8 range_val; +} cxl_timeout_ranges[NUM_CXL_TIMEOUT_RANGES ] = {
Static?
Bjorn
Re: [RFC PATCH 3/6] pcie/cxl_timeout: Add CXL.mem timeout range programming
Quoted 7 lines · Bjorn Helgaas
Quoted 6 lines · Ben Cheatham
Add programming of CXL.mem transaction timeout range (CXL 3.0 8.2.4.23.1 bits 4 & 11:8) through sysfs. To program the device, read the ranges supported from "
available_timeout_ranges" in the PCIe service device directory, then write the desired value to "timeout_range". The current value can be found by reading from "timeout_range".
Quoted 8 lines
Quoted 3 lines
Example for CXL-enabled PCIe port 0000:0c:00.0, with CXL timeout service as 020:
# cd /sys/bus/pci_express/devices/0000:0c:00.0:pcie020I would really, really like to avoid adding sysfs dependences on portdrv. Is there any chance these files could go in the normal
/sys/bus/pci/devices/hierarchy instead?
This was just the first place I tried putting it that seemed ok. I'll take a look at moving them over to pci/devices instead.
Quoted 10 lines
drivers/cxl/cxl.h static inline int ways_to_eiw(unsigned int ways, u8 *eiw) · line 148
Quoted 4 lines
drivers/cxl/cxl.h +3
-0+/* CXL 3.0 8.2.4.23.2 CXL Timeout and Isolation Control Register, bits 3:0 */ +#define CXL_TIMEOUT_TIMEOUT_RANGE_DEFAULT 0x0 +#define CXL_TIMEOUT_TIMEOUT_RANGE_D2 0xELooks like the single other example in this file of hex constants using A-F uses lower-case.
Does "
TIMEOUT_TIMEOUT" add information over just "TIMEOUT"?
TIMEOUT_TIMEOUT is supposed to specify transaction timeout, but I'll agree it is confusing. I could try changing to CXL_TRANSACTION_TIMEOUT_RANGE_* instead, but it would break the convention of CXL timeout & isolation defines starting with CXL_TIMEOUT.
Quoted 4 lines
Quoted 1 line
+#define
NUM_CXL_TIMEOUT_RANGES9I don't think we actually need this constant, do we?
Not really, just gets rid of a magic number (as well as makes sure anyone who changes that array remembers to update the array size).
Quoted 6 lines
Quoted 1 line
+static bool
cxl_validate_timeout_range(struct cxl_timeout *cxlt, u8 range)"validate" is not a very name for a function returning "bool" because you can't tell what true/false means from the name. "valid" would be fine.
Will change.
Quoted 7 lines
drivers/pci/pcie/cxl_timeout.c static struct pcie_cxlt_data *cxlt_create_pdata(struct pcie_device *dev) · line 182
Quoted 2 lines
drivers/pci/pcie/cxl_timeout.c +2
-0+pci_dbg (cxlt->dev->port, +"Timeout & isolation timeout set to range 0x%x\n" , range);I don't know CXL, but "timeout ... timeout" reads sort of strange. Is it actually a timeout for a timeout? Maybe it was supposed to be "transaction timeout"?
Yeah it's the same as above. I'll change it to "Timeout & isolation transaction timeout ..." instead.
Quoted 7 lines
drivers/pci/pcie/cxl_timeout.c static int cxl_enable_timeout(struct pcie_device *dev, struct cxl_timeout *cxlt) · line 253
Quoted 4 lines
drivers/pci/pcie/cxl_timeout.c +4
-0+const struct cxl_timeout_range { +const char *str; +u8 range_val; +} cxl_timeout_ranges[NUM_CXL_TIMEOUT_RANGES ] = {Static?
Yep, I'll change it.
Quoted 2 lines
Bjorn
Re: [RFC PATCH 3/6] pcie/cxl_timeout: Add CXL.mem timeout range programming
Quoted 9 lines · Ben Cheatham
Quoted 5 lines · Bjorn Helgaas
Quoted 1 line · Ben Cheatham
+#define
NUM_CXL_TIMEOUT_RANGES9I don't think we actually need this constant, do we?
Not really, just gets rid of a magic number (as well as makes sure anyone who changes that array remembers to update the array size).
My point was that I don't think you need to specify the size of the array at all since it's initialized, and you already use ARRAY_SIZE() elsewhere.
Re: [RFC PATCH 3/6] pcie/cxl_timeout: Add CXL.mem timeout range programming
Quoted 6 lines · Bjorn Helgaas
Quoted 5 lines · Ben Cheatham
Quoted 4 lines · Bjorn Helgaas
Quoted 1 line · Ben Cheatham
+#define
NUM_CXL_TIMEOUT_RANGES9
Quoted 9 lines
Quoted 4 lines
Quoted 1 line
I don't think we actually need this constant, do we?
Not really, just gets rid of a magic number (as well as makes sure anyone who changes that array remembers to update the array size).
My point was that I don't think you need to specify the size of the array at all since it's initialized, and you already use
ARRAY_SIZE()elsewhere.
Sorry about that, I just completely misinterpreted that. I agree, I'll remove it.
Thanks,
Ben
RFC PATCH 4/6 pcie/cxl_timeout: Add CXL.mem error isolation support
In reply to Ben CheathamAdd and enable CXL.mem error isolation support (CXL 3.0 12.3.2) to the CXL Timeout & Isolation service driver.
--- drivers/cxl/cxl.h | 2 ++ drivers/pci/pcie/cxl_timeout.c | 40 +++++++++++++++++++++++++++++++++- 2 files changed, 41 insertions(+), 1 deletion(-)
drivers/cxl/cxl.h +2 -0
@@ -131,9 +131,11 @@ static inline int ways_to_eiw(unsigned int ways, u8 *eiw)#define CXL_TIMEOUT_CAPABILITY_OFFSET 0x0#define CXL_TIMEOUT_CAP_MEM_TIMEOUT_MASK GENMASK(3, 0)#define CXL_TIMEOUT_CAP_MEM_TIMEOUT_SUPP BIT(4) +#define CXL_TIMEOUT_CAP_MEM_ISO_SUPP BIT(16)#define CXL_TIMEOUT_CONTROL_OFFSET 0x8#define CXL_TIMEOUT_CONTROL_MEM_TIMEOUT_MASK GENMASK(3, 0)#define CXL_TIMEOUT_CONTROL_MEM_TIMEOUT_ENABLE BIT(4) +#define CXL_TIMEOUT_CONTROL_MEM_ISO_ENABLE BIT(16)#define CXL_TIMEOUT_CAPABILITY_LENGTH 0x10/* CXL 3.0 8.2.4.23.2 CXL Timeout and Isolation Control Register, bits 3:0 */
drivers/pci/pcie/cxl_timeout.c +39 -1
@@ -207,6 +207,31 @@ static int cxl_enable_timeout(struct pcie_device *dev, struct cxl_timeout *cxlt) cxlt); } +static void cxl_disable_isolation (void *data) +{ +struct cxl_timeout *cxlt = data; +u32 cntrl =readl (cxlt->regs +CXL_TIMEOUT_CONTROL_OFFSET ); + + cntrl &= ~CXL_TIMEOUT_CONTROL_MEM_ISO_ENABLE ; +writel (cntrl, cxlt->regs +CXL_TIMEOUT_CONTROL_OFFSET ); +} + +static int cxl_enable_isolation (struct pcie_device *dev, +struct cxl_timeout *cxlt) +{ +u32 cntrl; + +if (!cxlt || !FIELD_GET (CXL_TIMEOUT_CAP_MEM_ISO_SUPP , cxlt->cap)) +return -ENXIO ; + + cntrl =readl (cxlt->regs +CXL_TIMEOUT_CONTROL_OFFSET ); + cntrl |=CXL_TIMEOUT_CONTROL_MEM_ISO_ENABLE ; +writel (cntrl, cxlt->regs +CXL_TIMEOUT_CONTROL_OFFSET ); + +return devm_add_action_or_reset (&dev->device, cxl_disable_isolation, + cxlt); +} +static ssize_t timeout_range_show (struct device *dev,struct device_attribute *attr,char *buf)
@@ -341,7 +366,8 @@ static int cxl_timeout_probe(struct pcie_device *dev)struct pci_dev *port = dev->port;struct pcie_cxlt_data *pdata;struct cxl_timeout *cxlt; -int rc =0 ; +bool timeout_enabled; +int rc;/* Limit to CXL root ports */ if (!pci_find_dvsec_capability(port, PCI_DVSEC_VENDOR_ID_CXL,
@@ -360,6 +386,18 @@ static int cxl_timeout_probe(struct pcie_device *dev)pci_dbg (dev->port,"Failed to enable CXL.mem timeout: %d\n" , rc); + timeout_enabled = !rc; + + rc =cxl_enable_isolation (dev, cxlt); +if (rc) +pci_dbg (dev->port,"Failed to enable CXL.mem isolation: %d\n" , + rc); + +if (rc && !timeout_enabled) { +pci_info (dev->port, +"Failed to enable CXL.mem timeout and isolation.\n" ); + } +return rc; }
Signature · 1 line
2.34.1
Re: [RFC PATCH 4/6] pcie/cxl_timeout: Add CXL.mem error isolation support
Quoted 14 lines · Ben Cheatham
Add and enable CXL.mem error isolation support (CXL 3.0 12.3.2) to the CXL Timeout & Isolation service driver.
drivers/pci/pcie/cxl_timeout.c +2
-1@@ -341,7 +366,8 @@ static int cxl_timeout_probe(struct pcie_device *dev)struct pci_dev *port = dev->port;struct pcie_cxlt_data *pdata;struct cxl_timeout *cxlt; -int rc =0 ; +bool timeout_enabled; +int rc;/* Limit to CXL root ports */ if (!pci_find_dvsec_capability(port, PCI_DVSEC_VENDOR_ID_CXL,
drivers/pci/pcie/cxl_timeout.c static int cxl_timeout_probe(struct pcie_device *dev) · line 389
Quoted 4 lines
drivers/pci/pcie/cxl_timeout.c +1
-0@@ -360,6 +386,18 @@ static int cxl_timeout_probe(struct pcie_device *dev)pci_dbg (dev->port,"Failed to enable CXL.mem timeout: %d\n" , rc); + timeout_enabled = !rc;
This ends up being a little weird: mixing int and bool, negating rc here and then negating timeout_enabled later, several messages.
Maybe could just keep rc1 and rc2, drop the pci_dbg messages and enhance the "enabled" message to be something like:
"enabled %s%s with IRQ", rc1 ? "" : "timeout", rc2 ? "" : "isolation" ("&" left for your imagination).
Or something like
#define FLAG(x) ((x) ? '-' : '+')
"CXL.mem timeout%c isolation%c enabled with IRQ %d", FLAG(rc1), FLAG(rc2)
drivers/pci/pcie/cxl_timeout.c static int cxl_timeout_probe(struct pcie_device *dev) · line 394
Quoted 5 lines
drivers/pci/pcie/cxl_timeout.c +4
-0+ rc =cxl_enable_isolation (dev, cxlt); +if (rc) +pci_dbg (dev->port,"Failed to enable CXL.mem isolation: %d\n" , + rc);
"(%pe)"
drivers/pci/pcie/cxl_timeout.c static int cxl_timeout_probe(struct pcie_device *dev) · line 398
Quoted 3 lines
drivers/pci/pcie/cxl_timeout.c +3
-0+if (rc && !timeout_enabled) { +pci_info (dev->port, +"Failed to enable CXL.mem timeout and isolation.\n" );
Most messages don't include a period at end. It just adds the chance for line wrapping unnecessarily.
Re: [RFC PATCH 4/6] pcie/cxl_timeout: Add CXL.mem error isolation support
Quoted 23 lines · Bjorn Helgaas
Quoted 14 lines · Ben Cheatham
Add and enable CXL.mem error isolation support (CXL 3.0 12.3.2) to the CXL Timeout & Isolation service driver.
drivers/pci/pcie/cxl_timeout.c +2
-1@@ -341,7 +366,8 @@ static int cxl_timeout_probe(struct pcie_device *dev)struct pci_dev *port = dev->port;struct pcie_cxlt_data *pdata;struct cxl_timeout *cxlt; -int rc =0 ; +bool timeout_enabled; +int rc;/* Limit to CXL root ports */ if (!pci_find_dvsec_capability(port, PCI_DVSEC_VENDOR_ID_CXL,drivers/pci/pcie/cxl_timeout.c static int cxl_timeout_probe(struct pcie_device *dev) · line 389
Quoted 4 lines
drivers/pci/pcie/cxl_timeout.c +1
-0@@ -360,6 +386,18 @@ static int cxl_timeout_probe(struct pcie_device *dev)pci_dbg (dev->port,"Failed to enable CXL.mem timeout: %d\n" , rc); + timeout_enabled = !rc;This ends up being a little weird: mixing int and bool, negating rc here and then negating
timeout_enabledlater, several messages.
Quoted 9 lines
Maybe could just keep rc1 and rc2, drop the
pci_dbgmessages and enhance the "enabled" message to be something like:
"enabled %s%s with IRQ", rc1 ? "" : "timeout", rc2 ? "" : "isolation" ("&" left for your imagination).Or something like
#define FLAG(x) ((x) ? '-' : '+')
"CXL.mem timeout%c isolation%c enabled with IRQ %d", FLAG(rc1), FLAG(rc2)
I thought it was janky as well. I tried something really quick using ternaries and it looked weirder :/. But I agree with you here, I'll take another stab at it.
Quoted 8 lines
drivers/pci/pcie/cxl_timeout.c static int cxl_timeout_probe(struct pcie_device *dev) · line 394
Quoted 5 lines
drivers/pci/pcie/cxl_timeout.c +4
-0+ rc =cxl_enable_isolation (dev, cxlt); +if (rc) +pci_dbg (dev->port,"Failed to enable CXL.mem isolation: %d\n" , + rc);"(%pe)"
Quoted 7 lines
drivers/pci/pcie/cxl_timeout.c static int cxl_timeout_probe(struct pcie_device *dev) · line 398
Quoted 3 lines
drivers/pci/pcie/cxl_timeout.c +3
-0+if (rc && !timeout_enabled) { +pci_info (dev->port, +"Failed to enable CXL.mem timeout and isolation.\n" );Most messages don't include a period at end. It just adds the chance for line wrapping unnecessarily.
I'll remove them.
RFC PATCH 5/6 pcie/portdrv: Add CXL MSI/-X allocation
In reply to Ben CheathamAllocate an MSI/-X for CXL-enabled PCIe root ports that support timeout & isolation interrupts. This vector will be used by the CXL timeout & isolation service driver to disable the root port in the CXL port hierarchy and any associated memory if the port enters isolation.
--- drivers/cxl/cxl.h | 2 ++ drivers/pci/pcie/cxl_timeout.c | 11 ++++++++++- drivers/pci/pcie/portdrv.c | 35 +++++++++++++++++++++++++++++++--- drivers/pci/pcie/portdrv.h | 6 ++++++ 4 files changed, 50 insertions(+), 4 deletions(-)
drivers/cxl/cxl.h +2 -0
@@ -132,6 +132,8 @@ static inline int ways_to_eiw(unsigned int ways, u8 *eiw)#define CXL_TIMEOUT_CAP_MEM_TIMEOUT_MASK GENMASK(3, 0)#define CXL_TIMEOUT_CAP_MEM_TIMEOUT_SUPP BIT(4)#define CXL_TIMEOUT_CAP_MEM_ISO_SUPP BIT(16) +#define CXL_TIMEOUT_CAP_INTR_SUPP BIT(26) +#define CXL_TIMEOUT_CAP_INTR_MASK GENMASK(31, 27)#define CXL_TIMEOUT_CONTROL_OFFSET 0x8#define CXL_TIMEOUT_CONTROL_MEM_TIMEOUT_MASK GENMASK(3, 0)#define CXL_TIMEOUT_CONTROL_MEM_TIMEOUT_ENABLE BIT(4)
drivers/pci/pcie/cxl_timeout.c +10 -1
@@ -99,7 +99,7 @@ static struct cxl_timeout *cxl_create_cxlt(struct pcie_device *dev)return ERR_PTR (rc); } -int cxl_find_timeout_cap (struct pci_dev *dev,u32 *cap) +int pcie_cxl_find_timeout_cap (struct pci_dev *dev,u32 *cap) {struct cxl_component_regs regs;struct cxl_register_map map;
@@ -115,6 +115,15 @@ int cxl_find_timeout_cap(struct pci_dev *dev, u32 *cap)return rc; } +bool pcie_supports_cxl_timeout_interrupts (u32 cap) +{ +if (!(cap &CXL_TIMEOUT_CAP_INTR_SUPP )) +return false; + +return (cap &CXL_TIMEOUT_CAP_MEM_ISO_SUPP ) || + (cap &CXL_TIMEOUT_CAP_MEM_TIMEOUT_SUPP ); +} +static struct pcie_cxlt_data *cxlt_create_pdata (struct pcie_device *dev) {struct pcie_cxlt_data *data;
drivers/pci/pcie/portdrv.c +32 -3
@@ -21,6 +21,7 @@#include "../pci.h" #include "portdrv.h" +#include "../../cxl/cxlpci.h" /* * The PCIe Capability Interrupt Message Number (PCIe r3.1, sec 7.8.2) must
@@ -55,7 +56,7 @@ static void release_pcie_device(struct device *dev)* required to accommodate the largest Message Number. */ static int pcie_message_numbers (struct pci_dev *dev,int mask, -u32 *pme,u32 *aer,u32 *dpc) +u32 *pme,u32 *aer,u32 *dpc,u32 *cxl) {u32 nvec =0 , pos;u16 reg16;
@@ -98,6 +99,19 @@ static int pcie_message_numbers(struct pci_dev *dev, int mask, } } +#ifdef CONFIG_PCIE_CXL_TIMEOUT +if (mask &PCIE_PORT_SERVICE_CXLT ) { +u32 cap; + +if (!pcie_cxl_find_timeout_cap (dev, &cap) && +pcie_supports_cxl_timeout_interrupts (cap)) { + *cxl =FIELD_GET (CXL_TIMEOUT_CAP_INTR_MASK , + pos); + nvec =max (nvec, *cxl +1 ); + } + } +#endif +return nvec; }
@@ -113,7 +127,7 @@ static int pcie_message_numbers(struct pci_dev *dev, int mask,static int pcie_port_enable_irq_vec (struct pci_dev *dev,int *irqs,int mask) {int nr_entries, nvec, pcie_irq; -u32 pme =0 , aer =0 , dpc =0 ; +u32 pme =0 , aer =0 , dpc =0 , cxlt =0 ;/* Allocate the maximum possible number of MSI/MSI-X vectors */ nr_entries = pci_alloc_irq_vectors(dev, 1, PCIE_PORT_MAX_MSI_ENTRIES,
@@ -122,7 +136,7 @@ static int pcie_port_enable_irq_vec(struct pci_dev *dev, int *irqs, int mask)return nr_entries;/* See how many and which Interrupt Message Numbers we actually use */ - nvec =pcie_message_numbers (dev, mask, &pme, &aer, &dpc); + nvec =pcie_message_numbers (dev, mask, &pme, &aer, &dpc, &cxlt);if (nvec > nr_entries) {pci_free_irq_vectors (dev);return -EIO ;
@@ -163,6 +177,9 @@ static int pcie_port_enable_irq_vec(struct pci_dev *dev, int *irqs, int mask)if (mask &PCIE_PORT_SERVICE_DPC ) irqs[PCIE_PORT_SERVICE_DPC_SHIFT ] =pci_irq_vector (dev, dpc); +if (mask &PCIE_PORT_SERVICE_CXLT ) + irqs[PCIE_PORT_SERVICE_CXLT_SHIFT ] =pci_irq_vector (dev, cxlt); +return 0 ; }
@@ -274,6 +291,18 @@ static int get_port_device_capability(struct pci_dev *dev) services |=PCIE_PORT_SERVICE_BWNOTIF ; } +#ifdef CONFIG_PCIE_CXL_TIMEOUT +if (pci_pcie_type (dev) ==PCI_EXP_TYPE_ROOT_PORT && +pci_find_dvsec_capability (dev,PCI_DVSEC_VENDOR_ID_CXL , +CXL_DVSEC_PORT_EXTENSIONS )) { +u32 cap; + +if (!pcie_cxl_find_timeout_cap (dev, &cap) && +pcie_supports_cxl_timeout_interrupts (cap)) + services |=PCIE_PORT_SERVICE_CXLT ; + } +#endif +return services; }
drivers/pci/pcie/portdrv.h +6 -0
@@ -129,4 +129,10 @@ static inline void pcie_pme_interrupt_enable(struct pci_dev *dev, bool en) {}#endif /* !CONFIG_PCIE_PME */ struct device *pcie_port_find_device (struct pci_dev *dev,u32 service); + +#ifdef CONFIG_PCIE_CXL_TIMEOUT +int pcie_cxl_find_timeout_cap (struct pci_dev *dev,u32 *cap); +bool pcie_supports_cxl_timeout_interrupts (u32 cap); +#endif +#endif /* _PORTDRV_H_ */
Signature · 1 line
2.34.1
Re: [RFC PATCH 5/6] pcie/portdrv: Add CXL MSI/-X allocation
Quoted 5 lines · Ben Cheatham
Allocate an MSI/-X for CXL-enabled PCIe root ports that support timeout & isolation interrupts. This vector will be used by the CXL timeout & isolation service driver to disable the root port in the CXL port hierarchy and any associated memory if the port enters isolation.
Wrap to fill 75 columns.
Re: [RFC PATCH 5/6] pcie/portdrv: Add CXL MSI/-X allocation
Quoted 8 lines · Bjorn Helgaas
Quoted 5 lines · Ben Cheatham
Allocate an MSI/-X for CXL-enabled PCIe root ports that support timeout & isolation interrupts. This vector will be used by the CXL timeout & isolation service driver to disable the root port in the CXL port hierarchy and any associated memory if the port enters isolation.
Wrap to fill 75 columns.
Consider it done :).
RFC PATCH 6/6 pcie/cxl_timeout: Add CXL.mem Timeout & Isolation interrupt support
In reply to Ben CheathamAdd support for CXL.mem Timeout & Isolation interrupts. A CXL root port under isolation will not complete writes and will return an exception response (i.e. poison) on reads (CXL 3.0 12.3.2). Therefore, when a CXL-enabled PCIe root port enters isolation, we assume that the memory under the port is unreachable and will need to be unmapped.
When an isolation interrupt occurs, the CXL Timeout & Isolation service driver will mark the port (cxl_dport) as isolated, destroy any CXL memory regions under the *bridge* (cxl_port), and attempt to unmap the memory backing the CXL region(s). If the memory was already in use, the mapping is not guaranteed to succeed.
--- drivers/cxl/core/pci.c | 5 + drivers/cxl/core/port.c | 80 ++++++++++++++++ drivers/cxl/core/region.c | 9 ++ drivers/cxl/cxl.h | 10 ++ drivers/cxl/cxlpci.h | 9 ++ drivers/pci/pcie/cxl_timeout.c | 165 ++++++++++++++++++++++++++++++++- drivers/pci/pcie/portdrv.h | 1 + 7 files changed, 278 insertions(+), 1 deletion(-)
drivers/cxl/core/pci.c +5 -0
@@ -64,6 +64,11 @@ static int match_add_dports(struct pci_dev *pdev, void *data) } ctx->count++; +if (type ==PCI_EXP_TYPE_ROOT_PORT && !pcie_cxlt_register_dport (dport)) +return devm_add_action_or_reset (dport->dport_dev, + pcie_cxlt_unregister_dport, + dport); +return 0 ; }
drivers/cxl/core/port.c +80 -0
86 lines not on this page · raw message
drivers/cxl/core/region.c +9 -0
@@ -1699,6 +1699,12 @@ static int cxl_region_attach(struct cxl_region *cxlr,return -ENXIO ; } +if (cxl_port_is_isolated (ep_port)) { +dev_err (&cxlr->dev,"%s:%s endpoint is under a dport in error isolation\n" , +dev_name (&cxlmd->dev),dev_name (&cxled->cxld.dev)); +return -EBUSY ; + } +if (cxled->cxld.target_type != cxlr->type) { dev_dbg(&cxlr->dev, "%s:%s type mismatch: %d vs %d\n", dev_name(&cxlmd->dev), dev_name(&cxled->cxld.dev),
@@ -2782,6 +2788,9 @@ static struct cxl_region *construct_region(struct cxl_root_decoder *cxlrd,struct resource *res;int rc; +if (cxl_port_is_isolated (cxlmd->endpoint)) +return ERR_PTR (-EBUSY ); + do { cxlr = __create_region(cxlrd, cxled->mode, atomic_read(&cxlrd->region_id));
drivers/cxl/cxl.h +10 -0
@@ -138,6 +138,10 @@ static inline int ways_to_eiw(unsigned int ways, u8 *eiw)#define CXL_TIMEOUT_CONTROL_MEM_TIMEOUT_MASK GENMASK(3, 0)#define CXL_TIMEOUT_CONTROL_MEM_TIMEOUT_ENABLE BIT(4)#define CXL_TIMEOUT_CONTROL_MEM_ISO_ENABLE BIT(16) +#define CXL_TIMEOUT_CONTROL_MEM_INTR_ENABLE BIT(26) +#define CXL_TIMEOUT_STATUS_OFFSET 0xC +#define CXL_TIMEOUT_STATUS_MEM_TIMEOUT BIT(0) +#define CXL_TIMEOUT_STATUS_MEM_ISO BIT(8)#define CXL_TIMEOUT_CAPABILITY_LENGTH 0x10/* CXL 3.0 8.2.4.23.2 CXL Timeout and Isolation Control Register, bits 3:0 */
@@ -700,8 +704,11 @@ struct cxl_dport {struct access_coordinate sw_coord;struct access_coordinate hb_coord;long link_latency; +bool isolated; }; +bool cxl_port_is_isolated (struct cxl_port *port); +/** * struct cxl_ep - track an endpoint's interest in a port * @ep: device that hosts a generic CXL endpoint (expander or accelerator)
@@ -735,6 +742,9 @@ struct cxl_region_ref {int nr_targets; }; +bool cxl_dport_is_in_region (struct cxl_dport *dport,struct cxl_region_ref *ref); +void cxl_port_kill_regions (struct cxl_port *port); +/* * The platform firmware device hosting the root is also the top of the * CXL port topology. All other CXL ports have another CXL port as their
drivers/cxl/cxlpci.h +9 -0
@@ -106,4 +106,13 @@ void read_cdat_data(struct cxl_port *port);void cxl_cor_error_detected (struct pci_dev *pdev);pci_ers_result_t cxl_error_detected (struct pci_dev *pdev,pci_channel_state_t state); + +#ifdef CONFIG_PCIE_CXL_TIMEOUT +int pcie_cxlt_register_dport (struct cxl_dport *dport); +void pcie_cxlt_unregister_dport (struct cxl_dport *dport); +#else +int pcie_cxlt_register_dport (void *dport) {return -ENXIO ; } +void pcie_cxlt_unregister_dport (void *dport) {} +#endif +#endif /* __CXL_PCI_H__ */
drivers/pci/pcie/cxl_timeout.c +164 -1
197 lines not on this page · raw message
drivers/pci/pcie/portdrv.h +1 -0
@@ -10,6 +10,7 @@#define _PORTDRV_H_#include <linux/compiler.h> +#include <linux/errno.h> /* Service Type */ #define PCIE_PORT_SERVICE_PME_SHIFT 0/* Power Management Event */
Signature · 1 line
2.34.1
Re: [RFC PATCH 6/6] pcie/cxl_timeout: Add CXL.mem Timeout & Isolation interrupt support
drivers/pci/pcie/portdrv.h line 13
Quoted 13 lines · Ben Cheatham
Add support for CXL.mem Timeout & Isolation interrupts. A CXL root port under isolation will not complete writes and will return an exception response (i.e. poison) on reads (CXL 3.0 12.3.2). Therefore, when a CXL-enabled PCIe root port enters isolation, we assume that the memory under the port is unreachable and will need to be unmapped.
drivers/pci/pcie/portdrv.h +1
-0@@ -10,6 +10,7 @@#define _PORTDRV_H_#include <linux/compiler.h> +#include <linux/errno.h>
This doesn't look required by portdrv.h. If it's only needed by something that *includes* portdrv.h, I think errno.h should be included by that .c file instead.
Re: [RFC PATCH 6/6] pcie/cxl_timeout: Add CXL.mem Timeout & Isolation interrupt support
Quoted 12 lines · Bjorn Helgaas
Quoted 11 lines · Ben Cheatham
Add support for CXL.mem Timeout & Isolation interrupts. A CXL root port under isolation will not complete writes and will return an exception response (i.e. poison) on reads (CXL 3.0 12.3.2). Therefore, when a CXL-enabled PCIe root port enters isolation, we assume that the memory under the port is unreachable and will need to be unmapped.
drivers/pci/pcie/portdrv.h +0
-0@@ -10,6 +10,7 @@#define _PORTDRV_H_
Quoted 7 lines
drivers/pci/pcie/portdrv.h line 13
Quoted 2 lines
drivers/pci/pcie/portdrv.h +1
-0#include <linux/compiler.h> +#include <linux/errno.h> This doesn't look required by
portdrv.h. If it's only needed by something that *includes*portdrv.h, I thinkerrno.hshould be included by that .c file instead.
I agree. It's a remnant of an older version of this that had a declaration that needed it, I'll remove it.
Thanks again,
Ben
kernel test robot
build botRe: [RFC PATCH 6/6] pcie/cxl_timeout: Add CXL.mem Timeout & Isolation interrupt support
In reply to Ben Cheathamkernel test robot noticed the following build warnings:
Hi Ben,
[This is a private test report for your RFC patch.] kernel test robot noticed the following build warnings:
[auto build test WARNING on pci/next]
[also build test WARNING on pci/for-linus cxl/next cxl/pending linus/master v6.8-rc4 next-20240216] [If your patch is applied to the wrong git tree, kindly drop us a note.
And when submitting patch, we suggest to use '--base' as documented in
https://git-scm.com/docs/git-format-patch#_base_tree_information]
url: https://github.com/intel-lab-lkp/linux/commits/Ben-Cheatham/cxl-core-Add-CXL-Timeout-Isolation-capability-parsing/20240216-034328 base: https://git.kernel.org/pub/scm/linux/kernel/git/pci/pci.git next patch link: https://lore.kernel.org/r/20240215194048.141411-7-Benjamin.Cheatham%40amd.com patch subject: [RFC PATCH 6/6] pcie/cxl_timeout: Add CXL.mem Timeout & Isolation interrupt support config: alpha-allyesconfig (https://download.01.org/0day-ci/archive/20240218/[email protected]/config) compiler: alpha-linux-gcc (GCC) 13.2.0 reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20240218/[email protected]/reproduce)
If you fix the issue in a separate patch/commit (i.e. not just a new version of the same patch/commit), kindly add following tags
| Reported-by: kernel test robot <[email protected]>
| Closes: https://lore.kernel.org/oe-kbuild-all/[email protected]/
All warnings (new ones prefixed by >>):
>> drivers/pci/pcie/cxl_timeout.c:231:13: warning: no previous prototype for 'cxl_timeout_thread' [-Wmissing-prototypes]
231 | irqreturn_t cxl_timeout_thread(int irq, void *data)
| ^~~~~~~~~~~~~~~~~~
vim +/cxl_timeout_thread +231 drivers/pci/pcie/cxl_timeout.c
230
> 231 irqreturn_t cxl_timeout_thread(int irq, void *data)
232 {
233 struct cxl_timeout_wq_data *wq_data;
234 struct cxl_timeout *cxlt = data;
235 struct pcie_device *pcie_dev = cxlt->dev;
236 struct pcie_cxlt_data *pdata;
237 struct cxl_dport *dport;
238 u32 status;
239
240 /*
241 * If the CXL core didn't register a cxl_dport with this PCIe device,
242 * then dport enumeration failed and there's nothing to do CXL-wise.
243 */
244 pdata = get_service_data(pcie_dev);
245 if (!pdata || !pdata->dport)
246 return IRQ_HANDLED;
247
248 dport = pdata->dport;
249
250 status = readl(cxlt->regs + CXL_TIMEOUT_STATUS_OFFSET);
251 if (!(status & CXL_TIMEOUT_STATUS_MEM_ISO
252 || status & CXL_TIMEOUT_STATUS_MEM_TIMEOUT))
253 return IRQ_HANDLED;
254
255 dport->isolated = true;
256
257 wq_data = kzalloc(sizeof(struct cxl_timeout_wq_data), GFP_NOWAIT);
258 if (!wq_data)
259 return IRQ_NONE;
260
261 wq_data->dport = dport;
262
263 INIT_WORK(&wq_data->w, cxl_timeout_handler);
264 queue_work(cxl_timeout_wq, &wq_data->w);
265
266 return IRQ_HANDLED;
267 }
268
Signature · 2 lines
0-DAY CI Kernel Test Service https://github.com/intel/lkp-tests/wiki
kernel test robot
build botRe: [RFC PATCH 6/6] pcie/cxl_timeout: Add CXL.mem Timeout & Isolation interrupt support
In reply to Ben Cheathamkernel test robot noticed the following build errors:
Hi Ben,
[This is a private test report for your RFC patch.] kernel test robot noticed the following build errors:
[auto build test ERROR on pci/next]
[also build test ERROR on pci/for-linus cxl/next cxl/pending linus/master v6.8-rc4 next-20240216] [If your patch is applied to the wrong git tree, kindly drop us a note.
And when submitting patch, we suggest to use '--base' as documented in
https://git-scm.com/docs/git-format-patch#_base_tree_information]
url: https://github.com/intel-lab-lkp/linux/commits/Ben-Cheatham/cxl-core-Add-CXL-Timeout-Isolation-capability-parsing/20240216-034328 base: https://git.kernel.org/pub/scm/linux/kernel/git/pci/pci.git next patch link: https://lore.kernel.org/r/20240215194048.141411-7-Benjamin.Cheatham%40amd.com patch subject: [RFC PATCH 6/6] pcie/cxl_timeout: Add CXL.mem Timeout & Isolation interrupt support config: i386-randconfig-005-20240217 (https://download.01.org/0day-ci/archive/20240218/[email protected]/config) compiler: gcc-12 (Debian 12.2.0-14) 12.2.0 reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20240218/[email protected]/reproduce)
If you fix the issue in a separate patch/commit (i.e. not just a new version of the same patch/commit), kindly add following tags
| Reported-by: kernel test robot <[email protected]>
| Closes: https://lore.kernel.org/oe-kbuild-all/[email protected]/
All errors (new ones prefixed by >>):
ld: drivers/cxl/core/port.o: in function `pcie_cxlt_register_dport':
>> drivers/cxl/cxlpci.h:114: multiple definition of `pcie_cxlt_register_dport'; drivers/pci/pcie/portdrv.o:drivers/pci/pcie/../../cxl/cxlpci.h:114: first defined here ld: drivers/cxl/core/port.o: in function `pcie_cxlt_unregister_dport': >> drivers/cxl/cxlpci.h:115: multiple definition of `pcie_cxlt_unregister_dport'; drivers/pci/pcie/portdrv.o:drivers/pci/pcie/../../cxl/cxlpci.h:115: first defined here ld: drivers/cxl/core/regs.o: in function `pcie_cxlt_register_dport': >> drivers/cxl/cxlpci.h:114: multiple definition of `pcie_cxlt_register_dport'; drivers/pci/pcie/portdrv.o:drivers/pci/pcie/../../cxl/cxlpci.h:114: first defined here ld: drivers/cxl/core/regs.o: in function `pcie_cxlt_unregister_dport': >> drivers/cxl/cxlpci.h:115: multiple definition of `pcie_cxlt_unregister_dport'; drivers/pci/pcie/portdrv.o:drivers/pci/pcie/../../cxl/cxlpci.h:115: first defined here ld: drivers/cxl/core/mbox.o: in function `pcie_cxlt_register_dport': >> drivers/cxl/cxlpci.h:114: multiple definition of `pcie_cxlt_register_dport'; drivers/pci/pcie/portdrv.o:drivers/pci/pcie/../../cxl/cxlpci.h:114: first defined here ld: drivers/cxl/core/mbox.o: in function `pcie_cxlt_unregister_dport': >> drivers/cxl/cxlpci.h:115: multiple definition of `pcie_cxlt_unregister_dport'; drivers/pci/pcie/portdrv.o:drivers/pci/pcie/../../cxl/cxlpci.h:115: first defined here ld: drivers/cxl/core/pci.o: in function `pcie_cxlt_register_dport': >> drivers/cxl/cxlpci.h:114: multiple definition of `pcie_cxlt_register_dport'; drivers/pci/pcie/portdrv.o:drivers/pci/pcie/../../cxl/cxlpci.h:114: first defined here ld: drivers/cxl/core/pci.o: in function `pcie_cxlt_unregister_dport': >> drivers/cxl/cxlpci.h:115: multiple definition of `pcie_cxlt_unregister_dport'; drivers/pci/pcie/portdrv.o:drivers/pci/pcie/../../cxl/cxlpci.h:115: first defined here ld: drivers/cxl/core/cdat.o: in function `pcie_cxlt_register_dport': >> drivers/cxl/cxlpci.h:114: multiple definition of `pcie_cxlt_register_dport'; drivers/pci/pcie/portdrv.o:drivers/pci/pcie/../../cxl/cxlpci.h:114: first defined here ld: drivers/cxl/core/cdat.o: in function `pcie_cxlt_unregister_dport': >> drivers/cxl/cxlpci.h:115: multiple definition of `pcie_cxlt_unregister_dport'; drivers/pci/pcie/portdrv.o:drivers/pci/pcie/../../cxl/cxlpci.h:115: first defined here ld: drivers/cxl/pci.o: in function `pcie_cxlt_register_dport': >> drivers/cxl/cxlpci.h:114: multiple definition of `pcie_cxlt_register_dport'; drivers/pci/pcie/portdrv.o:drivers/pci/pcie/../../cxl/cxlpci.h:114: first defined here ld: drivers/cxl/pci.o: in function `pcie_cxlt_unregister_dport': >> drivers/cxl/cxlpci.h:115: multiple definition of `pcie_cxlt_unregister_dport'; drivers/pci/pcie/portdrv.o:drivers/pci/pcie/../../cxl/cxlpci.h:115: first defined here ld: drivers/cxl/mem.o: in function `pcie_cxlt_register_dport': >> drivers/cxl/cxlpci.h:114: multiple definition of `pcie_cxlt_register_dport'; drivers/pci/pcie/portdrv.o:drivers/pci/pcie/../../cxl/cxlpci.h:114: first defined here ld: drivers/cxl/mem.o: in function `pcie_cxlt_unregister_dport': >> drivers/cxl/cxlpci.h:115: multiple definition of `pcie_cxlt_unregister_dport'; drivers/pci/pcie/portdrv.o:drivers/pci/pcie/../../cxl/cxlpci.h:115: first defined here ld: drivers/cxl/port.o: in function `pcie_cxlt_register_dport': >> drivers/cxl/cxlpci.h:114: multiple definition of `pcie_cxlt_register_dport'; drivers/pci/pcie/portdrv.o:drivers/pci/pcie/../../cxl/cxlpci.h:114: first defined here ld: drivers/cxl/port.o: in function `pcie_cxlt_unregister_dport': >> drivers/cxl/cxlpci.h:115: multiple definition of `pcie_cxlt_unregister_dport'; drivers/pci/pcie/portdrv.o:drivers/pci/pcie/../../cxl/cxlpci.h:115: first defined here
ld: drivers/perf/cxl_pmu.o: in function `pcie_cxlt_register_dport':
drivers/perf/../cxl/cxlpci.h:114: multiple definition of `pcie_cxlt_register_dport'; drivers/pci/pcie/portdrv.o:drivers/pci/pcie/../../cxl/cxlpci.h:114: first defined here
ld: drivers/perf/cxl_pmu.o: in function `pcie_cxlt_unregister_dport':
drivers/perf/../cxl/cxlpci.h:115: multiple definition of `pcie_cxlt_unregister_dport'; drivers/pci/pcie/portdrv.o:drivers/pci/pcie/../../cxl/cxlpci.h:115: first defined here
vim +114 drivers/cxl/cxlpci.h
100
101 int devm_cxl_port_enumerate_dports(struct cxl_port *port);
102 struct cxl_dev_state;
103 int cxl_hdm_decode_init(struct cxl_dev_state *cxlds, struct cxl_hdm *cxlhdm,
104 struct cxl_endpoint_dvsec_info *info);
105 void read_cdat_data(struct cxl_port *port);
106 void cxl_cor_error_detected(struct pci_dev *pdev);
107 pci_ers_result_t cxl_error_detected(struct pci_dev *pdev,
108 pci_channel_state_t state);
109
110 #ifdef CONFIG_PCIE_CXL_TIMEOUT
111 int pcie_cxlt_register_dport(struct cxl_dport *dport);
112 void pcie_cxlt_unregister_dport(struct cxl_dport *dport);
113 #else
> 114 int pcie_cxlt_register_dport(void *dport) { return -ENXIO; }
> 115 void pcie_cxlt_unregister_dport(void *dport) {} 116 #endif
117
Signature · 2 lines
0-DAY CI Kernel Test Service https://github.com/intel/lkp-tests/wiki
kernel test robot
build botRe: [RFC PATCH 6/6] pcie/cxl_timeout: Add CXL.mem Timeout & Isolation interrupt support
In reply to Ben Cheathamkernel test robot noticed the following build errors:
Hi Ben,
[This is a private test report for your RFC patch.] kernel test robot noticed the following build errors:
[auto build test ERROR on pci/next]
[also build test ERROR on pci/for-linus cxl/next cxl/pending linus/master v6.8-rc4 next-20240216] [If your patch is applied to the wrong git tree, kindly drop us a note.
And when submitting patch, we suggest to use '--base' as documented in
https://git-scm.com/docs/git-format-patch#_base_tree_information]
url: https://github.com/intel-lab-lkp/linux/commits/Ben-Cheatham/cxl-core-Add-CXL-Timeout-Isolation-capability-parsing/20240216-034328 base: https://git.kernel.org/pub/scm/linux/kernel/git/pci/pci.git next patch link: https://lore.kernel.org/r/20240215194048.141411-7-Benjamin.Cheatham%40amd.com patch subject: [RFC PATCH 6/6] pcie/cxl_timeout: Add CXL.mem Timeout & Isolation interrupt support config: i386-randconfig-016-20240217 (https://download.01.org/0day-ci/archive/20240218/[email protected]/config) compiler: gcc-7 (Ubuntu 7.5.0-6ubuntu2) 7.5.0 reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20240218/[email protected]/reproduce)
If you fix the issue in a separate patch/commit (i.e. not just a new version of the same patch/commit), kindly add following tags
| Reported-by: kernel test robot <[email protected]>
| Closes: https://lore.kernel.org/oe-kbuild-all/[email protected]/
All errors (new ones prefixed by >>):
ld: drivers/cxl/core/regs.o: in function `pcie_cxlt_register_dport':
>> drivers/cxl/cxlpci.h:114: multiple definition of `pcie_cxlt_register_dport'; drivers/cxl/core/port.o:drivers/cxl/cxlpci.h:114: first defined here ld: drivers/cxl/core/regs.o: in function `pcie_cxlt_unregister_dport': >> drivers/cxl/cxlpci.h:115: multiple definition of `pcie_cxlt_unregister_dport'; drivers/cxl/core/port.o:drivers/cxl/cxlpci.h:115: first defined here ld: drivers/cxl/core/mbox.o: in function `pcie_cxlt_register_dport': >> drivers/cxl/cxlpci.h:114: multiple definition of `pcie_cxlt_register_dport'; drivers/cxl/core/port.o:drivers/cxl/cxlpci.h:114: first defined here ld: drivers/cxl/core/mbox.o: in function `pcie_cxlt_unregister_dport': >> drivers/cxl/cxlpci.h:115: multiple definition of `pcie_cxlt_unregister_dport'; drivers/cxl/core/port.o:drivers/cxl/cxlpci.h:115: first defined here ld: drivers/cxl/core/pci.o: in function `pcie_cxlt_register_dport': >> drivers/cxl/cxlpci.h:114: multiple definition of `pcie_cxlt_register_dport'; drivers/cxl/core/port.o:drivers/cxl/cxlpci.h:114: first defined here ld: drivers/cxl/core/pci.o: in function `pcie_cxlt_unregister_dport': >> drivers/cxl/cxlpci.h:115: multiple definition of `pcie_cxlt_unregister_dport'; drivers/cxl/core/port.o:drivers/cxl/cxlpci.h:115: first defined here ld: drivers/cxl/core/cdat.o: in function `pcie_cxlt_register_dport': >> drivers/cxl/cxlpci.h:114: multiple definition of `pcie_cxlt_register_dport'; drivers/cxl/core/port.o:drivers/cxl/cxlpci.h:114: first defined here ld: drivers/cxl/core/cdat.o: in function `pcie_cxlt_unregister_dport': >> drivers/cxl/cxlpci.h:115: multiple definition of `pcie_cxlt_unregister_dport'; drivers/cxl/core/port.o:drivers/cxl/cxlpci.h:115: first defined here ld: drivers/cxl/port.o: in function `pcie_cxlt_register_dport': >> drivers/cxl/cxlpci.h:114: multiple definition of `pcie_cxlt_register_dport'; drivers/cxl/core/port.o:drivers/cxl/cxlpci.h:114: first defined here ld: drivers/cxl/port.o: in function `pcie_cxlt_unregister_dport': >> drivers/cxl/cxlpci.h:115: multiple definition of `pcie_cxlt_unregister_dport'; drivers/cxl/core/port.o:drivers/cxl/cxlpci.h:115: first defined here
vim +114 drivers/cxl/cxlpci.h
100
101 int devm_cxl_port_enumerate_dports(struct cxl_port *port);
102 struct cxl_dev_state;
103 int cxl_hdm_decode_init(struct cxl_dev_state *cxlds, struct cxl_hdm *cxlhdm,
104 struct cxl_endpoint_dvsec_info *info);
105 void read_cdat_data(struct cxl_port *port);
106 void cxl_cor_error_detected(struct pci_dev *pdev);
107 pci_ers_result_t cxl_error_detected(struct pci_dev *pdev,
108 pci_channel_state_t state);
109
110 #ifdef CONFIG_PCIE_CXL_TIMEOUT
111 int pcie_cxlt_register_dport(struct cxl_dport *dport);
112 void pcie_cxlt_unregister_dport(struct cxl_dport *dport);
113 #else
> 114 int pcie_cxlt_register_dport(void *dport) { return -ENXIO; }
> 115 void pcie_cxlt_unregister_dport(void *dport) {} 116 #endif
117
Signature · 2 lines
0-DAY CI Kernel Test Service https://github.com/intel/lkp-tests/wiki
[ add linux-mm because the implications of this feature weigh much
heavier on mm/ than drivers/ ]
Quoted 9 lines · Ben Cheatham
Implement initial support for CXL.mem Timeout & Isolation (CXL 3.0 12.3.2). This series implements support for CXL.mem enabling and programming CXL.mem transaction timeout, CXL.mem error isolation, and error isolation interrupts for CXL-enabled PCIe root ports that implement the CXL Timeout & Isolation capability.
I am operating under the assumption that recovery from error isolation will be more involved than just resetting the port and turning off isolation, so that flow is not implemented here.
That needs to be answered first.
The notification infrastructure is trivial in comparison. The use case needs to be clear *before* we start adding infrastructure to Linux that may end up just being dead code, and certainly before we further burden portdrv.c with more entanglements.
I put together the write-up below in a separate context for my thoughts on the error isolation capability and that Linux really needs an end user to stand up and say, "yes, even with all those caveats CXL Error Isolation is still useful for our environment." The tl;dr is "are you abosolutely sure you would not just rather reboot?"
Quoted 2 lines
There is also no support for CXL.cache, but I plan to eventually implement both.
To date there are zero upstream drivers for CXL.cache initiators, and CXL 3.0 introduced HDM-DB to supplant HDM-D. All that to say, if there are zero mass-market (devices with upstream drivers) adopters of HDM-D, and there are zero HDM-DB platforms available today it seems Linux has time for this to continue to evolve. If anyone reading this has a CXL.cache initiator driver waiting in the wings, do reach out on the list to clarify what commons belong in the Linux CXL and/or PCI core.
Quoted 3 lines
The series also introduces a PCIe port bus driver dependency on the CXL core. I expect to be able to remove that when when my team submits patches for a future rework of the PCIe port bus driver.
We have time to wait for that work to settle. Do not make the job harder in the near term by adding one more dependency to unwind.
Quoted 7 lines
I have done some testing using QEMU by adding the isolation registers and a hacked-up QMP command to test the interrupt flow, but I *DID NOT* implement the actual isolation feature and the subsequent device behavior. I'd be willing to share these changes (and my config) if anyone is interested in testing this.
Any thoughts/comments would be greatly appreciated!
---
Memory Error Isolation is a mechanism that *might* allow recovery of CXL Root Port Link Down conditions or CXL transaction timeouts. When the event occurs, outstanding writes are dropped, and outstanding reads terminate with machine check. In order to exit Isolation, the link must transition through a "link down" status. Effectively Isolation behaves like a combination of a machine check storm until system software can evacuate all users and then a surprise hot-removal (unplug) of the memory before the device can be recovered. Where recovery is effectively a hot re-plug of the device with a full re-enumeration thereafter. From the Linux perspective all memory contents are considered forfeited. This poses several challenges for how to utilize the memory to achieve reliable recovery. The criteria for evaluating the Linux upstream maintenance cost for overcoming those challenges is whether the sum total of those mitigations remains an improvement over a system-reboot to recover from the same Isolation event. Add to that the fact that not fully accounting for all the mentioned challenges is still going to result in a reboot due to kernel panic.
In order to understand the limits of Isolation recovery relative to reboot recovery, it is important to understand the fundamental limitations of Linux machine check recovery and memory-hotremove. Machine checks are typically only recoverable when they hit user memory. Roughly, if a machine check occurs in a kernel mapped page the machine check handler triggers a kernel panic. Machine checks are often recoverable because failures are limited to a few cachelines at a time and the page allocation distribution is heavily skewed towards user-memory.
CXL Isolation takes down an entire CXL root port, and with interleaving can lead to a region spanning multiple ports to be taken down. Even if the interleave configuration forfeited bandwidth to contain isolation events to a single CXL root port, it is still on the order of 100s of GBs that will start throwing machine checks on access all at once. If that memory is being used by the kernel as typical System-RAM, some of it is likely to be kernel mapped. Marking all CXL memory as ZONE_MOVABLE to avoid kernel allocations is not a reliable mitigation for this scenario as the kernel always needs some ratio of ZONE_NORMAL to access ZONE_MOVABLE memory.
The "kernel memory" problem similarly effects surprise removal events. The kernel can only reliably unplug memory that it can force offline and there is no facility to force-offline ZONE_NORMAL memory. Long term memory pinning like guests VMs with assigned devices or RDMA, or even short-term pins from transient device DMA, can hold off memory removal indefinitely which means recovery may be held off indefinitely. For System-RAM there is no facility to notify all users to evacuate, instead the memory hot-removal code walks every page in the range to be offlined and aborts if any single page has an elevated reference count.
It follows from the above that Isolation requires that the CXL memory ranges to be recovered must never be online as System-RAM, the kernel cannot offer typical memory management services for memory that is subject to "surprise removal". Instead, device-dax is a facility that has some properties that may allow recovery to be reliable. The device-dax facility arranges for a given memory range to be mappable via a device-file. This effectively allows userspace management of that memory, but at the cost of application changes.
If, for example, the intended use case of Isolation capable CXL memory is to place VMs that can die during an Isolation event while keeping the rest of the system up, then that could be achieved with device-dax. For example, allocate a device-dax instance per-VM and specify it as a "memory-backend-file" to qemu-kvm.
Again the loss of typical core mm memory semantics and the need for application changes raises the question of whether reboot is preferred over Isolation recovery. Unlike System-RAM that supports anonymous mappings disconnected from the physical memory device, device-dax implements file-backed mappings which includes methods to reverse-map all users and revoke their access to the memory range that has gone into Isolation.
---
So if someone says, "yes I can tolerate losing a root port at a time and I can tolerate deploying my workloads with userspace memory management, and this is preferable to a reboot", then maybe Linux should entertain CXL Error Isolation. Until such an end use case gains clear uptake it seems too early to worry about plumbing the notification mechanism.
Hey Dan,
Sorry that I went radio silent on this, I've been thinking about the approach to take from here on out. More below!
On 2/15/24 5:43 PM, Dan Williams wrote:
[snip]
Quoted 7 lines
Quoted 3 lines
The series also introduces a PCIe port bus driver dependency on the CXL core. I expect to be able to remove that when when my team submits patches for a future rework of the PCIe port bus driver.
We have time to wait for that work to settle. Do not make the job harder in the near term by adding one more dependency to unwind.
For sure, I'll withhold any work I do that touches the port bus driver until that's sent upstream. I'll send anything that doesn't touch the port driver, i.e. CXL region changes, as RFC as well.
[snip]
Quoted 5 lines
So if someone says, "yes I can tolerate losing a root port at a time and I can tolerate deploying my workloads with userspace memory management, and this is preferable to a reboot", then maybe Linux should entertain CXL Error Isolation. Until such an end use case gains clear uptake it seems too early to worry about plumbing the notification mechanism.
So in my mind the primary use case for this feature is in a server/data center environment. Losing a root port and the attached memory is definitely preferable to a reboot in this environment, so I think that isolation would still be useful even if it isn't plug-and-play.
I agree with your assessment of what has to happen before we can make this feature work. From what I understand these are the main requirements for making isolation work:
1. The memory region can't be onlined as System RAM
2. The region needs to be mapped as device-dax
3. There need to be safeguards such that someone can't remap the region to System RAM with error isolation enabled (added by me)
Considering these all have to do with mm, I think that's a good place to start. What I'm thinking of starting with is adding a module parameter (or config option) to enable isolation for CXL dax regions by default, as well as a sysfs option for toggling error isolation for the CXL region. When the module parameter is specified, the CXL region driver would create the region as a device-dax region by default instead of onlining the region as system RAM. The sysfs would allow toggling error isolation for CXL regions that are already device-dax.
That would cover requirements 1 & 2, but would still allow someone to reconfigure the region as a system RAM region with error isolation still enabled using sysfs/daxctl. To make sure the this doesn't happen, my plan is to have the CXL region driver automatically disable error isolation when the underlying memory region is going offline, then check to make sure the memory isn't onlined as System RAM before re-enabling isolation.
So, with that in mind, isolation would most likely go from something that is enabled by default when compiled in to a feature for correctly-configured CXL regions that has to be enabled by the end user. If that is sounds good, here's what my roadmap would be going forward:
1. Enable creating device-dax mapped CXL regions by default
2. Add support for checking a CXL region meets the requirements for enabling isolation (i.e. all devices in dax region(s) are device-dax)
3. Add back in the error isolation enablement and notification mechanisms in this patch series
And then after those are in place:
4. Add back in timeout mechanisms
5. Recovery flows/support
I'll also be dropping CXL.cache support until there is more support. I'd like to hear your (or anyone else's) thoughts on this!
Thanks,
Ben
Quoted 29 lines · Ben Cheatham
Hey Dan,
Sorry that I went radio silent on this, I've been thinking about the approach to take from here on out. More below!
On 2/15/24 5:43 PM, Dan Williams wrote:
[snip]
Quoted 7 lines
Quoted 3 lines
The series also introduces a PCIe port bus driver dependency on the CXL core. I expect to be able to remove that when when my team submits patches for a future rework of the PCIe port bus driver.
We have time to wait for that work to settle. Do not make the job harder in the near term by adding one more dependency to unwind.
For sure, I'll withhold any work I do that touches the port bus driver until that's sent upstream. I'll send anything that doesn't touch the port driver, i.e. CXL region changes, as RFC as well.
[snip]
Quoted 5 lines
So if someone says, "yes I can tolerate losing a root port at a time and I can tolerate deploying my workloads with userspace memory management, and this is preferable to a reboot", then maybe Linux should entertain CXL Error Isolation. Until such an end use case gains clear uptake it seems too early to worry about plumbing the notification mechanism.
Quoted 5 lines
So in my mind the primary use case for this feature is in a server/data center environment. Losing a root port and the attached memory is definitely preferable to a reboot in this environment, so I think that isolation would still be useful even if it isn't plug-and-play.
That is not sufficient. This feature needs an implementation partner to work through the caveats.
Quoted 3 lines
I agree with your assessment of what has to happen before we can make this feature work. From what I understand these are the main requirements for making isolation work:
Requirement 1 is "Find customer".
Quoted 4 lines
1. The memory region can't be onlined as System RAM
2. The region needs to be mapped as device-dax
3. There need to be safeguards such that someone can't remap the region to System RAM with error isolation enabled (added by me)
No, this policy does not belong in the kernel.
Quoted 8 lines
Considering these all have to do with mm, I think that's a good place to start. What I'm thinking of starting with is adding a module parameter (or config option) to enable isolation for CXL dax regions by default, as well as a sysfs option for toggling error isolation for the CXL region. When the module parameter is specified, the CXL region driver would create the region as a device-dax region by default instead of onlining the region as system RAM. The sysfs would allow toggling error isolation for CXL regions that are already device-dax.
No, definitely not going to invent module paramter policy for this. The policy to not online dax regions is already available.
Quoted 7 lines
That would cover requirements 1 & 2, but would still allow someone to reconfigure the region as a system RAM region with error isolation still enabled using sysfs/daxctl. To make sure the this doesn't happen, my plan is to have the CXL region driver automatically disable error isolation when the underlying memory region is going offline, then check to make sure the memory isn't onlined as System RAM before re-enabling isolation.
Why would you ever need to disable isolation? If it is present it at least nominally allows software to keep running vs hang awaiting a watchdog-timer reboot.
Quoted 5 lines
So, with that in mind, isolation would most likely go from something that is enabled by default when compiled in to a feature for correctly-configured CXL regions that has to be enabled by the end user. If that is sounds good, here's what my roadmap would be going forward:
Again, this needs a customer to weigh the mitigations that the kernel needs to carry.
Quoted 1 line
1. Enable creating device-dax mapped CXL regions by default
Already exists.
Quoted 3 lines
2. Add support for checking a CXL region meets the requirements for enabling isolation (i.e. all devices in
dax region(s) are device-dax)
Regions should not know or care if isolation is enabled, the implications are identical to force unbinding the region driver.
Quoted 2 lines
3. Add back in the error isolation enablement and notification mechanisms in this patch series
Not until it is clear that this feature has deployment value.
Sorry for the delay, I got a bit busy for a while there. Responses inline.
Quoted 30 lines · Dan Williams
Quoted 29 lines · Ben Cheatham
Hey Dan,
Sorry that I went radio silent on this, I've been thinking about the approach to take from here on out. More below!
On 2/15/24 5:43 PM, Dan Williams wrote:
[snip]
Quoted 7 lines
Quoted 3 lines
The series also introduces a PCIe port bus driver dependency on the CXL core. I expect to be able to remove that when when my team submits patches for a future rework of the PCIe port bus driver.
We have time to wait for that work to settle. Do not make the job harder in the near term by adding one more dependency to unwind.
For sure, I'll withhold any work I do that touches the port bus driver until that's sent upstream. I'll send anything that doesn't touch the port driver, i.e. CXL region changes, as RFC as well.
[snip]
Quoted 5 lines
So if someone says, "yes I can tolerate losing a root port at a time and I can tolerate deploying my workloads with userspace memory management, and this is preferable to a reboot", then maybe Linux should entertain CXL Error Isolation. Until such an end use case gains clear uptake it seems too early to worry about plumbing the notification mechanism.
Quoted 9 lines
Quoted 5 lines
So in my mind the primary use case for this feature is in a server/data center environment. Losing a root port and the attached memory is definitely preferable to a reboot in this environment, so I think that isolation would still be useful even if it isn't plug-and-play.
That is not sufficient. This feature needs an implementation partner to work through the caveats.
Got it, I'll come back to this if/when I have a customer willing to commit to this.
Quoted 4 lines
Quoted 3 lines
I agree with your assessment of what has to happen before we can make this feature work. From what I understand these are the main requirements for making isolation work:
Quoted 9 lines
Requirement 1 is "Find customer".
Quoted 4 lines
1. The memory region can't be onlined as System RAM
2. The region needs to be mapped as device-dax
3. There need to be safeguards such that someone can't remap the region to System RAM with error isolation enabled (added by me)No, this policy does not belong in the kernel.
Understood.
Quoted 20 lines
Quoted 8 lines
Considering these all have to do with mm, I think that's a good place to start. What I'm thinking of starting with is adding a module parameter (or config option) to enable isolation for CXL dax regions by default, as well as a sysfs option for toggling error isolation for the CXL region. When the module parameter is specified, the CXL region driver would create the region as a device-dax region by default instead of onlining the region as system RAM. The sysfs would allow toggling error isolation for CXL regions that are already device-dax.
No, definitely not going to invent module paramter policy for this. The policy to not online dax regions is already available.
Quoted 7 lines
That would cover requirements 1 & 2, but would still allow someone to reconfigure the region as a system RAM region with error isolation still enabled using sysfs/daxctl. To make sure the this doesn't happen, my plan is to have the CXL region driver automatically disable error isolation when the underlying memory region is going offline, then check to make sure the memory isn't onlined as System RAM before re-enabling isolation.
Quoted 4 lines
Why would you ever need to disable isolation? If it is present it at least nominally allows software to keep running vs hang awaiting a watchdog-timer reboot.
That's a good point. I think I was just looking at this too long and got a bit lost in the sauce, I'll keep this in mind for if/when I come back to this.
Quoted 11 lines
Quoted 5 lines
So, with that in mind, isolation would most likely go from something that is enabled by default when compiled in to a feature for correctly-configured CXL regions that has to be enabled by the end user. If that is sounds good, here's what my roadmap would be going forward:
Again, this needs a customer to weigh the mitigations that the kernel needs to carry.
Quoted 1 line
1. Enable creating device-dax mapped CXL regions by default
Quoted 9 lines
Already exists.
Quoted 3 lines
2. Add support for checking a CXL region meets the requirements for enabling isolation (i.e. all devices in
dax region(s) are device-dax)Regions should not know or care if isolation is enabled, the implications are identical to force unbinding the region driver.
Got it.
Thanks,
Ben
Quoted 4 lines
Quoted 2 lines
3. Add back in the error isolation enablement and notification mechanisms in this patch series
Not until it is clear that this feature has deployment value.