271 lines · plain
1Please note that attributes that are shared between devices are stored in2the directory pointed to by the symlink device/.3For example, the real path of the attribute /sys/class/cxl/afu0.0s/irqs_max is4/sys/class/cxl/afu0.0s/device/irqs_max, i.e. /sys/class/cxl/afu0.0/irqs_max.5 6 7Slave contexts (eg. /sys/class/cxl/afu0.0s):8 9What: /sys/class/cxl/<afu>/afu_err_buf10Date: September 201411Contact: linuxppc-dev@lists.ozlabs.org12Description: read only13 AFU Error Buffer contents. The contents of this file are14 application specific and depends on the AFU being used.15 Applications interacting with the AFU can use this attribute16 to know about the current error condition and take appropriate17 action like logging the event etc.18 19 20What: /sys/class/cxl/<afu>/irqs_max21Date: September 201422Contact: linuxppc-dev@lists.ozlabs.org23Description: read/write24 Decimal value of maximum number of interrupts that can be25 requested by userspace. The default on probe is the maximum26 that hardware can support (eg. 2037). Write values will limit27 userspace applications to that many userspace interrupts. Must28 be >= irqs_min.29Users: https://github.com/ibm-capi/libcxl30 31What: /sys/class/cxl/<afu>/irqs_min32Date: September 201433Contact: linuxppc-dev@lists.ozlabs.org34Description: read only35 Decimal value of the minimum number of interrupts that36 userspace must request on a CXL_START_WORK ioctl. Userspace may37 omit the num_interrupts field in the START_WORK IOCTL to get38 this minimum automatically.39Users: https://github.com/ibm-capi/libcxl40 41What: /sys/class/cxl/<afu>/mmio_size42Date: September 201443Contact: linuxppc-dev@lists.ozlabs.org44Description: read only45 Decimal value of the size of the MMIO space that may be mmapped46 by userspace.47Users: https://github.com/ibm-capi/libcxl48 49What: /sys/class/cxl/<afu>/modes_supported50Date: September 201451Contact: linuxppc-dev@lists.ozlabs.org52Description: read only53 List of the modes this AFU supports. One per line.54 Valid entries are: "dedicated_process" and "afu_directed"55Users: https://github.com/ibm-capi/libcxl56 57What: /sys/class/cxl/<afu>/mode58Date: September 201459Contact: linuxppc-dev@lists.ozlabs.org60Description: read/write61 The current mode the AFU is using. Will be one of the modes62 given in modes_supported. Writing will change the mode63 provided that no user contexts are attached.64Users: https://github.com/ibm-capi/libcxl65 66 67What: /sys/class/cxl/<afu>/prefault_mode68Date: September 201469Contact: linuxppc-dev@lists.ozlabs.org70Description: read/write71 Set the mode for prefaulting in segments into the segment table72 when performing the START_WORK ioctl. Only applicable when73 running under hashed page table mmu.74 Possible values:75 76 ======================= ======================================77 none No prefaulting (default)78 work_element_descriptor Treat the work element79 descriptor as an effective address and80 prefault what it points to.81 all all segments process calling82 START_WORK maps.83 ======================= ======================================84 85Users: https://github.com/ibm-capi/libcxl86 87What: /sys/class/cxl/<afu>/reset88Date: September 201489Contact: linuxppc-dev@lists.ozlabs.org90Description: write only91 Writing 1 here will reset the AFU provided there are not92 contexts active on the AFU.93Users: https://github.com/ibm-capi/libcxl94 95What: /sys/class/cxl/<afu>/api_version96Date: September 201497Contact: linuxppc-dev@lists.ozlabs.org98Description: read only99 Decimal value of the current version of the kernel/user API.100Users: https://github.com/ibm-capi/libcxl101 102What: /sys/class/cxl/<afu>/api_version_compatible103Date: September 2014104Contact: linuxppc-dev@lists.ozlabs.org105Description: read only106 Decimal value of the lowest version of the userspace API107 this kernel supports.108Users: https://github.com/ibm-capi/libcxl109 110 111AFU configuration records (eg. /sys/class/cxl/afu0.0/cr0):112 113An AFU may optionally export one or more PCIe like configuration records, known114as AFU configuration records, which will show up here (if present).115 116What: /sys/class/cxl/<afu>/cr<config num>/vendor117Date: February 2015118Contact: linuxppc-dev@lists.ozlabs.org119Description: read only120 Hexadecimal value of the vendor ID found in this AFU121 configuration record.122Users: https://github.com/ibm-capi/libcxl123 124What: /sys/class/cxl/<afu>/cr<config num>/device125Date: February 2015126Contact: linuxppc-dev@lists.ozlabs.org127Description: read only128 Hexadecimal value of the device ID found in this AFU129 configuration record.130Users: https://github.com/ibm-capi/libcxl131 132What: /sys/class/cxl/<afu>/cr<config num>/class133Date: February 2015134Contact: linuxppc-dev@lists.ozlabs.org135Description: read only136 Hexadecimal value of the class code found in this AFU137 configuration record.138Users: https://github.com/ibm-capi/libcxl139 140What: /sys/class/cxl/<afu>/cr<config num>/config141Date: February 2015142Contact: linuxppc-dev@lists.ozlabs.org143Description: read only144 This binary file provides raw access to the AFU configuration145 record. The format is expected to match the either the standard146 or extended configuration space defined by the PCIe147 specification.148Users: https://github.com/ibm-capi/libcxl149 150 151 152Master contexts (eg. /sys/class/cxl/afu0.0m)153 154What: /sys/class/cxl/<afu>m/mmio_size155Date: September 2014156Contact: linuxppc-dev@lists.ozlabs.org157Description: read only158 Decimal value of the size of the MMIO space that may be mmapped159 by userspace. This includes all slave contexts space also.160Users: https://github.com/ibm-capi/libcxl161 162What: /sys/class/cxl/<afu>m/pp_mmio_len163Date: September 2014164Contact: linuxppc-dev@lists.ozlabs.org165Description: read only166 Decimal value of the Per Process MMIO space length.167Users: https://github.com/ibm-capi/libcxl168 169What: /sys/class/cxl/<afu>m/pp_mmio_off170Date: September 2014171Contact: linuxppc-dev@lists.ozlabs.org172Description: read only173 (not in a guest)174 Decimal value of the Per Process MMIO space offset.175Users: https://github.com/ibm-capi/libcxl176 177 178Card info (eg. /sys/class/cxl/card0)179 180What: /sys/class/cxl/<card>/caia_version181Date: September 2014182Contact: linuxppc-dev@lists.ozlabs.org183Description: read only184 Identifies the CAIA Version the card implements.185Users: https://github.com/ibm-capi/libcxl186 187What: /sys/class/cxl/<card>/psl_revision188Date: September 2014189Contact: linuxppc-dev@lists.ozlabs.org190Description: read only191 Identifies the revision level of the PSL.192Users: https://github.com/ibm-capi/libcxl193 194What: /sys/class/cxl/<card>/base_image195Date: September 2014196Contact: linuxppc-dev@lists.ozlabs.org197Description: read only198 (not in a guest)199 Identifies the revision level of the base image for devices200 that support loadable PSLs. For FPGAs this field identifies201 the image contained in the on-adapter flash which is loaded202 during the initial program load.203Users: https://github.com/ibm-capi/libcxl204 205What: /sys/class/cxl/<card>/image_loaded206Date: September 2014207Contact: linuxppc-dev@lists.ozlabs.org208Description: read only209 (not in a guest)210 Will return "user" or "factory" depending on the image loaded211 onto the card.212Users: https://github.com/ibm-capi/libcxl213 214What: /sys/class/cxl/<card>/load_image_on_perst215Date: December 2014216Contact: linuxppc-dev@lists.ozlabs.org217Description: read/write218 (not in a guest)219 Valid entries are "none", "user", and "factory".220 "none" means PERST will not cause image to be loaded to the221 card. A power cycle is required to load the image.222 "none" could be useful for debugging because the trace arrays223 are preserved.224 225 "user" and "factory" means PERST will cause either the user or226 user or factory image to be loaded.227 Default is to reload on PERST whichever image the card has228 loaded.229Users: https://github.com/ibm-capi/libcxl230 231What: /sys/class/cxl/<card>/reset232Date: October 2014233Contact: linuxppc-dev@lists.ozlabs.org234Description: write only235 Writing 1 will issue a PERST to card provided there are no236 contexts active on any one of the card AFUs. This may cause237 the card to reload the FPGA depending on load_image_on_perst.238 Writing -1 will do a force PERST irrespective of any active239 contexts on the card AFUs.240Users: https://github.com/ibm-capi/libcxl241 242What: /sys/class/cxl/<card>/perst_reloads_same_image243Date: July 2015244Contact: linuxppc-dev@lists.ozlabs.org245Description: read/write246 (not in a guest)247 Trust that when an image is reloaded via PERST, it will not248 have changed.249 250 == =================================================251 0 don't trust, the image may be different (default)252 1 trust that the image will not change.253 == =================================================254Users: https://github.com/ibm-capi/libcxl255 256What: /sys/class/cxl/<card>/psl_timebase_synced257Date: March 2016258Contact: linuxppc-dev@lists.ozlabs.org259Description: read only260 Returns 1 if the psl timebase register is synchronized261 with the core timebase register, 0 otherwise.262Users: https://github.com/ibm-capi/libcxl263 264What: /sys/class/cxl/<card>/tunneled_ops_supported265Date: May 2018266Contact: linuxppc-dev@lists.ozlabs.org267Description: read only268 Returns 1 if tunneled operations are supported in capi mode,269 0 otherwise.270Users: https://github.com/ibm-capi/libcxl271