linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: Laura Abbott <labbott@redhat.com>
To: Laurent Pinchart <laurent.pinchart@ideasonboard.com>
Cc: Sumit Semwal <sumit.semwal@linaro.org>,
	Riley Andrews <riandrews@android.com>,
	arve@android.com, romlem@google.com, devel@driverdev.osuosl.org,
	linux-kernel@vger.kernel.org, linaro-mm-sig@lists.linaro.org,
	Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
	linux-arm-kernel@lists.infradead.org,
	linux-media@vger.kernel.org, dri-devel@lists.freedesktop.org,
	Brian Starkey <brian.starkey@arm.com>,
	Daniel Vetter <daniel.vetter@intel.com>,
	Mark Brown <broonie@kernel.org>,
	Benjamin Gaignard <benjamin.gaignard@linaro.org>,
	linux-mm@kvack.org
Subject: Re: [PATCHv3 13/22] staging: android: ion: Use CMA APIs directly
Date: Tue, 11 Apr 2017 09:48:12 -0700	[thread overview]
Message-ID: <fd813e0f-10c3-05a7-aaf8-f33531556ec4@redhat.com> (raw)
In-Reply-To: <20163378.oNfPtYlzx6@avalon>

On 04/10/2017 11:47 PM, Laurent Pinchart wrote:
> Hi Laura,
> 
> Thank you for the patch.
> 
> On Monday 03 Apr 2017 11:57:55 Laura Abbott wrote:
>> When CMA was first introduced, its primary use was for DMA allocation
>> and the only way to get CMA memory was to call dma_alloc_coherent. This
>> put Ion in an awkward position since there was no device structure
>> readily available and setting one up messed up the coherency model.
>> These days, CMA can be allocated directly from the APIs. Switch to using
>> this model to avoid needing a dummy device. This also mitigates some of
>> the caching problems (e.g. dma_alloc_coherent only returning uncached
>> memory).
> 
> Do we have a guarantee that the DMA mapping API, which we have to use for 
> cache handling, will always support memory we allocate directly from CMA 
> behind its back ?
> 

CMA pages are no different than other pages allocated via the buddy
allocator. There should be no issue passing that memory to the
streaming API.

Thanks,
Laura

>> Signed-off-by: Laura Abbott <labbott@redhat.com>
>> ---
>>  drivers/staging/android/ion/Kconfig        |  7 +++
>>  drivers/staging/android/ion/Makefile       |  3 +-
>>  drivers/staging/android/ion/ion_cma_heap.c | 97 +++++++--------------------
>>  3 files changed, 35 insertions(+), 72 deletions(-)
>>
>> diff --git a/drivers/staging/android/ion/Kconfig
>> b/drivers/staging/android/ion/Kconfig index 206c4de..15108c4 100644
>> --- a/drivers/staging/android/ion/Kconfig
>> +++ b/drivers/staging/android/ion/Kconfig
>> @@ -10,3 +10,10 @@ menuconfig ION
>>  	  If you're not using Android its probably safe to
>>  	  say N here.
>>
>> +config ION_CMA_HEAP
>> +	bool "Ion CMA heap support"
>> +	depends on ION && CMA
>> +	help
>> +	  Choose this option to enable CMA heaps with Ion. This heap is backed
>> +	  by the Contiguous Memory Allocator (CMA). If your system has these
>> +	  regions, you should say Y here.
>> diff --git a/drivers/staging/android/ion/Makefile
>> b/drivers/staging/android/ion/Makefile index 26672a0..66d0c4a 100644
>> --- a/drivers/staging/android/ion/Makefile
>> +++ b/drivers/staging/android/ion/Makefile
>> @@ -1,6 +1,7 @@
>>  obj-$(CONFIG_ION) +=	ion.o ion-ioctl.o ion_heap.o \
>>  			ion_page_pool.o ion_system_heap.o \
>> -			ion_carveout_heap.o ion_chunk_heap.o ion_cma_heap.o
>> +			ion_carveout_heap.o ion_chunk_heap.o
>> +obj-$(CONFIG_ION_CMA_HEAP) += ion_cma_heap.o
>>  ifdef CONFIG_COMPAT
>>  obj-$(CONFIG_ION) += compat_ion.o
>>  endif
>> diff --git a/drivers/staging/android/ion/ion_cma_heap.c
>> b/drivers/staging/android/ion/ion_cma_heap.c index d562fd7..f3e0f59 100644
>> --- a/drivers/staging/android/ion/ion_cma_heap.c
>> +++ b/drivers/staging/android/ion/ion_cma_heap.c
>> @@ -19,24 +19,19 @@
>>  #include <linux/slab.h>
>>  #include <linux/errno.h>
>>  #include <linux/err.h>
>> -#include <linux/dma-mapping.h>
>> +#include <linux/cma.h>
>> +#include <linux/scatterlist.h>
>>
>>  #include "ion.h"
>>  #include "ion_priv.h"
>>
>>  struct ion_cma_heap {
>>  	struct ion_heap heap;
>> -	struct device *dev;
>> +	struct cma *cma;
>>  };
>>
>>  #define to_cma_heap(x) container_of(x, struct ion_cma_heap, heap)
>>
>> -struct ion_cma_buffer_info {
>> -	void *cpu_addr;
>> -	dma_addr_t handle;
>> -	struct sg_table *table;
>> -};
>> -
>>
>>  /* ION CMA heap operations functions */
>>  static int ion_cma_allocate(struct ion_heap *heap, struct ion_buffer
>> *buffer, @@ -44,93 +39,53 @@ static int ion_cma_allocate(struct ion_heap
>> *heap, struct ion_buffer *buffer, unsigned long flags)
>>  {
>>  	struct ion_cma_heap *cma_heap = to_cma_heap(heap);
>> -	struct device *dev = cma_heap->dev;
>> -	struct ion_cma_buffer_info *info;
>> -
>> -	dev_dbg(dev, "Request buffer allocation len %ld\n", len);
>> -
>> -	if (buffer->flags & ION_FLAG_CACHED)
>> -		return -EINVAL;
>> +	struct sg_table *table;
>> +	struct page *pages;
>> +	int ret;
>>
>> -	info = kzalloc(sizeof(*info), GFP_KERNEL);
>> -	if (!info)
>> +	pages = cma_alloc(cma_heap->cma, len, 0, GFP_KERNEL);
>> +	if (!pages)
>>  		return -ENOMEM;
>>
>> -	info->cpu_addr = dma_alloc_coherent(dev, len, &(info->handle),
>> -						GFP_HIGHUSER | __GFP_ZERO);
>> -
>> -	if (!info->cpu_addr) {
>> -		dev_err(dev, "Fail to allocate buffer\n");
>> +	table = kmalloc(sizeof(struct sg_table), GFP_KERNEL);
>> +	if (!table)
>>  		goto err;
>> -	}
>>
>> -	info->table = kmalloc(sizeof(*info->table), GFP_KERNEL);
>> -	if (!info->table)
>> +	ret = sg_alloc_table(table, 1, GFP_KERNEL);
>> +	if (ret)
>>  		goto free_mem;
>>
>> -	if (dma_get_sgtable(dev, info->table, info->cpu_addr, info->handle,
>> -			    len))
>> -		goto free_table;
>> -	/* keep this for memory release */
>> -	buffer->priv_virt = info;
>> -	buffer->sg_table = info->table;
>> -	dev_dbg(dev, "Allocate buffer %p\n", buffer);
>> +	sg_set_page(table->sgl, pages, len, 0);
>> +
>> +	buffer->priv_virt = pages;
>> +	buffer->sg_table = table;
>>  	return 0;
>>
>> -free_table:
>> -	kfree(info->table);
>>  free_mem:
>> -	dma_free_coherent(dev, len, info->cpu_addr, info->handle);
>> +	kfree(table);
>>  err:
>> -	kfree(info);
>> +	cma_release(cma_heap->cma, pages, buffer->size);
>>  	return -ENOMEM;
>>  }
>>
>>  static void ion_cma_free(struct ion_buffer *buffer)
>>  {
>>  	struct ion_cma_heap *cma_heap = to_cma_heap(buffer->heap);
>> -	struct device *dev = cma_heap->dev;
>> -	struct ion_cma_buffer_info *info = buffer->priv_virt;
>> +	struct page *pages = buffer->priv_virt;
>>
>> -	dev_dbg(dev, "Release buffer %p\n", buffer);
>>  	/* release memory */
>> -	dma_free_coherent(dev, buffer->size, info->cpu_addr, info->handle);
>> +	cma_release(cma_heap->cma, pages, buffer->size);
>>  	/* release sg table */
>> -	sg_free_table(info->table);
>> -	kfree(info->table);
>> -	kfree(info);
>> -}
>> -
>> -static int ion_cma_mmap(struct ion_heap *mapper, struct ion_buffer *buffer,
>> -			struct vm_area_struct *vma)
>> -{
>> -	struct ion_cma_heap *cma_heap = to_cma_heap(buffer->heap);
>> -	struct device *dev = cma_heap->dev;
>> -	struct ion_cma_buffer_info *info = buffer->priv_virt;
>> -
>> -	return dma_mmap_coherent(dev, vma, info->cpu_addr, info->handle,
>> -				 buffer->size);
>> -}
>> -
>> -static void *ion_cma_map_kernel(struct ion_heap *heap,
>> -				struct ion_buffer *buffer)
>> -{
>> -	struct ion_cma_buffer_info *info = buffer->priv_virt;
>> -	/* kernel memory mapping has been done at allocation time */
>> -	return info->cpu_addr;
>> -}
>> -
>> -static void ion_cma_unmap_kernel(struct ion_heap *heap,
>> -				 struct ion_buffer *buffer)
>> -{
>> +	sg_free_table(buffer->sg_table);
>> +	kfree(buffer->sg_table);
>>  }
>>
>>  static struct ion_heap_ops ion_cma_ops = {
>>  	.allocate = ion_cma_allocate,
>>  	.free = ion_cma_free,
>> -	.map_user = ion_cma_mmap,
>> -	.map_kernel = ion_cma_map_kernel,
>> -	.unmap_kernel = ion_cma_unmap_kernel,
>> +	.map_user = ion_heap_map_user,
>> +	.map_kernel = ion_heap_map_kernel,
>> +	.unmap_kernel = ion_heap_unmap_kernel,
>>  };
>>
>>  struct ion_heap *ion_cma_heap_create(struct ion_platform_heap *data)
>> @@ -147,7 +102,7 @@ struct ion_heap *ion_cma_heap_create(struct
>> ion_platform_heap *data) * get device from private heaps data, later it
>> will be
>>  	 * used to make the link with reserved CMA memory
>>  	 */
>> -	cma_heap->dev = data->priv;
>> +	cma_heap->cma = data->priv;
>>  	cma_heap->heap.type = ION_HEAP_TYPE_DMA;
>>  	return &cma_heap->heap;
>>  }
> 

--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org.  For more info on Linux MM,
see: http://www.linux-mm.org/ .
Don't email: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>

  reply	other threads:[~2017-04-11 16:48 UTC|newest]

Thread overview: 34+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-04-03 18:57 [PATCHv3 00/22] Ion clean up in preparation in moving out of staging Laura Abbott
2017-04-03 18:57 ` [PATCHv3 01/22] cma: Store a name in the cma structure Laura Abbott
2017-04-03 18:57 ` [PATCHv3 02/22] cma: Introduce cma_for_each_area Laura Abbott
2017-04-03 18:57 ` [PATCHv3 03/22] staging: android: ion: Remove dmap_cnt Laura Abbott
2017-04-03 18:57 ` [PATCHv3 04/22] staging: android: ion: Remove alignment from allocation field Laura Abbott
2017-04-03 18:57 ` [PATCHv3 05/22] staging: android: ion: Duplicate sg_table Laura Abbott
2017-04-03 18:57 ` [PATCHv3 06/22] staging: android: ion: Call dma_map_sg for syncing and mapping Laura Abbott
2017-04-03 18:57 ` [PATCHv3 07/22] staging: android: ion: Remove page faulting support Laura Abbott
2017-04-11  6:00   ` Archit Taneja
2017-04-03 18:57 ` [PATCHv3 08/22] staging: android: ion: Remove crufty cache support Laura Abbott
2017-04-11  5:08   ` Archit Taneja
2017-04-03 18:57 ` [PATCHv3 09/22] staging: android: ion: Remove custom ioctl interface Laura Abbott
2017-04-03 18:57 ` [PATCHv3 10/22] staging: android: ion: Remove import interface Laura Abbott
2017-04-03 18:57 ` [PATCHv3 11/22] staging: android: ion: Remove duplicate ION_IOC_MAP Laura Abbott
2017-04-03 18:57 ` [PATCHv3 12/22] staging: android: ion: Remove old platform support Laura Abbott
2017-04-03 18:57 ` [PATCHv3 13/22] staging: android: ion: Use CMA APIs directly Laura Abbott
2017-04-11  6:47   ` Laurent Pinchart
2017-04-11 16:48     ` Laura Abbott [this message]
2017-04-18 14:07   ` Greg Kroah-Hartman
2017-04-03 18:57 ` [PATCHv3 14/22] staging: android: ion: Stop butchering the DMA address Laura Abbott
2017-04-03 18:57 ` [PATCHv3 15/22] staging: android: ion: Break the ABI in the name of forward progress Laura Abbott
2017-04-03 18:57 ` [PATCHv3 16/22] staging: android: ion: Get rid of ion_phys_addr_t Laura Abbott
2017-04-03 18:57 ` [PATCHv3 17/22] staging: android: ion: Collapse internal header files Laura Abbott
2017-04-08 18:12   ` Emil Velikov
2017-04-10 15:10     ` Laura Abbott
2017-04-03 18:58 ` [PATCHv3 18/22] staging: android: ion: Rework heap registration/enumeration Laura Abbott
2017-04-03 18:58 ` [PATCHv3 19/22] staging: android: ion: Drop ion_map_kernel interface Laura Abbott
2017-04-03 18:58 ` [PATCHv3 20/22] staging: android: ion: Remove ion_handle and ion_client Laura Abbott
2017-04-03 18:58 ` [PATCHv3 21/22] staging: android: ion: Set query return value Laura Abbott
2017-04-03 18:58 ` [PATCHv3 22/22] staging/android: Update Ion TODO list Laura Abbott
2017-04-08 10:38 ` [PATCHv3 00/22] Ion clean up in preparation in moving out of staging Greg Kroah-Hartman
2017-04-10 16:20   ` Laura Abbott
2017-04-10 16:25     ` Greg Kroah-Hartman
2017-04-10 17:20       ` Laura Abbott

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=fd813e0f-10c3-05a7-aaf8-f33531556ec4@redhat.com \
    --to=labbott@redhat.com \
    --cc=arve@android.com \
    --cc=benjamin.gaignard@linaro.org \
    --cc=brian.starkey@arm.com \
    --cc=broonie@kernel.org \
    --cc=daniel.vetter@intel.com \
    --cc=devel@driverdev.osuosl.org \
    --cc=dri-devel@lists.freedesktop.org \
    --cc=gregkh@linuxfoundation.org \
    --cc=laurent.pinchart@ideasonboard.com \
    --cc=linaro-mm-sig@lists.linaro.org \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-media@vger.kernel.org \
    --cc=linux-mm@kvack.org \
    --cc=riandrews@android.com \
    --cc=romlem@google.com \
    --cc=sumit.semwal@linaro.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).