linux-kernel - [PATCH 0/2] crypto: hisilicon - supports device isolation feature

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite for Android: free password hash cracker in your pocket

[<prev] [next>] [thread-next>] [day] [month] [year] [list]

Message-ID: <20220611070808.49219-1-yekai13@huawei.com>
Date:   Sat, 11 Jun 2022 15:08:06 +0800
From:   Kai Ye <yekai13@...wei.com>
To:     <gregkh@...uxfoundation.org>,
        <linux-accelerators@...ts.ozlabs.org>,
        <linux-kernel@...r.kernel.org>, <linuxarm@...wei.com>,
        <zhangfei.gao@...aro.org>, <wangzhou1@...ilicon.com>,
        <yekai13@...wei.com>
Subject: [PATCH 0/2] crypto: hisilicon - supports device isolation feature

Add the hardware error isolation feature for ACC. Defines a driver debugfs
node that used to configures the hardware error frequency. When the error
frequency is exceeded, the device will be isolated. The isolation strategy 
can be defined in each driver module. e.g. Defining the isolation strategy
for ACC, if the AER error frequency exceeds the value of setting for a 
certain period of time, The device will not be available in user space. The
VF device use the PF device isolation strategy. as well as the isolation 
strategy should not be set during device use.

Kai Ye (2):
  uacce: supports device isolation feature
  crypto: hisilicon/qm - defining the device isolation strategy

 drivers/crypto/hisilicon/qm.c | 149 +++++++++++++++++++++++++++++++---
 drivers/misc/uacce/uacce.c    |  76 +++++++++++++++++
 include/linux/hisi_acc_qm.h   |   8 ++
 include/linux/uacce.h         |  21 ++++-
 4 files changed, 241 insertions(+), 13 deletions(-)

-- 
2.33.0