File: debugfs.txt

package info (click to toggle)
linux 4.9.228-1
  • links: PTS, VCS
  • area: main
  • in suites: stretch
  • size: 814,720 kB
  • sloc: ansic: 14,532,095; asm: 289,032; makefile: 35,316; perl: 27,556; sh: 17,027; python: 13,390; cpp: 6,103; yacc: 4,354; lex: 2,440; awk: 1,212; pascal: 231; lisp: 218; sed: 21
file content (21 lines) | stat: -rw-r--r-- 826 bytes parent folder | download | duplicates (11)
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
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.