From: Richard Weinberger <richard.weinberger@gmail.com>
To: Thomas Ruf <freelancer@rufusul.de>
Cc: Vinod Koul <vkoul@kernel.org>,
Federico Vaga <federico.vaga@cern.ch>,
Dave Jiang <dave.jiang@intel.com>,
Dan Williams <dan.j.williams@intel.com>,
dmaengine@vger.kernel.org, LKML <linux-kernel@vger.kernel.org>
Subject: Re: DMA Engine: Transfer From Userspace
Date: Mon, 22 Jun 2020 14:27:12 +0200 [thread overview]
Message-ID: <CAFLxGvyNazbyBpySuNA6SU-8tcvqYWKHsAHuhTLsofR=VoiEwQ@mail.gmail.com> (raw)
In-Reply-To: <419762761.402939.1592827272368@mailbusiness.ionos.de>
On Mon, Jun 22, 2020 at 2:02 PM Thomas Ruf <freelancer@rufusul.de> wrote:
> > more the reason not do do so, why cant a kernel driver be added for your
> > usage?
>
> by chance i have written a driver allowing dma from user space using a memcpy like interface ;-)
> now i am trying to get this code upstream but was hit by the fact that DMA_SG is gone since Aug 2017 :-(
>
> just let me introduce myself and the project:
> - coding in C since '91
> - coding in C++ since '98
> - a lot of stuff not relevant for this ;-)
> - working as a freelancer since Nov '19
> - implemented a "dma-sg-proxy" driver for my client in Mar/Apr '20 to copy camera frames from uncached memory to cached memory using a second dma on a Zynq platform
> - last week we figured out that we can not upgrade from "Xilinx 2019.2" (kernel 4.19.x) to "2020.1" (kernel 5.4.x) because the DMA_SG interface is gone
> - subscribed to dmaengine on friday, saw the start of this discussion on saturday
> - talked to my client today if it is ok to try to revive DMA_SG and get our driver upstream to avoid such problems in future
How do you preserve bounds? This is the main reason why vfio requires an iommu.
> here the struct for the ioctl:
>
> typedef struct {
> unsigned int struct_size;
> const void *src_user_ptr;
> void *dst_user_ptr;
> unsigned long length;
> unsigned int timeout_in_ms;
> } dma_sg_proxy_arg_t;
Is this on top of uio or a complete new subsystem?
--
Thanks,
//richard
next prev parent reply other threads:[~2020-06-22 12:27 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-06-19 22:47 DMA Engine: Transfer From Userspace Federico Vaga
2020-06-19 23:31 ` Dave Jiang
2020-06-21 7:24 ` Vinod Koul
2020-06-21 20:36 ` Federico Vaga
2020-06-21 20:45 ` Richard Weinberger
2020-06-21 22:32 ` Federico Vaga
2020-06-22 4:47 ` Vinod Koul
2020-06-22 6:57 ` Federico Vaga
2020-06-22 12:01 ` Thomas Ruf
2020-06-22 12:27 ` Richard Weinberger [this message]
2020-06-22 14:01 ` Thomas Ruf
2020-06-22 12:30 ` Federico Vaga
2020-06-22 14:03 ` Thomas Ruf
2020-06-22 15:54 ` Vinod Koul
2020-06-22 16:34 ` Thomas Ruf
2020-06-24 9:30 ` Thomas Ruf
2020-06-24 9:38 ` Vinod Koul
2020-06-24 12:07 ` Peter Ujfalusi
2020-06-24 13:58 ` Thomas Ruf
2020-06-26 10:29 ` Peter Ujfalusi
2020-06-29 15:18 ` Thomas Ruf
2020-06-30 12:31 ` Peter Ujfalusi
2020-07-01 16:13 ` Thomas Ruf
2020-06-25 0:42 ` Dave Jiang
2020-06-25 8:11 ` Thomas Ruf
2020-06-26 20:08 ` Ira Weiny
2020-06-29 15:31 ` Thomas Ruf
2020-06-22 9:25 ` Federico Vaga
2020-06-22 9:42 ` Vinod Koul
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='CAFLxGvyNazbyBpySuNA6SU-8tcvqYWKHsAHuhTLsofR=VoiEwQ@mail.gmail.com' \
--to=richard.weinberger@gmail.com \
--cc=dan.j.williams@intel.com \
--cc=dave.jiang@intel.com \
--cc=dmaengine@vger.kernel.org \
--cc=federico.vaga@cern.ch \
--cc=freelancer@rufusul.de \
--cc=linux-kernel@vger.kernel.org \
--cc=vkoul@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;
as well as URLs for NNTP newsgroup(s).