Lines Matching +full:memory +full:- +full:region
4 Contact: linux-cxl@vger.kernel.org
14 Contact: linux-cxl@vger.kernel.org
17 Memory Device Output Payload in the CXL-2.0
24 Contact: linux-cxl@vger.kernel.org
27 identically named field in the Identify Memory Device Output
28 Payload in the CXL-2.0 specification.
34 Contact: linux-cxl@vger.kernel.org
37 identically named field in the Identify Memory Device Output
38 Payload in the CXL-2.0 specification.
44 Contact: linux-cxl@vger.kernel.org
46 (RO) 64-bit serial number per the PCIe Device Serial Number
48 Memory Device PCIe Capabilities and Extended Capabilities.
54 Contact: linux-cxl@vger.kernel.org
57 host PCI device for this memory device, emit the CPU node
64 Contact: linux-cxl@vger.kernel.org
69 for persistent memory: 'locked', 'unlocked' or 'frozen'. This
77 Contact: linux-cxl@vger.kernel.org
80 sanitize the device to securely re-purpose or decommission it.
81 This is done by ensuring that all user data and meta-data,
87 management, relying instead for it to be done when a region
96 Contact: linux-cxl@vger.kernel.org
103 management, relying instead for it to be done when a region
112 Contact: linux-cxl@vger.kernel.org
117 documented in sysfs-class-firmware.
123 Contact: linux-cxl@vger.kernel.org
133 Contact: linux-cxl@vger.kernel.org
143 Contact: linux-cxl@vger.kernel.org
155 Contact: linux-cxl@vger.kernel.org
159 corresponding memory device into the CXL port hierarchy. When a
170 Contact: linux-cxl@vger.kernel.org
176 may target in its decode of CXL memory resources. The 'Y'
177 integer reflects the hardware port unique-id used in the
184 Contact: linux-cxl@vger.kernel.org
197 Contact: linux-cxl@vger.kernel.org
205 and dynamically updates based on the active memory regions in
212 Contact: linux-cxl@vger.kernel.org
225 Contact: linux-cxl@vger.kernel.org
236 Contact: linux-cxl@vger.kernel.org
239 represents a fixed memory window identified by platform
240 firmware. A fixed window may only support a subset of memory
242 memory, volatile memory, accelerator memory, and / or expander
243 memory may be mapped behind this decoder's memory window.
249 Contact: linux-cxl@vger.kernel.org
252 can optionally decode either accelerator memory (type-2) or
253 expander memory (type-3). The 'target_type' attribute indicates
255 memory regions are activated in this decode hierarchy.
261 Contact: linux-cxl@vger.kernel.org
272 Contact: linux-cxl@vger.kernel.org
276 address range. Device-local address ranges are further split
277 into a 'ram' (volatile memory) range and 'pmem' (persistent
278 memory) range. The 'mode' attribute emits one of 'ram', 'pmem',
292 Contact: linux-cxl@vger.kernel.org
295 and its 'dpa_size' attribute is non-zero, this attribute
303 Contact: linux-cxl@vger.kernel.org
314 instance number disabled decoder with non-zero size. I.e.
323 Contact: linux-cxl@vger.kernel.org
326 physical address (HPA) memory range is interleaved. The device
338 Contact: linux-cxl@vger.kernel.org
350 Contact: linux-cxl@vger.kernel.org
353 of defining a new persistent, or volatile memory region
354 (interleave-set) within the decode range bounded by root decoder
358 region and allocate the region-id for the next creation attempt.
359 EBUSY is returned if the region name written does not match the
366 Contact: linux-cxl@vger.kernel.org
368 (WO) Write a string in the form 'regionZ' to delete that region,
375 Contact: linux-cxl@vger.kernel.org
377 (RW) Write a unique identifier for the region. This field must
379 UUID of another region. For volatile ram regions this
380 attribute is a read-only empty string.
386 Contact: linux-cxl@vger.kernel.org
397 Contact: linux-cxl@vger.kernel.org
400 region is set by writing this value. Each device will provide
401 1/interleave_ways of storage for the region.
407 Contact: linux-cxl@vger.kernel.org
409 (RW) System physical address space to be consumed by the region.
413 region's resource attribute. Size shall be set after the
424 Contact: linux-cxl@vger.kernel.org
426 (RO) The mode of a region is established at region creation time
428 region. For more details on the possible modes see
435 Contact: linux-cxl@vger.kernel.org
437 (RO) A region is a contiguous partition of a CXL root decoder
438 address space. Region capacity is allocated by writing to the
447 Contact: linux-cxl@vger.kernel.org
450 is the intended position of the endpoint device in the region
452 region. ENXIO is returned if the write results in an impossible
455 returned if the position in the region is already occupied, or
456 if the region is not in a state to accept interleave
460 performed before activating the region.
466 Contact: linux-cxl@vger.kernel.org
469 trigger the region to transition from the software programmed
471 operation in addition to validating that the region is in proper
475 Reading this value indicates whether the region is committed or
482 Contact: linux-cxl@vger.kernel.org