LKML Archive on lore.kernel.org help / color / mirror / Atom feed
From: Kai Ye <yekai13@huawei.com> To: <herbert@gondor.apana.org.au> Cc: <linux-crypto@vger.kernel.org>, <linux-kernel@vger.kernel.org>, <wangzhou1@hisilicon.com>, <yekai13@huawei.com> Subject: [PATCH 1/2] crypto: hisilicon/qm - fix the uacce mmap failed Date: Sat, 28 Aug 2021 11:39:38 +0800 [thread overview] Message-ID: <1630121979-53760-2-git-send-email-yekai13@huawei.com> (raw) In-Reply-To: <1630121979-53760-1-git-send-email-yekai13@huawei.com> Allocate an extra memory page for qp. This extra page is used to set the device or qp status. But this page not be used currently. Meanwhile it leads to dus size not equal to mmap size as using uacce sva mode, and cause the app task broken. Signed-off-by: Kai Ye <yekai13@huawei.com> --- drivers/crypto/hisilicon/qm.c | 4 +++- 1 file changed, 3 insertions(+), 1 deletion(-) diff --git a/drivers/crypto/hisilicon/qm.c b/drivers/crypto/hisilicon/qm.c index 369562d..2bd25bf 100644 --- a/drivers/crypto/hisilicon/qm.c +++ b/drivers/crypto/hisilicon/qm.c @@ -3122,8 +3122,10 @@ static int qm_alloc_uacce(struct hisi_qm *qm) else mmio_page_nr = qm->db_interval / PAGE_SIZE; + /* Add one more page for device or qp status */ dus_page_nr = (PAGE_SIZE - 1 + qm->sqe_size * QM_Q_DEPTH + - sizeof(struct qm_cqe) * QM_Q_DEPTH) >> PAGE_SHIFT; + sizeof(struct qm_cqe) * QM_Q_DEPTH + PAGE_SIZE) >> + PAGE_SHIFT; uacce->qf_pg_num[UACCE_QFRT_MMIO] = mmio_page_nr; uacce->qf_pg_num[UACCE_QFRT_DUS] = dus_page_nr; -- 2.7.4
next prev parent reply other threads:[~2021-08-28 3:41 UTC|newest] Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top 2021-08-28 3:39 [PATCH 0/2] crypto: hisilicon/qm - Support the userspace task resetting Kai Ye 2021-08-28 3:39 ` Kai Ye [this message] 2021-08-28 3:39 ` [PATCH 2/2] crypto: hisilicon/qm - support " Kai Ye 2021-09-17 3:19 ` [PATCH 0/2] crypto: hisilicon/qm - Support " Herbert Xu
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=1630121979-53760-2-git-send-email-yekai13@huawei.com \ --to=yekai13@huawei.com \ --cc=herbert@gondor.apana.org.au \ --cc=linux-crypto@vger.kernel.org \ --cc=linux-kernel@vger.kernel.org \ --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: linkBe 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; as well as URLs for NNTP newsgroup(s).