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
74 Contact: linux-cxl@vger.kernel.org
84 Contact: linux-cxl@vger.kernel.org
96 Contact: linux-cxl@vger.kernel.org
102 may target in its decode of CXL memory resources. The 'Y'
103 integer reflects the hardware port unique-id used in the
110 Contact: linux-cxl@vger.kernel.org
123 Contact: linux-cxl@vger.kernel.org
131 and dynamically updates based on the active memory regions in
138 Contact: linux-cxl@vger.kernel.org
151 Contact: linux-cxl@vger.kernel.org
162 Contact: linux-cxl@vger.kernel.org
165 represents a fixed memory window identified by platform
166 firmware. A fixed window may only support a subset of memory
168 memory, volatile memory, accelerator memory, and / or expander
169 memory may be mapped behind this decoder's memory window.
175 Contact: linux-cxl@vger.kernel.org
178 can optionally decode either accelerator memory (type-2) or
179 expander memory (type-3). The 'target_type' attribute indicates
181 memory regions are activated in this decode hierarchy.
187 Contact: linux-cxl@vger.kernel.org
198 Contact: linux-cxl@vger.kernel.org
202 address range. Device-local address ranges are further split
203 into a 'ram' (volatile memory) range and 'pmem' (persistent
204 memory) range. The 'mode' attribute emits one of 'ram', 'pmem',
218 Contact: linux-cxl@vger.kernel.org
221 and its 'dpa_size' attribute is non-zero, this attribute
229 Contact: linux-cxl@vger.kernel.org
240 instance number disabled decoder with non-zero size. I.e.
249 Contact: linux-cxl@vger.kernel.org
252 physical address (HPA) memory range is interleaved. The device
264 Contact: linux-cxl@vger.kernel.org
276 Contact: linux-cxl@vger.kernel.org
279 of defining a new persistent memory region (interleave-set)
283 done on write to assign the requested id to a region and
284 allocate the region-id for the next creation attempt. EBUSY is
285 returned if the region name written does not match the current
292 Contact: linux-cxl@vger.kernel.org
294 (WO) Write a string in the form 'regionZ' to delete that region,
301 Contact: linux-cxl@vger.kernel.org
303 (RW) Write a unique identifier for the region. This field must
305 UUID of another region.
311 Contact: linux-cxl@vger.kernel.org
322 Contact: linux-cxl@vger.kernel.org
325 region is set by writing this value. Each device will provide
326 1/interleave_ways of storage for the region.
332 Contact: linux-cxl@vger.kernel.org
334 (RW) System physical address space to be consumed by the region.
338 region's resource attribute. Size shall be set after the
349 Contact: linux-cxl@vger.kernel.org
351 (RO) A region is a contiguous partition of a CXL root decoder
352 address space. Region capacity is allocated by writing to the
361 Contact: linux-cxl@vger.kernel.org
364 is the intended position of the endpoint device in the region
366 region. ENXIO is returned if the write results in an impossible
369 returned if the position in the region is already occupied, or
370 if the region is not in a state to accept interleave
374 performed before activating the region.
380 Contact: linux-cxl@vger.kernel.org
383 trigger the region to transition from the software programmed
385 operation in addition to validating that the region is in proper
389 Reading this value indicates whether the region is committed or