These functions allow for retrieval of information on what is allocated from
within a given CMA region. It can be useful to know the number of distinct
contiguous allocations and where in the region those allocations are located.
Based on an initial version by Marc Carino <marc.ceeeee@xxxxxxxxx> in a driver
that used the CMA bitmap directly; this instead moves the logic into the core
CMA API.
Signed-off-by: Gregory Fong <gregory.0xf0@xxxxxxxxx>
---
This has been really useful for us to determine allocation information for a
CMA region. We have had a separate driver that might not be appropriate for
upstream, but allowed using a user program to run CMA unit tests to verify that
allocations end up where they we would expect. This addition would allow for
that without needing to expose the CMA bitmap. Wanted to put this out there to
see if anyone else would be interested, comments and suggestions welcome.