From: Kai Ye <yekai13@huawei.com>
To: <gregkh@linuxfoundation.org>, <herbert@gondor.apana.org.au>
Cc: <linux-crypto@vger.kernel.org>, <linux-kernel@vger.kernel.org>,
<wangzhou1@hisilicon.com>, <yekai13@huawei.com>
Subject: [PATCH v5 2/3] Documentation: add a isolation strategy sysfs node for uacce
Date: Fri, 8 Jul 2022 15:08:19 +0800 [thread overview]
Message-ID: <20220708070820.43958-3-yekai13@huawei.com> (raw)
In-Reply-To: <20220708070820.43958-1-yekai13@huawei.com>
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@huawei.com>
---
Documentation/ABI/testing/sysfs-driver-uacce | 18 ++++++++++++++++++
1 file changed, 18 insertions(+)
diff --git a/Documentation/ABI/testing/sysfs-driver-uacce b/Documentation/ABI/testing/sysfs-driver-uacce
index 08f2591138af..a8056271a963 100644
--- a/Documentation/ABI/testing/sysfs-driver-uacce
+++ b/Documentation/ABI/testing/sysfs-driver-uacce
@@ -19,6 +19,24 @@ Contact: linux-accelerators@lists.ozlabs.org
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: 5.20
+Contact: linux-accelerators@lists.ozlabs.org
+Description: A sysfs node that used to configures the hardware error
+ isolation strategy. This strategy is a configured integer value.
+ The default is 0. The maximum value is 65535. This value
+ indicates the number of device slot resets per unit time
+ that your service can tolerate.
+
+What: /sys/class/uacce/<dev_name>/isolate
+Date: Jul 2022
+KernelVersion: 5.20
+Contact: linux-accelerators@lists.ozlabs.org
+Description: A sysfs node that read the device isolated state. The value 0
+ means that the device is working. The value 1 means that the
+ device has been isolated.
+
What: /sys/class/uacce/<dev_name>/algorithms
Date: Feb 2020
KernelVersion: 5.7
--
2.33.0
next prev parent reply other threads:[~2022-07-08 7:15 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-07-08 7:08 [PATCH v5 0/3] crypto: hisilicon - supports device isolation feature Kai Ye
2022-07-08 7:08 ` [PATCH v5 1/3] uacce: " Kai Ye
2022-07-08 7:28 ` Greg KH
2022-07-08 9:33 ` yekai(A)
2022-07-08 10:01 ` Greg KH
2022-07-08 7:08 ` Kai Ye [this message]
2022-07-08 7:30 ` [PATCH v5 2/3] Documentation: add a isolation strategy sysfs node for uacce Greg KH
2022-07-08 9:38 ` yekai(A)
2022-07-08 10:02 ` Greg KH
2022-07-08 7:30 ` Greg KH
2022-07-08 7:08 ` [PATCH v5 3/3] crypto: hisilicon/qm - defining the device isolation strategy Kai Ye
2022-07-08 7:35 ` Greg KH
2022-07-21 8:14 ` yekai(A)
2022-07-23 7:21 ` yekai(A)
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20220708070820.43958-3-yekai13@huawei.com \
--to=yekai13@huawei.com \
--cc=gregkh@linuxfoundation.org \
--cc=herbert@gondor.apana.org.au \
--cc=linux-crypto@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=wangzhou1@hisilicon.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®