On 7/1/26 18:08, Thierry Reding wrote:

From: Thierry Reding <redacted>

There is no technical reason why there should be a limited number of CMA
regions, so extract some code into helpers and use them to create extra
functions (cma_create() and cma_free()) that allow creating and freeing,
respectively, CMA regions dynamically at runtime.

The static array of CMA areas cannot be replaced by dynamically created
areas because for many of them, allocation must not fail and some cases
may need to initialize them before the slab allocator is even available.
To account for this, keep these "early" areas in a separate list and
track the dynamic areas in a separate list.

I want MM maintainers to review/ack this before this gets merged.

I'm putting it on my todo list for next week (please ping me if it falls down
the cracks and nobody else ends up reviewing it in the meantime).

-- 
Cheers,

David