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
34 Contact: linux-cxl@vger.kernel.org
42 Contact: linux-cxl@vger.kernel.org
45 identically named field in the Identify Memory Device Output
46 Payload in the CXL-2.0 specification.
52 Contact: linux-cxl@vger.kernel.org
58 class-ids can be compared against a similar "qos_class"
60 that the endpoints map their local memory-class to a
63 side-effects that may result. First class-id is displayed.
69 Contact: linux-cxl@vger.kernel.org
72 identically named field in the Identify Memory Device Output
73 Payload in the CXL-2.0 specification.
79 Contact: linux-cxl@vger.kernel.org
85 class-ids can be compared against a similar "qos_class"
87 that the endpoints map their local memory-class to a
90 side-effects that may result. First class-id is displayed.
96 Contact: linux-cxl@vger.kernel.org
98 (RO) 64-bit serial number per the PCIe Device Serial Number
100 Memory Device PCIe Capabilities and Extended Capabilities.
106 Contact: linux-cxl@vger.kernel.org
109 host PCI device for this memory device, emit the CPU node
116 Contact: linux-cxl@vger.kernel.org
121 for persistent memory: 'locked', 'unlocked' or 'frozen'. This
129 Contact: linux-cxl@vger.kernel.org
132 sanitize the device to securely re-purpose or decommission it.
133 This is done by ensuring that all user data and meta-data,
139 management, relying instead for it to be done when a region
148 Contact: linux-cxl@vger.kernel.org
155 management, relying instead for it to be done when a region
164 Contact: linux-cxl@vger.kernel.org
169 documented in sysfs-class-firmware.
175 Contact: linux-cxl@vger.kernel.org
185 Contact: linux-cxl@vger.kernel.org
195 Contact: linux-cxl@vger.kernel.org
207 Contact: linux-cxl@vger.kernel.org
211 corresponding memory device into the CXL port hierarchy. When a
222 Contact: linux-cxl@vger.kernel.org
228 may target in its decode of CXL memory resources. The 'Y'
229 integer reflects the hardware port unique-id used in the
236 Contact: linux-cxl@vger.kernel.org
238 (RO) A memory device is considered active when any of its
251 Contact: linux-cxl@vger.kernel.org
264 Contact: linux-cxl@vger.kernel.org
272 and dynamically updates based on the active memory regions in
279 Contact: linux-cxl@vger.kernel.org
292 Contact: linux-cxl@vger.kernel.org
303 Contact: linux-cxl@vger.kernel.org
306 represents a fixed memory window identified by platform
307 firmware. A fixed window may only support a subset of memory
309 memory, volatile memory, accelerator memory, and / or expander
310 memory may be mapped behind this decoder's memory window.
316 Contact: linux-cxl@vger.kernel.org
319 can optionally decode either accelerator memory (type-2) or
320 expander memory (type-3). The 'target_type' attribute indicates
322 memory regions are activated in this decode hierarchy.
328 Contact: linux-cxl@vger.kernel.org
339 Contact: linux-cxl@vger.kernel.org
343 local address range. Device-local address ranges are further
344 split into a 'ram' (volatile memory) range and 'pmem'
345 (persistent memory) range. The 'mode' attribute emits one of
358 Contact: linux-cxl@vger.kernel.org
361 and its 'dpa_size' attribute is non-zero, this attribute
369 Contact: linux-cxl@vger.kernel.org
380 instance number disabled decoder with non-zero size. I.e.
389 Contact: linux-cxl@vger.kernel.org
392 physical address (HPA) memory range is interleaved. The device
404 Contact: linux-cxl@vger.kernel.org
416 Contact: linux-cxl@vger.kernel.org
419 of defining a new persistent, or volatile memory region
420 (interleave-set) within the decode range bounded by root decoder
424 region and allocate the region-id for the next creation attempt.
425 EBUSY is returned if the region name written does not match the
432 Contact: linux-cxl@vger.kernel.org
434 (WO) Write a string in the form 'regionZ' to delete that region,
441 Contact: linux-cxl@vger.kernel.org
444 root-decoder-only attribute conveys a platform specific cookie
446 This class-id can be compared against a similar "qos_class"
447 published for each memory-type that an endpoint supports. While
448 it is not required that endpoints map their local memory-class
450 there are platform specific side-effects that may result.
456 Contact: linux-cxl@vger.kernel.org
458 (RW) Write a unique identifier for the region. This field must
460 UUID of another region. For volatile ram regions this
461 attribute is a read-only empty string.
467 Contact: linux-cxl@vger.kernel.org
478 Contact: linux-cxl@vger.kernel.org
481 region is set by writing this value. Each device will provide
482 1/interleave_ways of storage for the region.
488 Contact: linux-cxl@vger.kernel.org
490 (RW) System physical address space to be consumed by the region.
494 region's resource attribute. Size shall be set after the
505 Contact: linux-cxl@vger.kernel.org
507 (RO) The mode of a region is established at region creation time
509 region. For more details on the possible modes see
516 Contact: linux-cxl@vger.kernel.org
518 (RO) A region is a contiguous partition of a CXL root decoder
519 address space. Region capacity is allocated by writing to the
528 Contact: linux-cxl@vger.kernel.org
531 is the intended position of the endpoint device in the region
533 region. ENXIO is returned if the write results in an impossible
536 returned if the position in the region is already occupied, or
537 if the region is not in a state to accept interleave
541 performed before activating the region.
547 Contact: linux-cxl@vger.kernel.org
550 trigger the region to transition from the software programmed
552 operation in addition to validating that the region is in proper
556 Reading this value indicates whether the region is committed or
563 Contact: linux-cxl@vger.kernel.org
578 Contact: linux-cxl@vger.kernel.org
580 (RO) The aggregated read or write bandwidth of the region. The
581 number is the accumulated read or write bandwidth of all CXL memory
582 devices that contributes to the region in MB/s. It is
586 See Documentation/ABI/stable/sysfs-devices-node. access0 provides
595 Contact: linux-cxl@vger.kernel.org
597 (RO) The read or write latency of the region. The number is
598 the worst read or write latency of all CXL memory devices that
599 contributes to the region in nanoseconds. It is identical data
603 See Documentation/ABI/stable/sysfs-devices-node. access0 provides
608 What: /sys/bus/cxl/devices/nvdimm-bridge0/ndbusX/nmemY/cxl/dirty_shutdown
611 Contact: linux-cxl@vger.kernel.org