From: Greg KH <gregkh@linuxfoundation.org>
To: Kai Ye <yekai13@huawei.com>
Cc: herbert@gondor.apana.org.au, linux-crypto@vger.kernel.org,
linux-accelerators@lists.ozlabs.org,
linux-kernel@vger.kernel.org, linuxarm@huawei.com,
zhangfei.gao@linaro.org, wangzhou1@hisilicon.com
Subject: Re: [PATCH v2 1/3] uacce: supports device isolation feature
Date: Tue, 14 Jun 2022 14:42:55 +0200 [thread overview]
Message-ID: <YqiCT1HT/Y0BeiBf@kroah.com> (raw)
In-Reply-To: <20220614122943.1406-2-yekai13@huawei.com>
On Tue, Jun 14, 2022 at 08:29:38PM +0800, Kai Ye wrote:
> UACCE add the hardware error isolation API. Users can configure
> the error frequency threshold by this vfs node. This API interface
> certainly supports the configuration of user protocol strategy. Then
> parse it inside the device driver. UACCE only reports the device
> isolate state. When the error frequency is exceeded, the device
> will be isolated. The isolation strategy should be defined in each
> driver module.
>
> Signed-off-by: Kai Ye <yekai13@huawei.com>
> Reviewed-by: Zhou Wang <wangzhou1@hisilicon.com>
> ---
> drivers/misc/uacce/uacce.c | 37 +++++++++++++++++++++++++++++++++++++
> include/linux/uacce.h | 16 +++++++++++++---
> 2 files changed, 50 insertions(+), 3 deletions(-)
>
> diff --git a/drivers/misc/uacce/uacce.c b/drivers/misc/uacce/uacce.c
> index b6219c6bfb48..525623215132 100644
> --- a/drivers/misc/uacce/uacce.c
> +++ b/drivers/misc/uacce/uacce.c
> @@ -346,12 +346,47 @@ static ssize_t region_dus_size_show(struct device *dev,
> uacce->qf_pg_num[UACCE_QFRT_DUS] << PAGE_SHIFT);
> }
>
> +static ssize_t isolate_show(struct device *dev,
> + struct device_attribute *attr, char *buf)
> +{
> + struct uacce_device *uacce = to_uacce_device(dev);
> +
> + return sysfs_emit(buf, "%d\n", uacce->ops->get_isolate_state(uacce));
> +}
> +
> +static ssize_t isolate_strategy_show(struct device *dev,
> + struct device_attribute *attr, char *buf)
> +{
> + struct uacce_device *uacce = to_uacce_device(dev);
> +
> + return sysfs_emit(buf, "%s\n", uacce->isolate_strategy);
> +}
> +
> +static ssize_t isolate_strategy_store(struct device *dev,
> + struct device_attribute *attr,
> + const char *buf, size_t count)
> +{
> + struct uacce_device *uacce = to_uacce_device(dev);
> + int ret;
> +
> + if (!buf || sizeof(buf) > UACCE_MAX_ISOLATE_STRATEGY_LEN)
> + return -EINVAL;
> +
> + memcpy(uacce->isolate_strategy, buf, strlen(buf));
> +
> + ret = uacce->ops->isolate_strategy_write(uacce, buf);
> +
> + return ret ? ret : count;
> +}
> +
> static DEVICE_ATTR_RO(api);
> static DEVICE_ATTR_RO(flags);
> static DEVICE_ATTR_RO(available_instances);
> static DEVICE_ATTR_RO(algorithms);
> static DEVICE_ATTR_RO(region_mmio_size);
> static DEVICE_ATTR_RO(region_dus_size);
> +static DEVICE_ATTR_RO(isolate);
> +static DEVICE_ATTR_RW(isolate_strategy);
>
> static struct attribute *uacce_dev_attrs[] = {
> &dev_attr_api.attr,
> @@ -360,6 +395,8 @@ static struct attribute *uacce_dev_attrs[] = {
> &dev_attr_algorithms.attr,
> &dev_attr_region_mmio_size.attr,
> &dev_attr_region_dus_size.attr,
> + &dev_attr_isolate.attr,
> + &dev_attr_isolate_strategy.attr,
> NULL,
> };
>
> diff --git a/include/linux/uacce.h b/include/linux/uacce.h
> index 48e319f40275..0f7668bfa645 100644
> --- a/include/linux/uacce.h
> +++ b/include/linux/uacce.h
> @@ -8,6 +8,7 @@
> #define UACCE_NAME "uacce"
> #define UACCE_MAX_REGION 2
> #define UACCE_MAX_NAME_SIZE 64
> +#define UACCE_MAX_ISOLATE_STRATEGY_LEN 256
So it's a random string of characters? What format?
>
> struct uacce_queue;
> struct uacce_device;
> @@ -30,6 +31,8 @@ struct uacce_qfile_region {
> * @is_q_updated: check whether the task is finished
> * @mmap: mmap addresses of queue to user space
> * @ioctl: ioctl for user space users of the queue
> + * @get_isolate_state: get the device state after set the isolate strategy
> + * @isolate_strategy_store: stored the isolate strategy to the device
> */
> struct uacce_ops {
> int (*get_available_instances)(struct uacce_device *uacce);
> @@ -43,6 +46,8 @@ struct uacce_ops {
> struct uacce_qfile_region *qfr);
> long (*ioctl)(struct uacce_queue *q, unsigned int cmd,
> unsigned long arg);
> + enum uacce_dev_state (*get_isolate_state)(struct uacce_device *uacce);
> + int (*isolate_strategy_write)(struct uacce_device *uacce, const char *buf);
Length of the buffer?
> };
>
> /**
> @@ -57,6 +62,12 @@ struct uacce_interface {
> const struct uacce_ops *ops;
> };
>
> +enum uacce_dev_state {
> + UACCE_DEV_ERR = -1,
> + UACCE_DEV_NORMAL,
> + UACCE_DEV_ISOLATE,
> +};
> +
> enum uacce_q_state {
> UACCE_Q_ZOMBIE = 0,
> UACCE_Q_INIT,
> @@ -117,6 +128,7 @@ struct uacce_device {
> struct list_head queues;
> struct mutex queues_lock;
> struct inode *inode;
> + char isolate_strategy[UACCE_MAX_ISOLATE_STRATEGY_LEN];
> };
>
> #if IS_ENABLED(CONFIG_UACCE)
> @@ -125,7 +137,7 @@ struct uacce_device *uacce_alloc(struct device *parent,
> struct uacce_interface *interface);
> int uacce_register(struct uacce_device *uacce);
> void uacce_remove(struct uacce_device *uacce);
> -
> +struct uacce_device *dev_to_uacce(struct device *dev);
Why is this moved to the .h file yet the function is not exported?
thanks,
greg k-h
next prev parent reply other threads:[~2022-06-14 12:44 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-14 12:29 [PATCH v2 0/3] crypto: hisilicon - supports device isolation feature Kai Ye
2022-06-14 12:29 ` [PATCH v2 1/3] uacce: " Kai Ye
2022-06-14 12:42 ` Greg KH [this message]
2022-06-15 8:52 ` Jonathan Cameron
2022-06-15 9:06 ` yekai(A)
2022-06-14 12:29 ` [PATCH v2 2/3] Documentation: add a isolation strategy vfs node for uacce Kai Ye
2022-06-14 12:41 ` Greg KH
2022-06-15 8:48 ` Jonathan Cameron
2022-06-15 9:18 ` yekai(A)
2022-06-14 12:29 ` [PATCH v2 3/3] crypto: hisilicon/qm - defining the device isolation strategy Kai Ye
2022-06-14 12:43 ` Greg KH
2022-06-14 13:24 ` yekai(A)
2022-06-14 13:29 ` Greg KH
2022-06-15 9:10 ` yekai(A)
2022-06-14 14:12 ` Zhangfei Gao
2022-06-15 13:02 ` Jonathan Cameron
2022-06-16 1:33 ` yekai(A)
2022-06-16 13:45 ` Jonathan Cameron
2022-06-17 2:07 ` yekai(A)
2022-06-14 12:29 ` [PATCH 1/3] uacce: supports device isolation feature Kai Ye
2022-06-14 14:14 ` Zhangfei Gao
2022-06-15 1:07 ` yekai(A)
2022-06-14 12:29 ` [PATCH 2/3] Documentation: add a isolation strategy vfs node for uacce Kai Ye
2022-06-14 12:29 ` [PATCH 3/3] crypto: hisilicon/qm - defining the device isolation strategy Kai Ye
-- strict thread matches above, loose matches on Subject: below --
2022-06-14 12:23 [PATCH v2 0/3] crypto: hisilicon - supports device isolation feature Kai Ye
2022-06-14 12:23 ` [PATCH v2 1/3] uacce: " 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=YqiCT1HT/Y0BeiBf@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=herbert@gondor.apana.org.au \
--cc=linux-accelerators@lists.ozlabs.org \
--cc=linux-crypto@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linuxarm@huawei.com \
--cc=wangzhou1@hisilicon.com \
--cc=yekai13@huawei.com \
--cc=zhangfei.gao@linaro.org \
/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