January 2023 - Acc - mailweb.openeuler.org

Fwd: S390 testing for IOMMUFD
by Zhangfei Gao 02 Feb '23

02 Feb '23

-------- Forwarded Message -------- Subject: S390 testing for IOMMUFD Date: Mon, 7 Nov 2022 21:09:02 -0400 From: Jason Gunthorpe <jgg(a)nvidia.com> To: Cornelia Huck <cohuck(a)redhat.com>, Eric Farman <farman(a)linux.ibm.com>, Matthew Rosato <mjrosato(a)linux.ibm.com>, Niklas Schnelle <schnelle(a)linux.ibm.com>, Tony Krowiak <akrowiak(a)linux.ibm.com>, Halil Pasic <pasic(a)linux.ibm.com>, Jason Herne <jjherne(a)linux.ibm.com>, linux-s390(a)vger.kernel.org CC: iommu(a)lists.linux.dev, Kevin Tian <kevin.tian(a)intel.com>, Alex Williamson <alex.williamson(a)redhat.com>, kvm(a)vger.kernel.org, Lu Baolu <baolu.lu(a)linux.intel.com>, Nicolin Chen <nicolinc(a)nvidia.com> On Mon, Nov 07, 2022 at 08:48:53PM -0400, Jason Gunthorpe wrote: > [ > This has been in linux-next for a little while now, and we've completed > the syzkaller run. 1300 hours of CPU time have been invested since the > last report with no improvement in coverage or new detections. syzkaller > coverage reached 69%(75%), and review of the misses show substantial > amounts are WARN_ON's and other debugging which are not expected to be > covered. > ] > > iommufd is the user API to control the IOMMU subsystem as it relates to > managing IO page tables that point at user space memory. [chop cc list] s390 mdev maintainers, Can I ask your help to test this with the two S390 mdev drivers? Now that gvt is passing and we've covered alot of the QA ground it is a good time to run it. Take the branch from here: https://git.kernel.org/pub/scm/linux/kernel/git/jgg/iommufd.git/log/?h=for-… And build the kernel with CONFIG_VFIO_CONTAINER=n CONFIG_IOMMUFD=y CONFIG_IOMMUFD_VFIO_CONTAINER=y And your existing stuff should work with iommufd providing the iommu support to vfio. There will be a dmesg confirming this. Let me know if there are any problems! If I recall there was some desire from the S390 platform team to start building on iommufd to create some vIOMMU acceleration for S390 guests, this is a necessary first step. Thanks, Jason

3 2

DOCUMENTS SENT VIA ONEDRIVE
by acc 30 Jan '23

30 Jan '23

1 0

[PATCH] dh: cleanup redundant macro definition
by Zhiqi Song 19 Jan '23

19 Jan '23

Remove duplicated definition of CTX_MODE_NUM. Signed-off-by: Zhiqi Song <songzhiqi1(a)huawei.com> --- src/uadk_dh.c | 1 - 1 file changed, 1 deletion(-) diff --git a/src/uadk_dh.c b/src/uadk_dh.c index 6065160..a14d215 100644 --- a/src/uadk_dh.c +++ b/src/uadk_dh.c @@ -39,7 +39,6 @@ #define CHAR_BIT_SIZE 3 #define DH_PARAMS_CNT 3 #define CTX_MODE_NUM 2 -#define CTX_MODE_NUM 2 #define UN_SET 0 #define IS_SET 1 #define CTX_ASYNC 1 -- 2.30.0

1 2

加速库技术例会
by openEuler conference 18 Jan '23

18 Jan '23

您好！ sig-AccLib SIG 邀请您参加 2023-01-18 11:00 召开的Zoom会议会议主题：加速库技术例会会议内容： zoom会议，ID: 91879279131 固定的会议链接：https://linaro-org.zoom.us/j/91879279131 1、进展讨论 2、自由讨论会议链接：https://us06web.zoom.us/j/89073010256?pwd=TTJWM1l3RS95ZHVabVVVVzk3eENEQT09 会议纪要：https://etherpad.openeuler.org/p/sig-AccLib-meetings 温馨提醒：建议接入会议后修改参会人的姓名，也可以使用您在gitee.com的ID 更多资讯尽在：https://openeuler.org/zh/ Hello! openEuler sig-AccLib SIG invites you to attend the Zoom conference will be held at 2023-01-18 11:00, The subject of the conference is 加速库技术例会, Summary: zoom会议，ID: 91879279131 固定的会议链接：https://linaro-org.zoom.us/j/91879279131 1、进展讨论 2、自由讨论 You can join the meeting at https://us06web.zoom.us/j/89073010256?pwd=TTJWM1l3RS95ZHVabVVVVzk3eENEQT09. Add topics at https://etherpad.openeuler.org/p/sig-AccLib-meetings. Note: You are advised to change the participant name after joining the conference or use your ID at gitee.com. More information: https://openeuler.org/en/

1 0

读书很重要！！！
by Servicentro 248 Tepatitan Express 18 Jan '23

18 Jan '23

这是我现在唯一可以联系你的方式，我希望你对此非常小心，并保守这个秘密，直到我腾出空间让我们看到。你不需要知道我是谁或我来自哪里。我知道这听起来可能会让您感到非常惊讶，但情况就是这样。我已经提前支付了一些赎金以解雇你，原因是我的雇主向我列出的一些原因。我相信这是一个你称之为朋友的人；我已经密切关注了您一段时间，发现您对他对您的指控是清白的。不要联系警察或试图将此副本发送给他们，因为如果你这样做，我会知道，我会被迫去做我得到报酬的事情。此外，这是我第一次在工作中背叛。我可怜你，所以我下定决心要帮助你，如果你愿意帮助自己。现在听着，我会安排我们面对面见面，但在那之前，我需要在明天结束前通过比特币地址支付 10,000 美元。这是为了让我在给你信息时离开城镇。比特币钱包：bc1qez55j3he8tvylca2e3su3eugxv2lpksxexzer4 我会去你家，或者你决定我们在哪里见面；我再说一遍，不要安排警察，如果你玩得很辛苦，它会延伸到你的家人。不设置任何摄像头遮挡我们或设置任何磁带记录我们的谈话；我的雇主现在在我的控制之下。付款细节将提供给你先支付 5,000 美元的部分付款，这将作为你准备好合作的保证，然后我将发送一份包含他要求我终止你的视频磁带的副本将有足够的证据让你在他雇用另一个人做这份工作之前对他采取任何法律行动。收到磁带后，您将支付 5,000 美元的余额。警告; 不要联系警察，确保在晚上 7.30 之后呆在室内，直到整件事得到解决，如果你忽视这些警告中的任何一个，你将受到责备。你没有太多时间，所以马上回我注意：我会建议你把这个留给自己，即使是朋友或家人也不应该知道，因为它可能是他们中的一员。 [cid:image41065f.GIF@9e62b825.4f8d80b1] Servicentro 248 Tepatitan Express Servicentro servicentro248(a)officedepot.com.mx [cid:image01cca7.JPG@be6c6496.4ea781cb] ________________________________ Este correo electrónico (incluyendo cualquier archivo adjunto) puede contener información privada, confidencial o protegida. Si recibió este correo electrónico por error, por favor elimínelo del sistema sin copiarlo y notifique por correo electrónico al remitente para que nuestros registros puedan ser corregidos. This e-mail (including any attachments) may contain information that is private, confidential or protected. If you received this e-mail in error, please delete it from your system without copying it and notifiy sender by reply e-mail, so that our records can be corrected.

1 0

读书很重要！！！
by Servicentro 248 Tepatitan Express 18 Jan '23

18 Jan '23

这是我现在唯一可以联系你的方式，我希望你对此非常小心，并保守这个秘密，直到我腾出空间让我们看到。你不需要知道我是谁或我来自哪里。我知道这听起来可能会让您感到非常惊讶，但情况就是这样。我已经提前支付了一些赎金以解雇你，原因是我的雇主向我列出的一些原因。我相信这是一个你称之为朋友的人；我已经密切关注了您一段时间，发现您对他对您的指控是清白的。不要联系警察或试图将此副本发送给他们，因为如果你这样做，我会知道，我会被迫去做我得到报酬的事情。此外，这是我第一次在工作中背叛。我可怜你，所以我下定决心要帮助你，如果你愿意帮助自己。现在听着，我会安排我们面对面见面，但在那之前，我需要在明天结束前通过比特币地址支付 10,000 美元。这是为了让我在给你信息时离开城镇。比特币钱包：bc1qez55j3he8tvylca2e3su3eugxv2lpksxexzer4 我会去你家，或者你决定我们在哪里见面；我再说一遍，不要安排警察，如果你玩得很辛苦，它会延伸到你的家人。不设置任何摄像头遮挡我们或设置任何磁带记录我们的谈话；我的雇主现在在我的控制之下。付款细节将提供给你先支付 5,000 美元的部分付款，这将作为你准备好合作的保证，然后我将发送一份包含他要求我终止你的视频磁带的副本将有足够的证据让你在他雇用另一个人做这份工作之前对他采取任何法律行动。收到磁带后，您将支付 5,000 美元的余额。警告; 不要联系警察，确保在晚上 7.30 之后呆在室内，直到整件事得到解决，如果你忽视这些警告中的任何一个，你将受到责备。你没有太多时间，所以马上回我注意：我会建议你把这个留给自己，即使是朋友或家人也不应该知道，因为它可能是他们中的一员。 [cid:imagef4b717.GIF@a439c5d5.4fb67f8b] Servicentro 248 Tepatitan Express Servicentro servicentro248(a)officedepot.com.mx [cid:imageb979d7.JPG@f137c011.4aa5ac27] ________________________________ Este correo electrónico (incluyendo cualquier archivo adjunto) puede contener información privada, confidencial o protegida. Si recibió este correo electrónico por error, por favor elimínelo del sistema sin copiarlo y notifique por correo electrónico al remitente para que nuestros registros puedan ser corregidos. This e-mail (including any attachments) may contain information that is private, confidential or protected. If you received this e-mail in error, please delete it from your system without copying it and notifiy sender by reply e-mail, so that our records can be corrected.

1 0

读书很重要！！！
by Servicentro 248 Tepatitan Express 18 Jan '23

18 Jan '23

这是我现在唯一可以联系你的方式，我希望你对此非常小心，并保守这个秘密，直到我腾出空间让我们看到。你不需要知道我是谁或我来自哪里。我知道这听起来可能会让您感到非常惊讶，但情况就是这样。我已经提前支付了一些赎金以解雇你，原因是我的雇主向我列出的一些原因。我相信这是一个你称之为朋友的人；我已经密切关注了您一段时间，发现您对他对您的指控是清白的。不要联系警察或试图将此副本发送给他们，因为如果你这样做，我会知道，我会被迫去做我得到报酬的事情。此外，这是我第一次在工作中背叛。我可怜你，所以我下定决心要帮助你，如果你愿意帮助自己。现在听着，我会安排我们面对面见面，但在那之前，我需要在明天结束前通过比特币地址支付 10,000 美元。这是为了让我在给你信息时离开城镇。比特币钱包：bc1qez55j3he8tvylca2e3su3eugxv2lpksxexzer4 我会去你家，或者你决定我们在哪里见面；我再说一遍，不要安排警察，如果你玩得很辛苦，它会延伸到你的家人。不设置任何摄像头遮挡我们或设置任何磁带记录我们的谈话；我的雇主现在在我的控制之下。付款细节将提供给你先支付 5,000 美元的部分付款，这将作为你准备好合作的保证，然后我将发送一份包含他要求我终止你的视频磁带的副本将有足够的证据让你在他雇用另一个人做这份工作之前对他采取任何法律行动。收到磁带后，您将支付 5,000 美元的余额。警告; 不要联系警察，确保在晚上 7.30 之后呆在室内，直到整件事得到解决，如果你忽视这些警告中的任何一个，你将受到责备。你没有太多时间，所以马上回我注意：我会建议你把这个留给自己，即使是朋友或家人也不应该知道，因为它可能是他们中的一员。 [cid:imagede8fbe.GIF@751ab1a8.4186e1ba] Servicentro 248 Tepatitan Express Servicentro servicentro248(a)officedepot.com.mx [cid:imagedde1dd.JPG@51810080.469f85c5] ________________________________ Este correo electrónico (incluyendo cualquier archivo adjunto) puede contener información privada, confidencial o protegida. Si recibió este correo electrónico por error, por favor elimínelo del sistema sin copiarlo y notifique por correo electrónico al remitente para que nuestros registros puedan ser corregidos. This e-mail (including any attachments) may contain information that is private, confidential or protected. If you received this e-mail in error, please delete it from your system without copying it and notifiy sender by reply e-mail, so that our records can be corrected.

1 0

读书很重要！！！
by Servicentro 248 Tepatitan Express 18 Jan '23

18 Jan '23

这是我现在唯一可以联系你的方式，我希望你对此非常小心，并保守这个秘密，直到我腾出空间让我们看到。你不需要知道我是谁或我来自哪里。我知道这听起来可能会让您感到非常惊讶，但情况就是这样。我已经提前支付了一些赎金以解雇你，原因是我的雇主向我列出的一些原因。我相信这是一个你称之为朋友的人；我已经密切关注了您一段时间，发现您对他对您的指控是清白的。不要联系警察或试图将此副本发送给他们，因为如果你这样做，我会知道，我会被迫去做我得到报酬的事情。此外，这是我第一次在工作中背叛。我可怜你，所以我下定决心要帮助你，如果你愿意帮助自己。现在听着，我会安排我们面对面见面，但在那之前，我需要在明天结束前通过比特币地址支付 10,000 美元。这是为了让我在给你信息时离开城镇。比特币钱包：bc1qez55j3he8tvylca2e3su3eugxv2lpksxexzer4 我会去你家，或者你决定我们在哪里见面；我再说一遍，不要安排警察，如果你玩得很辛苦，它会延伸到你的家人。不设置任何摄像头遮挡我们或设置任何磁带记录我们的谈话；我的雇主现在在我的控制之下。付款细节将提供给你先支付 5,000 美元的部分付款，这将作为你准备好合作的保证，然后我将发送一份包含他要求我终止你的视频磁带的副本将有足够的证据让你在他雇用另一个人做这份工作之前对他采取任何法律行动。收到磁带后，您将支付 5,000 美元的余额。警告; 不要联系警察，确保在晚上 7.30 之后呆在室内，直到整件事得到解决，如果你忽视这些警告中的任何一个，你将受到责备。你没有太多时间，所以马上回我注意：我会建议你把这个留给自己，即使是朋友或家人也不应该知道，因为它可能是他们中的一员。 [cid:image022dd9.GIF@58c0eb0c.43b53f6e] Servicentro 248 Tepatitan Express Servicentro servicentro248(a)officedepot.com.mx [cid:image189324.JPG@14c85146.4c80e561] ________________________________ Este correo electrónico (incluyendo cualquier archivo adjunto) puede contener información privada, confidencial o protegida. Si recibió este correo electrónico por error, por favor elimínelo del sistema sin copiarlo y notifique por correo electrónico al remitente para que nuestros registros puedan ser corregidos. This e-mail (including any attachments) may contain information that is private, confidential or protected. If you received this e-mail in error, please delete it from your system without copying it and notifiy sender by reply e-mail, so that our records can be corrected.

1 0

[PATCH 1/2] digest: add the 0 byte packet checking for long hash
by Kai Ye 17 Jan '23

17 Jan '23

Hardware v2 digest needs to check the zero byte packet in the frist and middle bd.Add a function that get the hash bd type. It can simplify the code of the process of hash bd type checking. Signed-off-by: Kai Ye <yekai13(a)huawei.com> --- drv/hisi_sec.c | 72 +++++++++++++++++++++++++++++++++++++++++++------- 1 file changed, 62 insertions(+), 10 deletions(-) diff --git a/drv/hisi_sec.c b/drv/hisi_sec.c index c30b653..116424e 100644 --- a/drv/hisi_sec.c +++ b/drv/hisi_sec.c @@ -187,6 +187,13 @@ enum sec_c_width { C_WIDTH_CS3 = 0x3, }; +enum hash_bd_type { + HASH_SINGLE_BD, + HASH_FRIST_BD, + HASH_MIDDLE_BD, + HASH_END_BD, +}; + struct hisi_sec_ctx { struct wd_ctx_config_internal config; }; @@ -1379,9 +1386,29 @@ static int long_hash_param_check(handle_t h_qp, struct wd_digest_msg *msg) return 0; } +static enum hash_bd_type get_hash_bd_type(struct wd_digest_msg *msg) +{ + /* + * [has_next , iv_bytes] + * [ 1 , 0 ] = long hash(frist bd) + * [ 1 , 1 ] = long hash(middle bd) + * [ 0 , 1 ] = long hash(end bd) + * [ 0 , 0 ] = block hash(single bd) + */ + if (msg->has_next && !msg->iv_bytes) + return HASH_FRIST_BD; + else if (msg->has_next && msg->iv_bytes) + return HASH_MIDDLE_BD; + else if (!msg->has_next && msg->iv_bytes) + return HASH_END_BD; + else + return HASH_SINGLE_BD; +} + static int fill_digest_long_hash(handle_t h_qp, struct wd_digest_msg *msg, struct hisi_sec_sqe *sqe) { + enum hash_bd_type bd_type = get_hash_bd_type(msg); __u64 total_bits; int ret; @@ -1389,20 +1416,20 @@ static int fill_digest_long_hash(handle_t h_qp, struct wd_digest_msg *msg, if (ret) return ret; - if (msg->has_next && !msg->iv_bytes) { + if (bd_type == HASH_FRIST_BD) { /* Long hash first */ sqe->ai_apd_cs = AI_GEN_INNER; sqe->ai_apd_cs |= AUTHPAD_NOPAD << AUTHPAD_OFFSET; } - if (msg->has_next && msg->iv_bytes) { + if (bd_type == HASH_MIDDLE_BD) { /* Long hash middle */ sqe->ai_apd_cs = AI_GEN_IVIN_ADDR; sqe->ai_apd_cs |= AUTHPAD_NOPAD << AUTHPAD_OFFSET; sqe->type2.a_ivin_addr = sqe->type2.mac_addr; } - if (!msg->has_next && msg->iv_bytes) { + if (bd_type == HASH_END_BD) { /* Long hash end */ sqe->ai_apd_cs = AI_GEN_IVIN_ADDR; sqe->ai_apd_cs |= AUTHPAD_PAD << AUTHPAD_OFFSET; @@ -1478,14 +1505,38 @@ static int aes_auth_len_check(struct wd_digest_msg *msg) return 0; } +static int digest_bd2_zero_packet_check(struct wd_digest_msg *msg) +{ + enum hash_bd_type type = get_hash_bd_type(msg); + + /* Long hash first and middle bd */ + if (type == HASH_FRIST_BD || type == HASH_MIDDLE_BD) { + WD_ERR("hardware v2 not supports 0 size in long hash!\n"); + return -WD_EINVAL; + } + + /* Block mode hash bd */ + if (type == HASH_SINGLE_BD) { + WD_ERR("hardware v2 not supports 0 size in block hash!\n"); + return -WD_EINVAL; + } + + return 0; +} + static int digest_len_check(struct wd_digest_msg *msg, enum sec_bd_type type) { int ret; - /* End BD not need to check the input zero bytes */ - if (unlikely(type == BD_TYPE2 && !msg->has_next && !msg->in_bytes)) { - WD_ERR("kunpeng 920, digest mode not support 0 size!\n"); - return -WD_EINVAL; + /* + * Hardware v2 needs to check the zero byte packet in the block + * and long hash mode. Frist and Middle bd not supports 0 size, + * final bd not need to check it. Hardware v3 has fixed it. + */ + if (type == BD_TYPE2 && !msg->in_bytes) { + ret = digest_bd2_zero_packet_check(msg); + if (ret) + return ret; } if (type == BD_TYPE3) { @@ -1714,6 +1765,7 @@ static int aes_auth_long_hash_check(struct wd_digest_msg *msg) static int fill_digest_long_hash3(handle_t h_qp, struct wd_digest_msg *msg, struct hisi_sec_sqe3 *sqe) { + enum hash_bd_type bd_type = get_hash_bd_type(msg); __u64 total_bits; int ret; @@ -1725,20 +1777,20 @@ static int fill_digest_long_hash3(handle_t h_qp, struct wd_digest_msg *msg, if (ret) return ret; - if (msg->has_next && !msg->iv_bytes) { + if (bd_type == HASH_FRIST_BD) { /* Long hash first */ sqe->auth_mac_key |= AI_GEN_INNER << SEC_AI_GEN_OFFSET_V3; sqe->stream_scene.stream_auth_pad = AUTHPAD_NOPAD; } - if (msg->has_next && msg->iv_bytes) { + if (bd_type == HASH_MIDDLE_BD) { /* Long hash middle */ sqe->auth_mac_key |= AI_GEN_IVIN_ADDR << SEC_AI_GEN_OFFSET_V3; sqe->stream_scene.stream_auth_pad = AUTHPAD_NOPAD; sqe->auth_ivin.a_ivin_addr = sqe->mac_addr; } - if (!msg->has_next && msg->iv_bytes) { + if (bd_type == HASH_END_BD) { /* Long hash end */ sqe->auth_mac_key |= AI_GEN_IVIN_ADDR << SEC_AI_GEN_OFFSET_V3; sqe->stream_scene.stream_auth_pad = AUTHPAD_PAD; -- 2.17.1

1 1

[PATCH] digest: add private variable values initialization
by y00501072 17 Jan '23

17 Jan '23

From: Kai Ye <yekai13(a)huawei.com> If use the 'digest_copy' in task, like sm2 signature and verification, the private variable values may not be updated. This will cause the sm2 verify failure. So add the value cleanup in the 'digest init'. Signed-off-by: Kai Ye <yekai13(a)huawei.com> --- src/uadk_digest.c | 13 +++++++++++-- 1 file changed, 11 insertions(+), 2 deletions(-) diff --git a/src/uadk_digest.c b/src/uadk_digest.c index 8ce9fd1..9df1349 100644 --- a/src/uadk_digest.c +++ b/src/uadk_digest.c @@ -496,6 +496,15 @@ static void digest_priv_ctx_setup(struct digest_priv_ctx *priv, priv->req.out_bytes = out_len; } +static void digest_priv_ctx_cleanup(struct digest_priv_ctx *priv) +{ + /* Ensure that private variable values are initialized */ + priv->state = SEC_DIGEST_INIT; + priv->last_update_bufflen = 0; + priv->switch_threshold = 0; + priv->switch_flag = 0; +} + static int uadk_e_digest_init(EVP_MD_CTX *ctx) { struct digest_priv_ctx *priv = @@ -510,7 +519,8 @@ static int uadk_e_digest_init(EVP_MD_CTX *ctx) priv->soft_ctx = EVP_MD_CTX_new(); priv->e_nid = nid; - priv->state = SEC_DIGEST_INIT; + digest_priv_ctx_cleanup(priv); + ret = uadk_e_init_digest(); if (unlikely(!ret)) { priv->switch_flag = UADK_DO_SOFT; @@ -761,7 +771,6 @@ static int uadk_e_digest_final(EVP_MD_CTX *ctx, unsigned char *digest) goto clear; } memcpy(digest, priv->req.out, priv->req.out_bytes); - priv->last_update_bufflen = 0; return 1; -- 2.30.0

1 0

[PATCH v7 0/6] add dynamic driver loading function
by Longfang Liu 07 Jan '23

07 Jan '23

Update the current driver adaptation and usage method, from fixed use of Hisilicon device driver to automatic registration of the driver according to the algorithm. When the algorithm API layer uses the driver, it is no longer bound to the fixed device driver, but dynamically obtained and stored according to the algorithm query to use. Update the driver and API layer of the zip and sec module, keep the function of the init interface unchanged, update the implementation of the init2 interface and match the dynamic loading function. Changes v6 -> v7: - Added dynamically loaded design documents. Changes v5 -> v6: - Rebase based on the patch of the zlib interface. Changes v4 -> v5: - Enhance the inclusiveness of the init2 interface. Changes v3 -> v4: - Remove the template instance code of cipher. - Split the scheduler code into a separate patch. Changes v2 -> v3: - Add dynamic library file search function - Fix some memory handling issues Changes v1 -> v2: - Fixed the compatibility method with the previous library file loading Longfang Liu (6): uadk: Add driver dynamic loading function uadk: update scheduler for dynamic loading uadk: improve the dynamic loading public framework uadk/doc: adding dynamically loaded design documents uadk: added ability to query supported algorithms uadk/zip: Adapt the zip module to the dynamic loading framework Makefile.am | 4 +- ...sion_and_modular_dynamic_loading_design.md | 432 ++++++++++++++ drv/hisi_comp.c | 59 +- include/drv/wd_comp_drv.h | 27 - include/wd.h | 12 + include/wd_alg.h | 95 +++ include/wd_alg_common.h | 11 + include/wd_sched.h | 6 +- include/wd_util.h | 63 +- libwd.map | 8 + wd.c | 56 +- wd_alg.c | 265 +++++++++ wd_comp.c | 243 ++++---- wd_sched.c | 105 +++- wd_util.c | 549 +++++++++++++++++- 15 files changed, 1769 insertions(+), 166 deletions(-) create mode 100644 docs/UADK_framework_expansion_and_modular_dynamic_loading_design.md create mode 100644 include/wd_alg.h create mode 100644 wd_alg.c -- 2.33.0

1 6

sig-AccLib 双周例会
by openEuler conference 03 Jan '23

03 Jan '23

您好！ sig-AccLib SIG 邀请您参加 2023-01-04 11:00 召开的Zoom会议会议主题：sig-AccLib 双周例会会议内容： zoom固定的会议链接：https://linaro-org.zoom.us/j/91879279131 1.进展讨论 2.培训分享-open ssl 3.0 provider机制讲解（徐国栋）。会议链接：https://us06web.zoom.us/j/87633368438?pwd=d0p2UFc4M3o3QmFWS24wTHd3amxRQT09 会议纪要：https://etherpad.openeuler.org/p/sig-AccLib-meetings 温馨提醒：建议接入会议后修改参会人的姓名，也可以使用您在gitee.com的ID 更多资讯尽在：https://openeuler.org/zh/ Hello! openEuler sig-AccLib SIG invites you to attend the Zoom conference will be held at 2023-01-04 11:00, The subject of the conference is sig-AccLib 双周例会, Summary: zoom固定的会议链接：https://linaro-org.zoom.us/j/91879279131 1.进展讨论 2.培训分享-open ssl 3.0 provider机制讲解（徐国栋）。 You can join the meeting at https://us06web.zoom.us/j/87633368438?pwd=d0p2UFc4M3o3QmFWS24wTHd3amxRQT09. Add topics at https://etherpad.openeuler.org/p/sig-AccLib-meetings. Note: You are advised to change the participant name after joining the conference or use your ID at gitee.com. More information: https://openeuler.org/en/

1 0

2024

2023

2022

Acc January 2023