From: Christoph Hellwig <hch@lst.de>
To: Mathieu Poirier <mathieu.poirier@linaro.org>
Cc: yj.chiang@mediatek.com, linux-remoteproc@vger.kernel.org,
linux-kernel@vger.kernel.org, iommu@lists.linux-foundation.org,
linux-mediatek@lists.infradead.org,
linux-arm-kernel@lists.infradead.org, matthias.bgg@gmail.com,
robin.murphy@arm.com, Christoph Hellwig <hch@lst.de>,
Mark-PK Tsai <mark-pk.tsai@mediatek.com>
Subject: Re: [PATCH 0/2] dma-mapping, remoteproc: Fix dma_mem leak after rproc_shutdown
Date: Thu, 23 Jun 2022 07:42:11 +0200 [thread overview]
Message-ID: <20220623054211.GA12408@lst.de> (raw)
In-Reply-To: <20220622162540.GA1606016@p14s>
On Wed, Jun 22, 2022 at 10:25:40AM -0600, Mathieu Poirier wrote:
> On Sat, Apr 23, 2022 at 07:46:50PM +0200, Christoph Hellwig wrote:
> > Sigh. In theory drivers should never declare coherent memory like
> > this, and there has been some work to fix remoteproc in that regard.
> >
> > But I guess until that is merged we'll need somthing like this fix.
>
> Should I take this in the remoteproc tree? If so, can I get an RB?
Reluctantly-Acked-by: Christoph Hellwig <hch@lst.de>
_______________________________________________
iommu mailing list
iommu@lists.linux-foundation.org
https://lists.linuxfoundation.org/mailman/listinfo/iommu
WARNING: multiple messages have this Message-ID (diff)
From: Christoph Hellwig <hch@lst.de>
To: Mathieu Poirier <mathieu.poirier@linaro.org>
Cc: Christoph Hellwig <hch@lst.de>,
Mark-PK Tsai <mark-pk.tsai@mediatek.com>,
bjorn.andersson@linaro.org, robin.murphy@arm.com,
m.szyprowski@samsung.com, matthias.bgg@gmail.com,
linux-remoteproc@vger.kernel.org, linux-kernel@vger.kernel.org,
iommu@lists.linux-foundation.org,
linux-arm-kernel@lists.infradead.org,
linux-mediatek@lists.infradead.org, yj.chiang@mediatek.com
Subject: Re: [PATCH 0/2] dma-mapping, remoteproc: Fix dma_mem leak after rproc_shutdown
Date: Thu, 23 Jun 2022 07:42:11 +0200 [thread overview]
Message-ID: <20220623054211.GA12408@lst.de> (raw)
In-Reply-To: <20220622162540.GA1606016@p14s>
On Wed, Jun 22, 2022 at 10:25:40AM -0600, Mathieu Poirier wrote:
> On Sat, Apr 23, 2022 at 07:46:50PM +0200, Christoph Hellwig wrote:
> > Sigh. In theory drivers should never declare coherent memory like
> > this, and there has been some work to fix remoteproc in that regard.
> >
> > But I guess until that is merged we'll need somthing like this fix.
>
> Should I take this in the remoteproc tree? If so, can I get an RB?
Reluctantly-Acked-by: Christoph Hellwig <hch@lst.de>
WARNING: multiple messages have this Message-ID (diff)
From: Christoph Hellwig <hch@lst.de>
To: Mathieu Poirier <mathieu.poirier@linaro.org>
Cc: Christoph Hellwig <hch@lst.de>,
Mark-PK Tsai <mark-pk.tsai@mediatek.com>,
bjorn.andersson@linaro.org, robin.murphy@arm.com,
m.szyprowski@samsung.com, matthias.bgg@gmail.com,
linux-remoteproc@vger.kernel.org, linux-kernel@vger.kernel.org,
iommu@lists.linux-foundation.org,
linux-arm-kernel@lists.infradead.org,
linux-mediatek@lists.infradead.org, yj.chiang@mediatek.com
Subject: Re: [PATCH 0/2] dma-mapping, remoteproc: Fix dma_mem leak after rproc_shutdown
Date: Thu, 23 Jun 2022 07:42:11 +0200 [thread overview]
Message-ID: <20220623054211.GA12408@lst.de> (raw)
In-Reply-To: <20220622162540.GA1606016@p14s>
On Wed, Jun 22, 2022 at 10:25:40AM -0600, Mathieu Poirier wrote:
> On Sat, Apr 23, 2022 at 07:46:50PM +0200, Christoph Hellwig wrote:
> > Sigh. In theory drivers should never declare coherent memory like
> > this, and there has been some work to fix remoteproc in that regard.
> >
> > But I guess until that is merged we'll need somthing like this fix.
>
> Should I take this in the remoteproc tree? If so, can I get an RB?
Reluctantly-Acked-by: Christoph Hellwig <hch@lst.de>
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
next prev parent reply other threads:[~2022-06-23 5:42 UTC|newest]
Thread overview: 37+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-04-22 6:24 [PATCH 0/2] dma-mapping, remoteproc: Fix dma_mem leak after rproc_shutdown Mark-PK Tsai via iommu
2022-04-22 6:24 ` Mark-PK Tsai
2022-04-22 6:24 ` Mark-PK Tsai
2022-04-22 6:24 ` Mark-PK Tsai
2022-04-22 6:24 ` [PATCH 1/2] dma-mapping: Add dma_release_coherent_memory to DMA API Mark-PK Tsai via iommu
2022-04-22 6:24 ` Mark-PK Tsai
2022-04-22 6:24 ` Mark-PK Tsai
2022-04-22 6:24 ` Mark-PK Tsai
2022-04-22 6:24 ` [PATCH 2/2] remoteproc: Fix dma_mem leak after rproc_shutdown Mark-PK Tsai via iommu
2022-04-22 6:24 ` Mark-PK Tsai
2022-04-22 6:24 ` Mark-PK Tsai
2022-04-22 6:24 ` Mark-PK Tsai
2022-04-23 17:46 ` [PATCH 0/2] dma-mapping, " Christoph Hellwig
2022-04-23 17:46 ` Christoph Hellwig
2022-04-23 17:46 ` Christoph Hellwig
2022-04-23 17:46 ` Christoph Hellwig
2022-05-23 10:15 ` Mark-PK Tsai via iommu
2022-05-23 10:15 ` Mark-PK Tsai
2022-05-23 10:15 ` Mark-PK Tsai
2022-05-23 10:15 ` Mark-PK Tsai
2022-05-23 10:24 ` Robin Murphy
2022-05-23 10:24 ` Robin Murphy
2022-05-23 10:24 ` Robin Murphy
2022-05-23 10:24 ` Robin Murphy
2022-05-23 12:27 ` Mark-PK Tsai via iommu
2022-05-23 12:27 ` Mark-PK Tsai
2022-05-23 12:27 ` Mark-PK Tsai
2022-05-23 12:27 ` Mark-PK Tsai
2022-06-22 16:25 ` Mathieu Poirier
2022-06-22 16:25 ` Mathieu Poirier
2022-06-22 16:25 ` Mathieu Poirier
2022-06-23 5:42 ` Christoph Hellwig [this message]
2022-06-23 5:42 ` Christoph Hellwig
2022-06-23 5:42 ` Christoph Hellwig
2022-06-24 16:48 ` Mathieu Poirier
2022-06-24 16:48 ` Mathieu Poirier
2022-06-24 16:48 ` Mathieu Poirier
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=20220623054211.GA12408@lst.de \
--to=hch@lst.de \
--cc=iommu@lists.linux-foundation.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mediatek@lists.infradead.org \
--cc=linux-remoteproc@vger.kernel.org \
--cc=mark-pk.tsai@mediatek.com \
--cc=mathieu.poirier@linaro.org \
--cc=matthias.bgg@gmail.com \
--cc=robin.murphy@arm.com \
--cc=yj.chiang@mediatek.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.