From: Mathieu Poirier <mathieu.poirier@linaro.org>
To: Arnaud POULIQUEN <arnaud.pouliquen@foss.st.com>
Cc: Christoph Hellwig <hch@lst.de>, Ohad Ben-Cohen <ohad@wizery.com>,
Bjorn Andersson <bjorn.andersson@linaro.org>,
linux-remoteproc@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: remoteproc DMA API abuse status
Date: Mon, 28 Jun 2021 14:14:19 -0600 [thread overview]
Message-ID: <20210628201419.GC1200359@p14s> (raw)
In-Reply-To: <011dac94-cfe0-d276-980a-b8ffe1447521@foss.st.com>
On Fri, Jun 25, 2021 at 09:27:09AM +0200, Arnaud POULIQUEN wrote:
> Hello Mathieu,
>
> On 6/24/21 9:35 PM, Mathieu Poirier wrote:
> > Good day Christoph,
> >
> > On Wed, Jun 23, 2021 at 03:43:07PM +0200, Christoph Hellwig wrote:
> >> Hi remoteproc maintainers,
> >>
> >> did you make any progress to get remoteproc out of creating fake
> >> devices that fake their dma ops status and the abuse of
> >> dma_declare_coherent_memory in removeproc_virtio? I remember we had
> >> a discussion on this a long time ago, and there was an unfinished
> >> patchset to change the memory pool handling. What happened to all that?
> >
> > I believe the conversation and patchset you are referring to are pre-dating my
> > time in this subsystem. To make sure I am looking at the right thing, can you
> > (or anyone else) point me to that discussion and related patches?
>
> 2 references:
>
> 1)Previous discussion thread on the topic:
>
> https://patchwork.kernel.org/project/linux-remoteproc/patch/AOKowLclCbOCKxyiJ71WeNyuAAj2q8EUtxrXbyky5E@cp7-web-042.plabs.ch/
>
I remember that one. Glad to see there wasn't anything else before that.
> 2) My patchset related to the refactoring of remoteproc virtio which tries to
> address the point by creating a remoteproc platform driver and declaring a
> virtio subnode in the device tree remoteproc node.
>
> https://lkml.org/lkml/2020/4/16/1817
>
I thought your current work on refactoring the rpmsg_char driver was part of the
early steps on the way to splitting that patchset up...
> No time yet on my side to come back on the patchset :(
>
I know the feeling.
Thanks for the info,
Mathieu
next prev parent reply other threads:[~2021-06-28 20:14 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-06-23 13:43 remoteproc DMA API abuse status Christoph Hellwig
2021-06-24 19:35 ` Mathieu Poirier
2021-06-25 7:27 ` Arnaud POULIQUEN
2021-06-28 13:36 ` Christoph Hellwig
2021-06-28 20:14 ` Mathieu Poirier [this message]
2021-06-29 10:10 ` Arnaud POULIQUEN
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=20210628201419.GC1200359@p14s \
--to=mathieu.poirier@linaro.org \
--cc=arnaud.pouliquen@foss.st.com \
--cc=bjorn.andersson@linaro.org \
--cc=hch@lst.de \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-remoteproc@vger.kernel.org \
--cc=ohad@wizery.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).