On Mon, Sep 3, 2012 at 2:23 PM, Nishanth Peethambaran nishanth.peethu@gmail.com wrote:
Rebecca has already updated heap_show to show the orphaned buffers. This patch won't apply on top of it.
For our need, I have updated the heap_show() and heap_total() functions to account the heap usage per heap->id instead of heap->type. I had posted a patch also for that. There can be multiple
Does the patch for id has been merged ?
heaps of same type. Use-cases are to map read buffer in sdram bank0 and write buffer in sdram bank1. Or to have small dedicated carveout heap for camera use-case which we don't want to fail or get delayed
I am afraid this can not be achieved in existing ion.c, where only heap->id is used.
ion_alloc /* if the client doesn't support this heap type */ if (!((1 << heap->type) & client->heap_mask)) continue; /* if the caller didn't specify this heap type */ if (!((1 << heap->id) & heap_mask)) continue;
The client->heap_mask is -1 and heap->type does not used at all. ion_open -> ion_client_create(dev, -1, "user") -> client->heap_mask = heap_mask;
Besides, ion_allocation_data only have vector heap_mask, how to use both id and type?
because of cma migration failures/retries.
- Nishanth Peethambaran