From: Christoph Hellwig <hch@lst.de>
To: Manivannan Sadhasivam <manivannan.sadhasivam@linaro.org>
Cc: Christoph Hellwig <hch@lst.de>, Andy Gross <agross@kernel.org>,
Bjorn Andersson <andersson@kernel.org>,
Konrad Dybcio <konrad.dybcio@linaro.org>,
Mathieu Poirier <mathieu.poirier@linaro.org>,
Andrew Morton <akpm@linux-foundation.org>,
Uladzislau Rezki <urezki@gmail.com>,
linux-arm-msm@vger.kernel.org, linux-remoteproc@vger.kernel.org,
linux-kernel@vger.kernel.org, linux-mm@kvack.org,
iommu@lists.linux.dev
Subject: Re: [PATCH 1/2] Revert "remoteproc: qcom_q6v5_mss: map/unmap metadata region before/after use"
Date: Fri, 23 Dec 2022 16:51:41 +0100 [thread overview]
Message-ID: <20221223155141.GB30339@lst.de> (raw)
In-Reply-To: <20221223154039.GD4587@thinkpad>
On Fri, Dec 23, 2022 at 09:10:39PM +0530, Manivannan Sadhasivam wrote:
> On Fri, Dec 23, 2022 at 03:57:22PM +0100, Christoph Hellwig wrote:
> > On Fri, Dec 23, 2022 at 08:17:31PM +0530, Manivannan Sadhasivam wrote:
> > > Acked-by: Manivannan Sadhasivam <manivannan.sadhasivam@linaro.org>
> >
> > Btw, if the hardware really does not like a kernel mapping, the
> > right way is to just keep using the normal dma allocator, but make
> > sure that there shared-dma-pool with the no-map property for the
> > device.
>
> Sibi posted a series that uses a separate no-map carveout for this usecase:
> https://lore.kernel.org/lkml/20221213140724.8612-1-quic_sibis@quicinc.com/
Oh, I've missed that entire thread. I actually stumbled over this
today while finding it during a vmap audit..
next prev parent reply other threads:[~2022-12-23 15:51 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-12-23 9:27 revert dma-mapping and vmap API abuse in qcom_q6v5_mss Christoph Hellwig
2022-12-23 9:27 ` [PATCH 1/2] Revert "remoteproc: qcom_q6v5_mss: map/unmap metadata region before/after use" Christoph Hellwig
2022-12-23 14:47 ` Manivannan Sadhasivam
2022-12-23 14:57 ` Christoph Hellwig
2022-12-23 15:40 ` Manivannan Sadhasivam
2022-12-23 15:51 ` Christoph Hellwig [this message]
2022-12-23 9:27 ` [PATCH 2/2] vmalloc: reject vmap with VM_FLUSH_RESET_PERMS Christoph Hellwig
2022-12-23 10:24 ` Lorenzo Stoakes
2022-12-23 14:03 ` Christoph Hellwig
2022-12-23 14:10 ` Lorenzo Stoakes
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=20221223155141.GB30339@lst.de \
--to=hch@lst.de \
--cc=agross@kernel.org \
--cc=akpm@linux-foundation.org \
--cc=andersson@kernel.org \
--cc=iommu@lists.linux.dev \
--cc=konrad.dybcio@linaro.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=linux-remoteproc@vger.kernel.org \
--cc=manivannan.sadhasivam@linaro.org \
--cc=mathieu.poirier@linaro.org \
--cc=urezki@gmail.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: 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;
as well as URLs for NNTP newsgroup(s).