From: Matthias Kaehlcke <mka@chromium.org>
To: Sibi Sankar <quic_sibis@quicinc.com>
Cc: bjorn.andersson@linaro.org, arnd@arndb.de,
linux-kernel@vger.kernel.org, linux-arm-msm@vger.kernel.org,
sboyd@kernel.org, agross@kernel.org,
linux-remoteproc@vger.kernel.org, mathieu.poirier@linaro.org
Subject: Re: [PATCH] remoteproc: qcom_q6v5_mss: map/unmap metadata region before/after use
Date: Fri, 6 May 2022 11:07:41 -0700 [thread overview]
Message-ID: <YnVj7fxUbTqkJpdz@google.com> (raw)
In-Reply-To: <1651845086-16535-1-git-send-email-quic_sibis@quicinc.com>
On Fri, May 06, 2022 at 07:21:26PM +0530, Sibi Sankar wrote:
> The application processor accessing the dynamically assigned metadata
> region after assigning it to the remote Q6 would lead to an XPU violation.
> Fix this by un-mapping the metadata region post firmware header copy. The
> metadata region is freed only after the modem Q6 is done with fw header
> authentication.
>
> Signed-off-by: Sibi Sankar <quic_sibis@quicinc.com>
Should this have a 'Fixes:' tag?
> ---
> drivers/remoteproc/qcom_q6v5_mss.c | 43 +++++++++++++++++++++++++++++++-------
> 1 file changed, 35 insertions(+), 8 deletions(-)
>
> diff --git a/drivers/remoteproc/qcom_q6v5_mss.c b/drivers/remoteproc/qcom_q6v5_mss.c
> index af217de75e4d..eb34a258b67b 100644
> --- a/drivers/remoteproc/qcom_q6v5_mss.c
> +++ b/drivers/remoteproc/qcom_q6v5_mss.c
> @@ -10,6 +10,7 @@
> #include <linux/clk.h>
> #include <linux/delay.h>
> #include <linux/devcoredump.h>
> +#include <linux/dma-map-ops.h>
> #include <linux/dma-mapping.h>
> #include <linux/interrupt.h>
> #include <linux/kernel.h>
> @@ -932,27 +933,52 @@ static void q6v5proc_halt_axi_port(struct q6v5 *qproc,
> static int q6v5_mpss_init_image(struct q6v5 *qproc, const struct firmware *fw,
> const char *fw_name)
> {
> - unsigned long dma_attrs = DMA_ATTR_FORCE_CONTIGUOUS;
> + unsigned long dma_attrs = DMA_ATTR_FORCE_CONTIGUOUS | DMA_ATTR_NO_KERNEL_MAPPING;
> + unsigned long flags = VM_DMA_COHERENT | VM_FLUSH_RESET_PERMS;
> + struct page **pages;
> + struct page *page;
> dma_addr_t phys;
> void *metadata;
> int mdata_perm;
> int xferop_ret;
> size_t size;
> - void *ptr;
> + void *vaddr;
> + int count;
> int ret;
> + int i;
>
> metadata = qcom_mdt_read_metadata(fw, &size, fw_name, qproc->dev);
> if (IS_ERR(metadata))
> return PTR_ERR(metadata);
>
> - ptr = dma_alloc_attrs(qproc->dev, size, &phys, GFP_KERNEL, dma_attrs);
> - if (!ptr) {
> - kfree(metadata);
> + page = dma_alloc_attrs(qproc->dev, size, &phys, GFP_KERNEL, dma_attrs);
> + if (!page) {
> dev_err(qproc->dev, "failed to allocate mdt buffer\n");
> - return -ENOMEM;
> + ret = -ENOMEM;
> + goto free_metadata;
> + }
> +
> + count = PAGE_ALIGN(size) >> PAGE_SHIFT;
> + pages = kmalloc_array(count, sizeof(struct page *), GFP_KERNEL);
> + if (!pages) {
> + ret = -ENOMEM;
> + goto free_metadata;
> }
>
> - memcpy(ptr, metadata, size);
> + for (i = 0; i < count; i++)
> + pages[i] = nth_page(page, i);
> +
> + vaddr = vmap(pages, count, flags, dma_pgprot(qproc->dev, PAGE_KERNEL, dma_attrs));
> + kfree(pages);
> + if (!vaddr) {
> + dev_err(qproc->dev, "unable to map memory region: %pa+%zx\n", &phys, size);
> + ret = -EBUSY;
> + goto free_metadata;
> + }
> +
> + memcpy(vaddr, metadata, size);
> +
> + vunmap(vaddr);
>
> /* Hypervisor mapping to access metadata by modem */
> mdata_perm = BIT(QCOM_SCM_VMID_HLOS);
> @@ -982,7 +1008,8 @@ static int q6v5_mpss_init_image(struct q6v5 *qproc, const struct firmware *fw,
> "mdt buffer not reclaimed system may become unstable\n");
>
> free_dma_attrs:
> - dma_free_attrs(qproc->dev, size, ptr, phys, dma_attrs);
> + dma_free_attrs(qproc->dev, size, page, phys, dma_attrs);
> +free_metadata:
> kfree(metadata);
>
> return ret < 0 ? ret : 0;
> --
> 2.7.4
>
next prev parent reply other threads:[~2022-05-06 18:07 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-05-06 13:51 [PATCH] remoteproc: qcom_q6v5_mss: map/unmap metadata region before/after use Sibi Sankar
2022-05-06 18:07 ` Matthias Kaehlcke [this message]
2022-05-11 5:51 ` Sibi Sankar
2022-05-06 22:40 ` kernel test robot
2022-05-07 0:14 ` kernel test robot
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=YnVj7fxUbTqkJpdz@google.com \
--to=mka@chromium.org \
--cc=agross@kernel.org \
--cc=arnd@arndb.de \
--cc=bjorn.andersson@linaro.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-remoteproc@vger.kernel.org \
--cc=mathieu.poirier@linaro.org \
--cc=quic_sibis@quicinc.com \
--cc=sboyd@kernel.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