xref: /linux/Documentation/ABI/testing/debugfs-cxl (revision be239684b18e1cdcafcf8c7face4a2f562c745ad)
1What:		/sys/kernel/debug/cxl/memX/inject_poison
2Date:		April, 2023
3KernelVersion:	v6.4
4Contact:	linux-cxl@vger.kernel.org
5Description:
6		(WO) When a Device Physical Address (DPA) is written to this
7		attribute, the memdev driver sends an inject poison command to
8		the device for the specified address. The DPA must be 64-byte
9		aligned and the length of the injected poison is 64-bytes. If
10		successful, the device returns poison when the address is
11		accessed through the CXL.mem bus. Injecting poison adds the
12		address to the device's Poison List and the error source is set
13		to Injected. In addition, the device adds a poison creation
14		event to its internal Informational Event log, updates the
15		Event Status register, and if configured, interrupts the host.
16		It is not an error to inject poison into an address that
17		already has poison present and no error is returned. The
18		inject_poison attribute is only visible for devices supporting
19		the capability.
20
21
22What:		/sys/kernel/debug/memX/clear_poison
23Date:		April, 2023
24KernelVersion:	v6.4
25Contact:	linux-cxl@vger.kernel.org
26Description:
27		(WO) When a Device Physical Address (DPA) is written to this
28		attribute, the memdev driver sends a clear poison command to
29		the device for the specified address. Clearing poison removes
30		the address from the device's Poison List and writes 0 (zero)
31		for 64 bytes starting at address. It is not an error to clear
32		poison from an address that does not have poison set. If the
33		device cannot clear poison from the address, -ENXIO is returned.
34		The clear_poison attribute is only visible for devices
35		supporting the capability.
36