From: Liam Mark <lmark@codeaurora.org>
To: Alexey Skidanov <alexey.skidanov@intel.com>
Cc: Laura Abbott <labbott@redhat.com>,
Greg KH <gregkh@linuxfoundation.org>,
devel@driverdev.osuosl.org, tkjos@android.com, rve@android.com,
linux-kernel@vger.kernel.org, maco@android.com,
sumit.semwal@linaro.org
Subject: Re: [PATCH v3] staging: android: ion: Add implementation of dma_buf_vmap and dma_buf_vunmap
Date: Sat, 15 Dec 2018 21:20:49 -0800 (PST) [thread overview]
Message-ID: <alpine.DEB.2.10.1812152119130.2951@lmark-linux.qualcomm.com> (raw)
In-Reply-To: <7d836085-cd8d-300b-56be-e8db4ff37afc@intel.com>
On Tue, 6 Feb 2018, Alexey Skidanov wrote:
>
>
> On 02/07/2018 01:56 AM, Laura Abbott wrote:
> > On 01/31/2018 10:10 PM, Alexey Skidanov wrote:
> >>
> >> On 01/31/2018 03:00 PM, Greg KH wrote:
> >>> On Wed, Jan 31, 2018 at 02:03:42PM +0200, Alexey Skidanov wrote:
> >>>> Any driver may access shared buffers, created by ion, using
> >>>> dma_buf_vmap and
> >>>> dma_buf_vunmap dma-buf API that maps/unmaps previosuly allocated
> >>>> buffers into
> >>>> the kernel virtual address space. The implementation of these API is
> >>>> missing in
> >>>> the current ion implementation.
> >>>>
> >>>> Signed-off-by: Alexey Skidanov <alexey.skidanov@intel.com>
> >>>> ---
> >>>
> >>> No review from any other Intel developers? :(
> >> Will add.
> >>>
> >>> Anyway, what in-tree driver needs access to these functions?
> >> I'm not sure that there are the in-tree drivers using these functions
> >> and ion as> buffer exporter because they are not implemented in ion :)
> >> But there are some in-tre> drivers using these APIs (gpu drivers) with
> >> other buffer exporters.
> >
> > It's still not clear why you need to implement these APIs.
> How the importing kernel module may access the content of the buffer? :)
> With the current ion implementation it's only possible by dma_buf_kmap,
> mapping one page at a time. For pretty large buffers, it might have some
> performance impact.
> (Probably, the page by page mapping is the only way to access large
> buffers on 32 bit systems, where the vmalloc range is very small. By the
> way, the current ion dma_map_kmap doesn't really map only 1 page at a
> time - it uses the result of vmap() that might fail on 32 bit systems.)
>
> > Are you planning to use Ion with GPU drivers? I'm especially
> > interested in this if you have a non-Android use case.
> Yes, my use case is the non-Android one. But not with GPU drivers.
> >
> > Thanks,
> > Laura
>
> Thanks,
> Alexey
I was wondering if we could re-open the discussion on adding support to
ION for dma_buf_vmap.
It seems like the patch was not taken as the reviewers wanted more
evidence of an upstream use case.
Here would be my upstream usage argument for including dma_buf_vmap
support in ION.
Currently all calls to ion_dma_buf_begin_cpu_access result in the creation
of a kernel mapping for the buffer, unfortunately the resulting call to
alloc_vmap_area can be quite expensive and this has caused a performance
regression for certain clients when they have moved to the new version of
ION.
The kernel mapping is not actually needed in ion_dma_buf_begin_cpu_access,
and generally isn't needed by clients. So if we remove the creation of the
kernel mapping in ion_dma_buf_begin_cpu_access and only create it when
needed we can speed up the calls to ion_dma_buf_begin_cpu_access.
An additional benefit of removing the creation of kernel mappings from
ion_dma_buf_begin_cpu_access is that it makes the ION code more secure.
Currently a malicious client could call the DMA_BUF_IOCTL_SYNC IOCTL with
flags DMA_BUF_SYNC_END multiple times to cause the ION buffer kmap_cnt to
go negative which could lead to undesired behavior.
One disadvantage of the above change is that a kernel mapping is not
already created when a client calls dma_buf_kmap. So the following
dma_buf_kmap contract can't be satisfied.
/**
* dma_buf_kmap - Map a page of the buffer object into kernel address
space. The
* same restrictions as for kmap and friends apply.
* @dmabuf: [in] buffer to map page from.
* @page_num: [in] page in PAGE_SIZE units to map.
*
* This call must always succeed, any necessary preparations that might
fail
* need to be done in begin_cpu_access.
*/
But hopefully we can work around this by moving clients to dma_buf_vmap.
Based on discussions at LPC here is what was proposed:
- #1 Add support to ION for dma_buf_vmap and dma_buf_vunmap
- #2 Move any existing ION clients over from using dma_buf_kmap to
dma_buf_vmap
- #3 Deprecate support in ION for dma_buf_kmap?
- #4 Make the above performance optimization to
ion_dma_buf_begin_cpu_access to remove the creation of a kernel mapping.
Thoughts?
Liam
Qualcomm Innovation Center, Inc. is a member of Code Aurora Forum,
a Linux Foundation Collaborative Project
next prev parent reply other threads:[~2018-12-16 5:20 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-01-31 12:03 [PATCH v3] staging: android: ion: Add implementation of dma_buf_vmap and dma_buf_vunmap Alexey Skidanov
2018-01-31 13:00 ` Greg KH
2018-02-01 6:10 ` Alexey Skidanov
2018-02-06 23:56 ` Laura Abbott
2018-02-07 5:25 ` Alexey Skidanov
2018-12-16 5:20 ` Liam Mark [this message]
2018-12-16 6:35 ` Alexey Skidanov
2018-12-17 18:42 ` Liam Mark
2018-12-18 16:24 ` Alexey Skidanov
2019-01-04 17:41 ` Liam Mark
2019-01-04 22:11 ` Skidanov, Alexey
2019-01-29 23:56 ` Liam Mark
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=alpine.DEB.2.10.1812152119130.2951@lmark-linux.qualcomm.com \
--to=lmark@codeaurora.org \
--cc=alexey.skidanov@intel.com \
--cc=devel@driverdev.osuosl.org \
--cc=gregkh@linuxfoundation.org \
--cc=labbott@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=maco@android.com \
--cc=rve@android.com \
--cc=sumit.semwal@linaro.org \
--cc=tkjos@android.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).