sysfs-class-mic.txt 6.4 KB

123456789101112131415161718192021222324252627282930313233343536373839404142434445464748495051525354555657585960616263646566676869707172737475767778798081828384858687888990919293949596979899100101102103104105106107108109110111112113114115116117118119120121122123124125126127128129130131132133134135136137138139140141142143144145146147148149150151152153154155156157158159160161162163164165166
  1. What: /sys/class/mic/
  2. Date: October 2013
  3. KernelVersion: 3.13
  4. Contact: Sudeep Dutt <sudeep.dutt@intel.com>
  5. Description:
  6. The mic class directory belongs to Intel MIC devices and
  7. provides information per MIC device. An Intel MIC device is a
  8. PCIe form factor add-in Coprocessor card based on the Intel Many
  9. Integrated Core (MIC) architecture that runs a Linux OS.
  10. What: /sys/class/mic/mic(x)
  11. Date: October 2013
  12. KernelVersion: 3.13
  13. Contact: Sudeep Dutt <sudeep.dutt@intel.com>
  14. Description:
  15. The directories /sys/class/mic/mic0, /sys/class/mic/mic1 etc.,
  16. represent MIC devices (0,1,..etc). Each directory has
  17. information specific to that MIC device.
  18. What: /sys/class/mic/mic(x)/family
  19. Date: October 2013
  20. KernelVersion: 3.13
  21. Contact: Sudeep Dutt <sudeep.dutt@intel.com>
  22. Description:
  23. Provides information about the Coprocessor family for an Intel
  24. MIC device. For example - "x100"
  25. What: /sys/class/mic/mic(x)/stepping
  26. Date: October 2013
  27. KernelVersion: 3.13
  28. Contact: Sudeep Dutt <sudeep.dutt@intel.com>
  29. Description:
  30. Provides information about the silicon stepping for an Intel
  31. MIC device. For example - "A0" or "B0"
  32. What: /sys/class/mic/mic(x)/state
  33. Date: October 2013
  34. KernelVersion: 3.13
  35. Contact: Sudeep Dutt <sudeep.dutt@intel.com>
  36. Description:
  37. When read, this entry provides the current state of an Intel
  38. MIC device in the context of the card OS. Possible values that
  39. will be read are:
  40. "ready" - The MIC device is ready to boot the card OS. On
  41. reading this entry after an OSPM resume, a "boot" has to be
  42. written to this entry if the card was previously shutdown
  43. during OSPM suspend.
  44. "booting" - The MIC device has initiated booting a card OS.
  45. "online" - The MIC device has completed boot and is online
  46. "shutting_down" - The card OS is shutting down.
  47. "resetting" - A reset has been initiated for the MIC device
  48. "reset_failed" - The MIC device has failed to reset.
  49. When written, this sysfs entry triggers different state change
  50. operations depending upon the current state of the card OS.
  51. Acceptable values are:
  52. "boot" - Boot the card OS image specified by the combination
  53. of firmware, ramdisk, cmdline and bootmode
  54. sysfs entries.
  55. "reset" - Initiates device reset.
  56. "shutdown" - Initiates card OS shutdown.
  57. What: /sys/class/mic/mic(x)/shutdown_status
  58. Date: October 2013
  59. KernelVersion: 3.13
  60. Contact: Sudeep Dutt <sudeep.dutt@intel.com>
  61. Description:
  62. An Intel MIC device runs a Linux OS during its operation. This
  63. OS can shutdown because of various reasons. When read, this
  64. entry provides the status on why the card OS was shutdown.
  65. Possible values are:
  66. "nop" - shutdown status is not applicable, when the card OS is
  67. "online"
  68. "crashed" - Shutdown because of a HW or SW crash.
  69. "halted" - Shutdown because of a halt command.
  70. "poweroff" - Shutdown because of a poweroff command.
  71. "restart" - Shutdown because of a restart command.
  72. What: /sys/class/mic/mic(x)/cmdline
  73. Date: October 2013
  74. KernelVersion: 3.13
  75. Contact: Sudeep Dutt <sudeep.dutt@intel.com>
  76. Description:
  77. An Intel MIC device runs a Linux OS during its operation. Before
  78. booting this card OS, it is possible to pass kernel command line
  79. options to configure various features in it, similar to
  80. self-bootable machines. When read, this entry provides
  81. information about the current kernel command line options set to
  82. boot the card OS. This entry can be written to change the
  83. existing kernel command line options. Typically, the user would
  84. want to read the current command line options, append new ones
  85. or modify existing ones and then write the whole kernel command
  86. line back to this entry.
  87. What: /sys/class/mic/mic(x)/firmware
  88. Date: October 2013
  89. KernelVersion: 3.13
  90. Contact: Sudeep Dutt <sudeep.dutt@intel.com>
  91. Description:
  92. When read, this sysfs entry provides the path name under
  93. /lib/firmware/ where the firmware image to be booted on the
  94. card can be found. The entry can be written to change the
  95. firmware image location under /lib/firmware/.
  96. What: /sys/class/mic/mic(x)/ramdisk
  97. Date: October 2013
  98. KernelVersion: 3.13
  99. Contact: Sudeep Dutt <sudeep.dutt@intel.com>
  100. Description:
  101. When read, this sysfs entry provides the path name under
  102. /lib/firmware/ where the ramdisk image to be used during card
  103. OS boot can be found. The entry can be written to change
  104. the ramdisk image location under /lib/firmware/.
  105. What: /sys/class/mic/mic(x)/bootmode
  106. Date: October 2013
  107. KernelVersion: 3.13
  108. Contact: Sudeep Dutt <sudeep.dutt@intel.com>
  109. Description:
  110. When read, this sysfs entry provides the current bootmode for
  111. the card. This sysfs entry can be written with the following
  112. valid strings:
  113. a) linux - Boot a Linux image.
  114. b) flash - Boot an image for flash updates.
  115. What: /sys/class/mic/mic(x)/log_buf_addr
  116. Date: October 2013
  117. KernelVersion: 3.13
  118. Contact: Sudeep Dutt <sudeep.dutt@intel.com>
  119. Description:
  120. An Intel MIC device runs a Linux OS during its operation. For
  121. debugging purpose and early kernel boot messages, the user can
  122. access the card OS log buffer via debugfs. When read, this entry
  123. provides the kernel virtual address of the buffer where the card
  124. OS log buffer can be read. This entry is written by the host
  125. configuration daemon to set the log buffer address. The correct
  126. log buffer address to be written can be found in the System.map
  127. file of the card OS.
  128. What: /sys/class/mic/mic(x)/log_buf_len
  129. Date: October 2013
  130. KernelVersion: 3.13
  131. Contact: Sudeep Dutt <sudeep.dutt@intel.com>
  132. Description:
  133. An Intel MIC device runs a Linux OS during its operation. For
  134. debugging purpose and early kernel boot messages, the user can
  135. access the card OS log buffer via debugfs. When read, this entry
  136. provides the kernel virtual address where the card OS log buffer
  137. length can be read. This entry is written by host configuration
  138. daemon to set the log buffer length address. The correct log
  139. buffer length address to be written can be found in the
  140. System.map file of the card OS.
  141. What: /sys/class/mic/mic(x)/heartbeat_enable
  142. Date: March 2015
  143. KernelVersion: 3.20
  144. Contact: Ashutosh Dixit <ashutosh.dixit@intel.com>
  145. Description:
  146. The MIC drivers detect and inform user space about card crashes
  147. via a heartbeat mechanism (see the description of
  148. shutdown_status above). User space can turn off this
  149. notification by setting heartbeat_enable to 0 and enable it by
  150. setting this entry to 1. If this notification is disabled it is
  151. the responsibility of user space to detect card crashes via
  152. alternative means such as a network ping. This setting is
  153. enabled by default.