From: "yekai (A)" <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>, <liulongfang@huawei.com>
Subject: Re: [PATCH v10 0/3] crypto: hisilicon - supports device isolation feature
Date: Fri, 9 Dec 2022 14:15:07 +0800 [thread overview]
Message-ID: <75ca78c7-1ca3-3e62-1175-5207ed9f5cf8@huawei.com> (raw)
In-Reply-To: <9b934709-2f74-7392-aab6-eb506ddcf708@huawei.com>
On 2022/11/25 16:49, yekai (A) wrote:
>
> On 2022/11/19 15:48, Kai Ye wrote:
>> 1、Add the uacce hardware error isolation interface. Hardware error
>> thresholds can be configured by sysfs node. User can get the hardware
>> isolated state by sysfs node.
>> 2、Defining the isolation strategy for uacce device by uacce sysfs node.
>> If the number of hardware errors exceeds the configured value, the
>> uacce device will not be available in user space.
>> 3、The ACC VF device use the PF device isolation strategy.
>>
>> changes v1->v2:
>> - deleted dev_to_uacce api.
>> - add vfs node doc.
>> - move uacce->ref to driver.
>> changes v2->v3:
>> - deleted some redundant code.
>> - use qm state instead of reference count.
>> - add null pointer check.
>> - isolate_strategy_read() instead of a copy.
>> changes v3->v4:
>> - modify a comment
>> changes v4->v5:
>> - use bool instead of atomic.
>> - isolation frequency instead of isolation command.
>> changes v5->v6:
>> - add is_visible in uacce.
>> - add the description of the isolation strategy file node.
>> changes v6->v7
>> - add an example for isolate_strategy in Documentation.
>> changes v7->v8
>> - update the correct date.
>> changes v8->v9
>> - move isolation strategy from qm to uacce.
>> changes v9->v10
>> - Go back to the v8 version of the solution.
>> - Modify some code according to suggestions.
>>
>> Kai Ye (3):
>> uacce: supports device isolation feature
>> Documentation: add the device isolation feature sysfs nodes for uacce
>> crypto: hisilicon/qm - define the device isolation strategy
>>
>> Documentation/ABI/testing/sysfs-driver-uacce | 18 ++
>> drivers/crypto/hisilicon/qm.c | 169 +++++++++++++++++--
>> drivers/misc/uacce/uacce.c | 50 ++++++
>> include/linux/hisi_acc_qm.h | 15 ++
>> include/linux/uacce.h | 12 ++
>> 5 files changed, 249 insertions(+), 15 deletions(-)
>>
> Hi Grek
>
> Just a friendly ping.
>
> Thanks
> Kai
Hi Greg KH
Could you help me to apply this patchset v10?
thanks
Kai
next prev parent reply other threads:[~2022-12-09 6:15 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-19 7:48 Kai Ye
2022-11-19 7:48 ` [PATCH v10 1/3] uacce: " Kai Ye
2022-11-19 7:48 ` [PATCH v10 2/3] Documentation: add the device isolation feature sysfs nodes for uacce Kai Ye
2022-11-19 7:48 ` [PATCH v10 3/3] crypto: hisilicon/qm - define the device isolation strategy Kai Ye
2022-12-11 6:16 ` Herbert Xu
2023-01-10 11:57 ` yekai (A)
[not found] ` <e1bb7612-2763-5a00-0e53-bad22fa167cf@huawei.com>
[not found] ` <9e3aa5d6-951c-afcd-5544-2056d63a087a@huawei.com>
2023-01-20 11:06 ` Greg KH
2022-11-25 8:49 ` [PATCH v10 0/3] crypto: hisilicon - supports device isolation feature yekai (A)
2022-12-09 6:15 ` yekai (A) [this message]
2022-12-09 15:32 ` Greg KH
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=75ca78c7-1ca3-3e62-1175-5207ed9f5cf8@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=liulongfang@huawei.com \
--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®