Lines Matching +full:non +full:- +full:interleave
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
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
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
88 Contact: linux-cxl@vger.kernel.org
98 Contact: linux-cxl@vger.kernel.org
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,
130 Contact: linux-cxl@vger.kernel.org
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
204 Contact: linux-cxl@vger.kernel.org
211 integer reflects the hardware port unique-id used in the
218 Contact: linux-cxl@vger.kernel.org
233 Contact: linux-cxl@vger.kernel.org
246 Contact: linux-cxl@vger.kernel.org
261 Contact: linux-cxl@vger.kernel.org
274 Contact: linux-cxl@vger.kernel.org
278 configured interleave order of the decoder's dport instances.
285 Contact: linux-cxl@vger.kernel.org
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
310 Contact: linux-cxl@vger.kernel.org
321 Contact: linux-cxl@vger.kernel.org
325 address range. Device-local address ranges are further split
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
378 decoder's position in the interleave is determined by the
380 decoders their interleave is specified by platform firmware and
387 Contact: linux-cxl@vger.kernel.org
391 to the next target in the interleave at address N +
399 Contact: linux-cxl@vger.kernel.org
403 (interleave-set) within the decode range bounded by root decoder
407 region and allocate the region-id for the next creation attempt.
415 Contact: linux-cxl@vger.kernel.org
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
444 attribute is a read-only empty string.
450 Contact: linux-cxl@vger.kernel.org
453 interleave set will claim. The possible interleave granularity
461 Contact: linux-cxl@vger.kernel.org
471 Contact: linux-cxl@vger.kernel.org
478 interleave configuration parameters. Once set it cannot be
488 Contact: linux-cxl@vger.kernel.org
499 Contact: linux-cxl@vger.kernel.org
511 Contact: linux-cxl@vger.kernel.org
515 interleave and N is the 'interleave_ways' setting for the
518 position relative to the root decoder interleave. EBUSY is
520 if the region is not in a state to accept interleave
530 Contact: linux-cxl@vger.kernel.org
546 Contact: linux-cxl@vger.kernel.org
561 Contact: linux-cxl@vger.kernel.org
569 See Documentation/ABI/stable/sysfs-devices-node. access0 provides
578 Contact: linux-cxl@vger.kernel.org
586 See Documentation/ABI/stable/sysfs-devices-node. access0 provides