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
40 class-ids can be compared against a similar "qos_class"
42 that the endpoints map their local memory-class to a
45 side-effects that may result. First class-id is displayed.
51 Contact: linux-cxl@vger.kernel.org
54 identically named field in the Identify Memory Device Output
55 Payload in the CXL-2.0 specification.
61 Contact: linux-cxl@vger.kernel.org
67 class-ids can be compared against a similar "qos_class"
69 that the endpoints map their local memory-class to a
72 side-effects that may result. First class-id is displayed.
78 Contact: linux-cxl@vger.kernel.org
80 (RO) 64-bit serial number per the PCIe Device Serial Number
82 Memory Device PCIe Capabilities and Extended Capabilities.
88 Contact: linux-cxl@vger.kernel.org
91 host PCI device for this memory device, emit the CPU node
98 Contact: linux-cxl@vger.kernel.org
103 for persistent memory: 'locked', 'unlocked' or 'frozen'. This
111 Contact: linux-cxl@vger.kernel.org
114 sanitize the device to securely re-purpose or decommission it.
115 This is done by ensuring that all user data and meta-data,
121 management, relying instead for it to be done when a region
130 Contact: linux-cxl@vger.kernel.org
137 management, relying instead for it to be done when a region
146 Contact: linux-cxl@vger.kernel.org
151 documented in sysfs-class-firmware.
157 Contact: linux-cxl@vger.kernel.org
167 Contact: linux-cxl@vger.kernel.org
177 Contact: linux-cxl@vger.kernel.org
189 Contact: linux-cxl@vger.kernel.org
193 corresponding memory device into the CXL port hierarchy. When a
204 Contact: linux-cxl@vger.kernel.org
210 may target in its decode of CXL memory resources. The 'Y'
211 integer reflects the hardware port unique-id used in the
218 Contact: linux-cxl@vger.kernel.org
220 (RO) A memory device is considered active when any of its
233 Contact: linux-cxl@vger.kernel.org
246 Contact: linux-cxl@vger.kernel.org
254 and dynamically updates based on the active memory regions in
261 Contact: linux-cxl@vger.kernel.org
274 Contact: linux-cxl@vger.kernel.org
285 Contact: linux-cxl@vger.kernel.org
288 represents a fixed memory window identified by platform
289 firmware. A fixed window may only support a subset of memory
291 memory, volatile memory, accelerator memory, and / or expander
292 memory may be mapped behind this decoder's memory window.
298 Contact: linux-cxl@vger.kernel.org
301 can optionally decode either accelerator memory (type-2) or
302 expander memory (type-3). The 'target_type' attribute indicates
304 memory regions are activated in this decode hierarchy.
310 Contact: linux-cxl@vger.kernel.org
321 Contact: linux-cxl@vger.kernel.org
325 address range. Device-local address ranges are further split
326 into a 'ram' (volatile memory) range and 'pmem' (persistent
327 memory) range. The 'mode' attribute emits one of 'ram', 'pmem',
341 Contact: linux-cxl@vger.kernel.org
344 and its 'dpa_size' attribute is non-zero, this attribute
352 Contact: linux-cxl@vger.kernel.org
363 instance number disabled decoder with non-zero size. I.e.
372 Contact: linux-cxl@vger.kernel.org
375 physical address (HPA) memory range is interleaved. The device
387 Contact: linux-cxl@vger.kernel.org
399 Contact: linux-cxl@vger.kernel.org
402 of defining a new persistent, or volatile memory region
403 (interleave-set) within the decode range bounded by root decoder
407 region and allocate the region-id for the next creation attempt.
408 EBUSY is returned if the region name written does not match the
415 Contact: linux-cxl@vger.kernel.org
417 (WO) Write a string in the form 'regionZ' to delete that region,
424 Contact: linux-cxl@vger.kernel.org
427 root-decoder-only attribute conveys a platform specific cookie
429 This class-id can be compared against a similar "qos_class"
430 published for each memory-type that an endpoint supports. While
431 it is not required that endpoints map their local memory-class
433 there are platform specific side-effects that may result.
439 Contact: linux-cxl@vger.kernel.org
441 (RW) Write a unique identifier for the region. This field must
443 UUID of another region. For volatile ram regions this
444 attribute is a read-only empty string.
450 Contact: linux-cxl@vger.kernel.org
461 Contact: linux-cxl@vger.kernel.org
464 region is set by writing this value. Each device will provide
465 1/interleave_ways of storage for the region.
471 Contact: linux-cxl@vger.kernel.org
473 (RW) System physical address space to be consumed by the region.
477 region's resource attribute. Size shall be set after the
488 Contact: linux-cxl@vger.kernel.org
490 (RO) The mode of a region is established at region creation time
492 region. For more details on the possible modes see
499 Contact: linux-cxl@vger.kernel.org
501 (RO) A region is a contiguous partition of a CXL root decoder
502 address space. Region capacity is allocated by writing to the
511 Contact: linux-cxl@vger.kernel.org
514 is the intended position of the endpoint device in the region
516 region. ENXIO is returned if the write results in an impossible
519 returned if the position in the region is already occupied, or
520 if the region is not in a state to accept interleave
524 performed before activating the region.
530 Contact: linux-cxl@vger.kernel.org
533 trigger the region to transition from the software programmed
535 operation in addition to validating that the region is in proper
539 Reading this value indicates whether the region is committed or
546 Contact: linux-cxl@vger.kernel.org
561 Contact: linux-cxl@vger.kernel.org
563 (RO) The aggregated read or write bandwidth of the region. The
564 number is the accumulated read or write bandwidth of all CXL memory
565 devices that contributes to the region in MB/s. It is
569 See Documentation/ABI/stable/sysfs-devices-node. access0 provides
578 Contact: linux-cxl@vger.kernel.org
580 (RO) The read or write latency of the region. The number is
581 the worst read or write latency of all CXL memory devices that
582 contributes to the region in nanoseconds. It is identical data
586 See Documentation/ABI/stable/sysfs-devices-node. access0 provides