threeeye
bc1d038eac
Squashed backup commit (no shallow-clone history issues) of xiaomi-mt6833-dev/kernel_xiaomi_mt6833 (lineage-23.2 branch, upstream commit 9eece662e) plus all fixes applied to get everpal_defconfig building clean against a modern (GCC 15.2.0) toolchain -- see the previous commit message on the lineage-23.2 branch (also in this repo history is not available here since this is a squashed snapshot; full incremental history lives in the local DL380 checkout and the upstream GitHub remote). Upstream: https://github.com/xiaomi-mt6833-dev/kernel_xiaomi_mt6833 (lineage-23.2)
22 lines
826 B
Plaintext
22 lines
826 B
Plaintext
The CMA debugfs interface is useful to retrieve basic information out of the
|
|
different CMA areas and to test allocation/release in each of the areas.
|
|
|
|
Each CMA zone represents a directory under <debugfs>/cma/, indexed by the
|
|
kernel's CMA index. So the first CMA zone would be:
|
|
|
|
<debugfs>/cma/cma-0
|
|
|
|
The structure of the files created under that directory is as follows:
|
|
|
|
- [RO] base_pfn: The base PFN (Page Frame Number) of the zone.
|
|
- [RO] count: Amount of memory in the CMA area.
|
|
- [RO] order_per_bit: Order of pages represented by one bit.
|
|
- [RO] bitmap: The bitmap of page states in the zone.
|
|
- [WO] alloc: Allocate N pages from that CMA area. For example:
|
|
|
|
echo 5 > <debugfs>/cma/cma-2/alloc
|
|
|
|
would try to allocate 5 pages from the cma-2 area.
|
|
|
|
- [WO] free: Free N pages from that CMA area, similar to the above.
|