From: Greg KH <gregkh@linuxfoundation.org>
To: "yekai (A)" <yekai13@huawei.com>
Cc: herbert@gondor.apana.org.au, linux-crypto@vger.kernel.org,
linux-kernel@vger.kernel.org, wangzhou1@hisilicon.com,
liulongfang@huawei.com
Subject: Re: [PATCH v6 2/3] Documentation: add a isolation strategy sysfs node for uacce
Date: Mon, 1 Aug 2022 08:13:44 +0200 [thread overview]
Message-ID: <YudvGPbcegOZQlbE@kroah.com> (raw)
In-Reply-To: <901896fa-2acc-127c-a8ea-8143cda47b1b@huawei.com>
On Mon, Aug 01, 2022 at 10:20:27AM +0800, yekai (A) wrote:
>
>
> On 2022/7/30 19:06, Greg KH wrote:
> > On Sat, Jul 30, 2022 at 04:32:45PM +0800, Kai Ye wrote:
> >> 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 | 17 +++++++++++++++++
> >> 1 file changed, 17 insertions(+)
> >>
> >> diff --git a/Documentation/ABI/testing/sysfs-driver-uacce b/Documentation/ABI/testing/sysfs-driver-uacce
> >> index 08f2591138af..1601f9dac29c 100644
> >> --- a/Documentation/ABI/testing/sysfs-driver-uacce
> >> +++ b/Documentation/ABI/testing/sysfs-driver-uacce
> >> @@ -19,6 +19,23 @@ 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: (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 handling strategy.
> > what is a "driver handling strategy"? What exactly is this units in?
> > Any documentation for how to use this?
> >
> > thanks,
> >
> > greg k-h
> > .
> The unit is the number of times, also means frequency size.
> e.g.
> In the hisilicon acc 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 strategy can be defined in different drivers.
Ok, can you please explain this better here when you redo the patch
series?
thanks,
greg k-h
next prev parent reply other threads:[~2022-08-01 6:14 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-07-30 8:32 [PATCH v6 0/3] crypto: hisilicon - supports device isolation feature Kai Ye
2022-07-30 8:32 ` [PATCH v6 1/3] uacce: " Kai Ye
2022-07-30 8:32 ` [PATCH v6 2/3] Documentation: add a isolation strategy sysfs node for uacce Kai Ye
2022-07-30 11:06 ` Greg KH
2022-08-01 2:20 ` yekai (A)
2022-08-01 6:13 ` Greg KH [this message]
2022-08-01 9:25 ` yekai (A)
2022-07-30 8:32 ` [PATCH v6 3/3] crypto: hisilicon/qm - define the device isolation strategy Kai Ye
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=YudvGPbcegOZQlbE@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=herbert@gondor.apana.org.au \
--cc=linux-crypto@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=liulongfang@huawei.com \
--cc=wangzhou1@hisilicon.com \
--cc=yekai13@huawei.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