sysfs-class-cxl 9.4 KB

123456789101112131415161718192021222324252627282930313233343536373839404142434445464748495051525354555657585960616263646566676869707172737475767778798081828384858687888990919293949596979899100101102103104105106107108109110111112113114115116117118119120121122123124125126127128129130131132133134135136137138139140141142143144145146147148149150151152153154155156157158159160161162163164165166167168169170171172173174175176177178179180181182183184185186187188189190191192193194195196197198199200201202203204205206207208209210211212213214215216217218219220221222223224225226227228229230231232233234235
  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. Possible values:
  62. none: No prefaulting (default)
  63. work_element_descriptor: Treat the work element
  64. descriptor as an effective address and
  65. prefault what it points to.
  66. all: all segments process calling START_WORK maps.
  67. Users: https://github.com/ibm-capi/libcxl
  68. What: /sys/class/cxl/<afu>/reset
  69. Date: September 2014
  70. Contact: linuxppc-dev@lists.ozlabs.org
  71. Description: write only
  72. Writing 1 here will reset the AFU provided there are not
  73. contexts active on the AFU.
  74. Users: https://github.com/ibm-capi/libcxl
  75. What: /sys/class/cxl/<afu>/api_version
  76. Date: September 2014
  77. Contact: linuxppc-dev@lists.ozlabs.org
  78. Description: read only
  79. Decimal value of the current version of the kernel/user API.
  80. Users: https://github.com/ibm-capi/libcxl
  81. What: /sys/class/cxl/<afu>/api_version_compatible
  82. Date: September 2014
  83. Contact: linuxppc-dev@lists.ozlabs.org
  84. Description: read only
  85. Decimal value of the the lowest version of the userspace API
  86. this this kernel supports.
  87. Users: https://github.com/ibm-capi/libcxl
  88. AFU configuration records (eg. /sys/class/cxl/afu0.0/cr0):
  89. An AFU may optionally export one or more PCIe like configuration records, known
  90. as AFU configuration records, which will show up here (if present).
  91. What: /sys/class/cxl/<afu>/cr<config num>/vendor
  92. Date: February 2015
  93. Contact: linuxppc-dev@lists.ozlabs.org
  94. Description: read only
  95. Hexadecimal value of the vendor ID found in this AFU
  96. configuration record.
  97. Users: https://github.com/ibm-capi/libcxl
  98. What: /sys/class/cxl/<afu>/cr<config num>/device
  99. Date: February 2015
  100. Contact: linuxppc-dev@lists.ozlabs.org
  101. Description: read only
  102. Hexadecimal value of the device ID found in this AFU
  103. configuration record.
  104. Users: https://github.com/ibm-capi/libcxl
  105. What: /sys/class/cxl/<afu>/cr<config num>/class
  106. Date: February 2015
  107. Contact: linuxppc-dev@lists.ozlabs.org
  108. Description: read only
  109. Hexadecimal value of the class code found in this AFU
  110. configuration record.
  111. Users: https://github.com/ibm-capi/libcxl
  112. What: /sys/class/cxl/<afu>/cr<config num>/config
  113. Date: February 2015
  114. Contact: linuxppc-dev@lists.ozlabs.org
  115. Description: read only
  116. This binary file provides raw access to the AFU configuration
  117. record. The format is expected to match the either the standard
  118. or extended configuration space defined by the PCIe
  119. specification.
  120. Users: https://github.com/ibm-capi/libcxl
  121. Master contexts (eg. /sys/class/cxl/afu0.0m)
  122. What: /sys/class/cxl/<afu>m/mmio_size
  123. Date: September 2014
  124. Contact: linuxppc-dev@lists.ozlabs.org
  125. Description: read only
  126. Decimal value of the size of the MMIO space that may be mmaped
  127. by userspace. This includes all slave contexts space also.
  128. Users: https://github.com/ibm-capi/libcxl
  129. What: /sys/class/cxl/<afu>m/pp_mmio_len
  130. Date: September 2014
  131. Contact: linuxppc-dev@lists.ozlabs.org
  132. Description: read only
  133. Decimal value of the Per Process MMIO space length.
  134. Users: https://github.com/ibm-capi/libcxl
  135. What: /sys/class/cxl/<afu>m/pp_mmio_off
  136. Date: September 2014
  137. Contact: linuxppc-dev@lists.ozlabs.org
  138. Description: read only
  139. Decimal value of the Per Process MMIO space offset.
  140. Users: https://github.com/ibm-capi/libcxl
  141. Card info (eg. /sys/class/cxl/card0)
  142. What: /sys/class/cxl/<card>/caia_version
  143. Date: September 2014
  144. Contact: linuxppc-dev@lists.ozlabs.org
  145. Description: read only
  146. Identifies the CAIA Version the card implements.
  147. Users: https://github.com/ibm-capi/libcxl
  148. What: /sys/class/cxl/<card>/psl_revision
  149. Date: September 2014
  150. Contact: linuxppc-dev@lists.ozlabs.org
  151. Description: read only
  152. Identifies the revision level of the PSL.
  153. Users: https://github.com/ibm-capi/libcxl
  154. What: /sys/class/cxl/<card>/base_image
  155. Date: September 2014
  156. Contact: linuxppc-dev@lists.ozlabs.org
  157. Description: read only
  158. Identifies the revision level of the base image for devices
  159. that support loadable PSLs. For FPGAs this field identifies
  160. the image contained in the on-adapter flash which is loaded
  161. during the initial program load.
  162. Users: https://github.com/ibm-capi/libcxl
  163. What: /sys/class/cxl/<card>/image_loaded
  164. Date: September 2014
  165. Contact: linuxppc-dev@lists.ozlabs.org
  166. Description: read only
  167. Will return "user" or "factory" depending on the image loaded
  168. onto the card.
  169. Users: https://github.com/ibm-capi/libcxl
  170. What: /sys/class/cxl/<card>/load_image_on_perst
  171. Date: December 2014
  172. Contact: linuxppc-dev@lists.ozlabs.org
  173. Description: read/write
  174. Valid entries are "none", "user", and "factory".
  175. "none" means PERST will not cause image to be loaded to the
  176. card. A power cycle is required to load the image.
  177. "none" could be useful for debugging because the trace arrays
  178. are preserved.
  179. "user" and "factory" means PERST will cause either the user or
  180. user or factory image to be loaded.
  181. Default is to reload on PERST whichever image the card has
  182. loaded.
  183. Users: https://github.com/ibm-capi/libcxl
  184. What: /sys/class/cxl/<card>/reset
  185. Date: October 2014
  186. Contact: linuxppc-dev@lists.ozlabs.org
  187. Description: write only
  188. Writing 1 will issue a PERST to card which may cause the card
  189. to reload the FPGA depending on load_image_on_perst.
  190. Users: https://github.com/ibm-capi/libcxl
  191. What: /sys/class/cxl/<card>/perst_reloads_same_image
  192. Date: July 2015
  193. Contact: linuxppc-dev@lists.ozlabs.org
  194. Description: read/write
  195. Trust that when an image is reloaded via PERST, it will not
  196. have changed.
  197. 0 = don't trust, the image may be different (default)
  198. 1 = trust that the image will not change.
  199. Users: https://github.com/ibm-capi/libcxl