Skip to contentSkip to conversation

staging: ion: Fix ion_cma_heap allocations

PATCH Superseded John Stultz 2 participants 3 messages Dec 13, 2017 – Dec 14, 2017 Staging

v2 of 3 Superseded Latest is v3 →

lore
Share & tools
lore
#0 lore raw

PATCH v2 1/1 staging: ion: Fix ion_cma_heap allocations

In trying to add support for drm_hwcomposer to HiKey, I've needed to utilize the ION CMA heap, and I've noticed problems with allocations on newer kernels failing.

It seems back with 204f672255c2 ("ion: Use CMA APIs directly"), the ion_cma_heap code was modified to use the CMA API, but kept the arguments as buffer lengths rather then number of pages.

This results in errors as we don't have enough pages in CMA to satisfy the exaggerated requests.

This patch converts the ion_cma_heap CMA API usage to properly request pages.

It also fixes a minor issue in the allocation where in the error path, the cma_release is called with the buffer->size value which hasn't yet been set.

Cc Laura Abbott <[email protected]>
Cc Sumit Semwal <[email protected]>
Cc Benjamin Gaignard <[email protected]>
Cc Archit Taneja <[email protected]>
Cc Greg KH <[email protected]>
Cc Daniel Vetter <[email protected]>
Cc Dmitry Shmidt <[email protected]>
Cc Todd Kjos <[email protected]>
Cc Amit Pundir <[email protected]>
Fixes 204f672255c2 ("staging: android: ion: Use CMA APIs directly")

---
v2: Fix build errors when CONFIG_CMA_ALIGNMENT isn't defined

 drivers/staging/android/ion/ion_cma_heap.c | 21 +++++++++++++++++----
 1 file changed, 17 insertions(+), 4 deletions(-)
drivers/staging/android/ion/ion_cma_heap.c +17 -4
index dd5545d..ff405c7 100644
@@ -31,6 +31,12 @@ struct ion_cma_heap {
 
 #define to_cma_heap(x) container_of(x, struct ion_cma_heap, heap)
 
+#ifdef CONFIG_CMA_ALIGNMENT
+ #define CMA_ALIGNMENT CONFIG_CMA_ALIGNMENT
+#else
+ #define CMA_ALIGNMNET 8
+#endif
+
 /* ION CMA heap operations functions */
 static int ion_cma_allocate(struct ion_heap *heap, struct ion_buffer *buffer,
 			    unsigned long len,
@@ -39,9 +45,15 @@ static int ion_cma_allocate(struct ion_heap *heap, struct ion_buffer *buffer,
 	struct ion_cma_heap *cma_heap = to_cma_heap(heap);
 	struct sg_table *table;
 	struct page *pages;
+	unsigned long size = PAGE_ALIGN(len);
+	unsigned long nr_pages = size >> PAGE_SHIFT;
+	unsigned long align = get_order(size);
 	int ret;
 
-	pages = cma_alloc(cma_heap->cma, len, 0, GFP_KERNEL);
+	if (align > CMA_ALIGNMENT)
+		align = CMA_ALIGNMENT;
+
+	pages = cma_alloc(cma_heap->cma, nr_pages, align, GFP_KERNEL);
 	if (!pages)
 		return -ENOMEM;
 
@@ -53,7 +65,7 @@ static int ion_cma_allocate(struct ion_heap *heap, struct ion_buffer *buffer,
 	if (ret)
 		goto free_mem;
 
-	sg_set_page(table->sgl, pages, len, 0);
+	sg_set_page(table->sgl, pages, size, 0);
 
 	buffer->priv_virt = pages;
 	buffer->sg_table = table;
@@ -62,7 +74,7 @@ static int ion_cma_allocate(struct ion_heap *heap, struct ion_buffer *buffer,
 free_mem:
 	kfree(table);
 err:
-	cma_release(cma_heap->cma, pages, buffer->size);
+	cma_release(cma_heap->cma, pages, nr_pages);
 	return -ENOMEM;
 }
 
@@ -70,9 +82,10 @@ static void ion_cma_free(struct ion_buffer *buffer)
 {
 	struct ion_cma_heap *cma_heap = to_cma_heap(buffer->heap);
 	struct page *pages = buffer->priv_virt;
+	unsigned long nr_pages = PAGE_ALIGN(buffer->size) >> PAGE_SHIFT;
 
 	/* release memory */
-	cma_release(cma_heap->cma, pages, buffer->size);
+	cma_release(cma_heap->cma, pages, nr_pages);
 	/* release sg table */
 	sg_free_table(buffer->sg_table);
 	kfree(buffer->sg_table);
Signature · 1 line
2.7.4
maintainer
#1 lore raw
Quoted 30 lines · John Stultz

In trying to add support for drm_hwcomposer to HiKey, I've needed to utilize the ION CMA heap, and I've noticed problems with allocations on newer kernels failing.

It seems back with 204f672255c2 ("ion: Use CMA APIs directly"), the ion_cma_heap code was modified to use the CMA API, but kept the arguments as buffer lengths rather then number of pages.

This results in errors as we don't have enough pages in CMA to satisfy the exaggerated requests.

This patch converts the ion_cma_heap CMA API usage to properly request pages.

It also fixes a minor issue in the allocation where in the error path, the cma_release is called with the buffer->size value which hasn't yet been set.

Cc Laura Abbott <[email protected]>
Cc Sumit Semwal <[email protected]>
Cc Benjamin Gaignard <[email protected]>
Cc Archit Taneja <[email protected]>
Cc Greg KH <[email protected]>
Cc Daniel Vetter <[email protected]>
Cc Dmitry Shmidt <[email protected]>
Cc Todd Kjos <[email protected]>
Cc Amit Pundir <[email protected]>
Fixes 204f672255c2 ("staging: android: ion: Use CMA APIs directly")
Quoted 2 lines

---
v2: Fix build errors when CONFIG_CMA_ALIGNMENT isn't defined

As v1 is already in my tree, can you send me the diff so I can just apply that instead of me having to revert the original and then add this one?

thanks,

greg k-h

maintainer
#2 lore raw
In reply to John Stultz
Quoted 30 lines · John Stultz

In trying to add support for drm_hwcomposer to HiKey, I've needed to utilize the ION CMA heap, and I've noticed problems with allocations on newer kernels failing.

It seems back with 204f672255c2 ("ion: Use CMA APIs directly"), the ion_cma_heap code was modified to use the CMA API, but kept the arguments as buffer lengths rather then number of pages.

This results in errors as we don't have enough pages in CMA to satisfy the exaggerated requests.

This patch converts the ion_cma_heap CMA API usage to properly request pages.

It also fixes a minor issue in the allocation where in the error path, the cma_release is called with the buffer->size value which hasn't yet been set.

Cc Laura Abbott <[email protected]>
Cc Sumit Semwal <[email protected]>
Cc Benjamin Gaignard <[email protected]>
Cc Archit Taneja <[email protected]>
Cc Greg KH <[email protected]>
Cc Daniel Vetter <[email protected]>
Cc Dmitry Shmidt <[email protected]>
Cc Todd Kjos <[email protected]>
Cc Amit Pundir <[email protected]>
Fixes 204f672255c2 ("staging: android: ion: Use CMA APIs directly")
Quoted 2 lines

---
v2: Fix build errors when CONFIG_CMA_ALIGNMENT isn't defined

Wait, why would CONFIG_CMA_ALIGNMENT not be defined if we are using the cma code? Is that a Kconfig issue somehow?

thanks,

greg k-h