Update documentation describing sysfs node that could help to
configure isolation strategy for users in the user space. And
describing sysfs node that could read the device isolated state.
Signed-off-by: Kai Ye <yekai13@xxxxxxxxxx>
---
Documentation/ABI/testing/sysfs-driver-uacce | 26 ++++++++++++++++++++
1 file changed, 26 insertions(+)
diff --git a/Documentation/ABI/testing/sysfs-driver-uacce b/Documentation/ABI/testing/sysfs-driver-uacce
index 08f2591138af..e09fd160d3fa 100644
--- a/Documentation/ABI/testing/sysfs-driver-uacce
+++ b/Documentation/ABI/testing/sysfs-driver-uacce
@@ -19,6 +19,32 @@ Contact: linux-accelerators@xxxxxxxxxxxxxxxx
Description: Available instances left of the device
Return -ENODEV if uacce_ops get_available_instances is not provided
+What: /sys/class/uacce/<dev_name>/isolate_strategy
+Date: Jul 2022
+KernelVersion: 6.0
+Contact: linux-accelerators@xxxxxxxxxxxxxxxx
+Description: (RW) Configure the frequency size for the hardware error
+ isolation strategy. This size is a configured integer value.
+ The default is 0. The maximum value is 65535. This value is a
+ threshold based on your driver strategies.
+
+ For example, in the hisilicon accelerator engine, first we will
+ time-stamp every slot AER error. Then check the AER error log
+ when the device AER error occurred. if the device slot AER error
+ count exceeds the preset the number of times in one hour, the
+ isolated state will be set to true. So the device will be
+ isolated. And the AER error log that exceed one hour will be
+ cleared. Of course, different strategies can be defined in
+ different drivers.
+
+What: /sys/class/uacce/<dev_name>/isolate
+Date: Jul 2022
+KernelVersion: 6.0
+Contact: linux-accelerators@xxxxxxxxxxxxxxxx
+Description: (R) A sysfs node that read the device isolated state. The value 1
+ means the device is unavailable. The 0 means the device is
+ available.
+
What: /sys/class/uacce/<dev_name>/algorithms
Date: Feb 2020
KernelVersion: 5.7
--
2.33.0
