sysfs-class-cxl 10 KB

123456789101112131415161718192021222324252627282930313233343536373839404142434445464748495051525354555657585960616263646566676869707172737475767778798081828384858687888990919293949596979899100101102103104105106107108109110111112113114115116117118119120121122123124125126127128129130131132133134135136137138139140141142143144145146147148149150151152153154155156157158159160161162163164165166167168169170171172173174175176177178179180181182183184185186187188189190191192193194195196197198199200201202203204205206207208209210211212213214215216217218219220221222223224225226227228229230231232233234235236237238239240241242243244245246247248249250251252253254255256
  1. Note: Attributes that are shared between devices are stored in the directory
  2. pointed to by the symlink device/.
  3. Example: The real path of the attribute /sys/class/cxl/afu0.0s/irqs_max is
  4. /sys/class/cxl/afu0.0s/device/irqs_max, i.e. /sys/class/cxl/afu0.0/irqs_max.
  5. Slave contexts (eg. /sys/class/cxl/afu0.0s):
  6. What: /sys/class/cxl/<afu>/afu_err_buf
  7. Date: September 2014
  8. Contact: linuxppc-dev@lists.ozlabs.org
  9. Description: read only
  10. AFU Error Buffer contents. The contents of this file are
  11. application specific and depends on the AFU being used.
  12. Applications interacting with the AFU can use this attribute
  13. to know about the current error condition and take appropriate
  14. action like logging the event etc.
  15. What: /sys/class/cxl/<afu>/irqs_max
  16. Date: September 2014
  17. Contact: linuxppc-dev@lists.ozlabs.org
  18. Description: read/write
  19. Decimal value of maximum number of interrupts that can be
  20. requested by userspace. The default on probe is the maximum
  21. that hardware can support (eg. 2037). Write values will limit
  22. userspace applications to that many userspace interrupts. Must
  23. be >= irqs_min.
  24. Users: https://github.com/ibm-capi/libcxl
  25. What: /sys/class/cxl/<afu>/irqs_min
  26. Date: September 2014
  27. Contact: linuxppc-dev@lists.ozlabs.org
  28. Description: read only
  29. Decimal value of the minimum number of interrupts that
  30. userspace must request on a CXL_START_WORK ioctl. Userspace may
  31. omit the num_interrupts field in the START_WORK IOCTL to get
  32. this minimum automatically.
  33. Users: https://github.com/ibm-capi/libcxl
  34. What: /sys/class/cxl/<afu>/mmio_size
  35. Date: September 2014
  36. Contact: linuxppc-dev@lists.ozlabs.org
  37. Description: read only
  38. Decimal value of the size of the MMIO space that may be mmaped
  39. by userspace.
  40. Users: https://github.com/ibm-capi/libcxl
  41. What: /sys/class/cxl/<afu>/modes_supported
  42. Date: September 2014
  43. Contact: linuxppc-dev@lists.ozlabs.org
  44. Description: read only
  45. List of the modes this AFU supports. One per line.
  46. Valid entries are: "dedicated_process" and "afu_directed"
  47. Users: https://github.com/ibm-capi/libcxl
  48. What: /sys/class/cxl/<afu>/mode
  49. Date: September 2014
  50. Contact: linuxppc-dev@lists.ozlabs.org
  51. Description: read/write
  52. The current mode the AFU is using. Will be one of the modes
  53. given in modes_supported. Writing will change the mode
  54. provided that no user contexts are attached.
  55. Users: https://github.com/ibm-capi/libcxl
  56. What: /sys/class/cxl/<afu>/prefault_mode
  57. Date: September 2014
  58. Contact: linuxppc-dev@lists.ozlabs.org
  59. Description: read/write
  60. Set the mode for prefaulting in segments into the segment table
  61. when performing the START_WORK ioctl. Only applicable when
  62. running under hashed page table mmu.
  63. Possible values:
  64. none: No prefaulting (default)
  65. work_element_descriptor: Treat the work element
  66. descriptor as an effective address and
  67. prefault what it points to.
  68. all: all segments process calling START_WORK maps.
  69. Users: https://github.com/ibm-capi/libcxl
  70. What: /sys/class/cxl/<afu>/reset
  71. Date: September 2014
  72. Contact: linuxppc-dev@lists.ozlabs.org
  73. Description: write only
  74. Writing 1 here will reset the AFU provided there are not
  75. contexts active on the AFU.
  76. Users: https://github.com/ibm-capi/libcxl
  77. What: /sys/class/cxl/<afu>/api_version
  78. Date: September 2014
  79. Contact: linuxppc-dev@lists.ozlabs.org
  80. Description: read only
  81. Decimal value of the current version of the kernel/user API.
  82. Users: https://github.com/ibm-capi/libcxl
  83. What: /sys/class/cxl/<afu>/api_version_compatible
  84. Date: September 2014
  85. Contact: linuxppc-dev@lists.ozlabs.org
  86. Description: read only
  87. Decimal value of the the lowest version of the userspace API
  88. this this kernel supports.
  89. Users: https://github.com/ibm-capi/libcxl
  90. AFU configuration records (eg. /sys/class/cxl/afu0.0/cr0):
  91. An AFU may optionally export one or more PCIe like configuration records, known
  92. as AFU configuration records, which will show up here (if present).
  93. What: /sys/class/cxl/<afu>/cr<config num>/vendor
  94. Date: February 2015
  95. Contact: linuxppc-dev@lists.ozlabs.org
  96. Description: read only
  97. Hexadecimal value of the vendor ID found in this AFU
  98. configuration record.
  99. Users: https://github.com/ibm-capi/libcxl
  100. What: /sys/class/cxl/<afu>/cr<config num>/device
  101. Date: February 2015
  102. Contact: linuxppc-dev@lists.ozlabs.org
  103. Description: read only
  104. Hexadecimal value of the device ID found in this AFU
  105. configuration record.
  106. Users: https://github.com/ibm-capi/libcxl
  107. What: /sys/class/cxl/<afu>/cr<config num>/class
  108. Date: February 2015
  109. Contact: linuxppc-dev@lists.ozlabs.org
  110. Description: read only
  111. Hexadecimal value of the class code found in this AFU
  112. configuration record.
  113. Users: https://github.com/ibm-capi/libcxl
  114. What: /sys/class/cxl/<afu>/cr<config num>/config
  115. Date: February 2015
  116. Contact: linuxppc-dev@lists.ozlabs.org
  117. Description: read only
  118. This binary file provides raw access to the AFU configuration
  119. record. The format is expected to match the either the standard
  120. or extended configuration space defined by the PCIe
  121. specification.
  122. Users: https://github.com/ibm-capi/libcxl
  123. Master contexts (eg. /sys/class/cxl/afu0.0m)
  124. What: /sys/class/cxl/<afu>m/mmio_size
  125. Date: September 2014
  126. Contact: linuxppc-dev@lists.ozlabs.org
  127. Description: read only
  128. Decimal value of the size of the MMIO space that may be mmaped
  129. by userspace. This includes all slave contexts space also.
  130. Users: https://github.com/ibm-capi/libcxl
  131. What: /sys/class/cxl/<afu>m/pp_mmio_len
  132. Date: September 2014
  133. Contact: linuxppc-dev@lists.ozlabs.org
  134. Description: read only
  135. Decimal value of the Per Process MMIO space length.
  136. Users: https://github.com/ibm-capi/libcxl
  137. What: /sys/class/cxl/<afu>m/pp_mmio_off (not in a guest)
  138. Date: September 2014
  139. Contact: linuxppc-dev@lists.ozlabs.org
  140. Description: read only
  141. Decimal value of the Per Process MMIO space offset.
  142. Users: https://github.com/ibm-capi/libcxl
  143. Card info (eg. /sys/class/cxl/card0)
  144. What: /sys/class/cxl/<card>/caia_version
  145. Date: September 2014
  146. Contact: linuxppc-dev@lists.ozlabs.org
  147. Description: read only
  148. Identifies the CAIA Version the card implements.
  149. Users: https://github.com/ibm-capi/libcxl
  150. What: /sys/class/cxl/<card>/psl_revision
  151. Date: September 2014
  152. Contact: linuxppc-dev@lists.ozlabs.org
  153. Description: read only
  154. Identifies the revision level of the PSL.
  155. Users: https://github.com/ibm-capi/libcxl
  156. What: /sys/class/cxl/<card>/base_image (not in a guest)
  157. Date: September 2014
  158. Contact: linuxppc-dev@lists.ozlabs.org
  159. Description: read only
  160. Identifies the revision level of the base image for devices
  161. that support loadable PSLs. For FPGAs this field identifies
  162. the image contained in the on-adapter flash which is loaded
  163. during the initial program load.
  164. Users: https://github.com/ibm-capi/libcxl
  165. What: /sys/class/cxl/<card>/image_loaded (not in a guest)
  166. Date: September 2014
  167. Contact: linuxppc-dev@lists.ozlabs.org
  168. Description: read only
  169. Will return "user" or "factory" depending on the image loaded
  170. onto the card.
  171. Users: https://github.com/ibm-capi/libcxl
  172. What: /sys/class/cxl/<card>/load_image_on_perst (not in a guest)
  173. Date: December 2014
  174. Contact: linuxppc-dev@lists.ozlabs.org
  175. Description: read/write
  176. Valid entries are "none", "user", and "factory".
  177. "none" means PERST will not cause image to be loaded to the
  178. card. A power cycle is required to load the image.
  179. "none" could be useful for debugging because the trace arrays
  180. are preserved.
  181. "user" and "factory" means PERST will cause either the user or
  182. user or factory image to be loaded.
  183. Default is to reload on PERST whichever image the card has
  184. loaded.
  185. Users: https://github.com/ibm-capi/libcxl
  186. What: /sys/class/cxl/<card>/reset
  187. Date: October 2014
  188. Contact: linuxppc-dev@lists.ozlabs.org
  189. Description: write only
  190. Writing 1 will issue a PERST to card provided there are no
  191. contexts active on any one of the card AFUs. This may cause
  192. the card to reload the FPGA depending on load_image_on_perst.
  193. Writing -1 will do a force PERST irrespective of any active
  194. contexts on the card AFUs.
  195. Users: https://github.com/ibm-capi/libcxl
  196. What: /sys/class/cxl/<card>/perst_reloads_same_image (not in a guest)
  197. Date: July 2015
  198. Contact: linuxppc-dev@lists.ozlabs.org
  199. Description: read/write
  200. Trust that when an image is reloaded via PERST, it will not
  201. have changed.
  202. 0 = don't trust, the image may be different (default)
  203. 1 = trust that the image will not change.
  204. Users: https://github.com/ibm-capi/libcxl
  205. What: /sys/class/cxl/<card>/psl_timebase_synced
  206. Date: March 2016
  207. Contact: linuxppc-dev@lists.ozlabs.org
  208. Description: read only
  209. Returns 1 if the psl timebase register is synchronized
  210. with the core timebase register, 0 otherwise.
  211. Users: https://github.com/ibm-capi/libcxl
  212. What: /sys/class/cxl/<card>/tunneled_ops_supported
  213. Date: May 2018
  214. Contact: linuxppc-dev@lists.ozlabs.org
  215. Description: read only
  216. Returns 1 if tunneled operations are supported in capi mode,
  217. 0 otherwise.
  218. Users: https://github.com/ibm-capi/libcxl