MM: dump pixel trace at bugreport
Create pixel speicifc trace buffer and enable CMA trace events.
At bugreport, dumpstate will dump the trace buffer into
dumpstate_board.txt
binder:3947_2-3963 [003] .... 29.954681: cma_alloc_start: name=vframe count=16 align=4
binder:3947_2-3963 [003] .... 29.956230: cma_alloc_finish: name=vframe pfn=946080 page=000000003d6b380b count=16 align=4
binder:3947_2-3963 [003] .... 29.956235: cma_alloc_info: name=vframe pfn=0x946080 count=16 align=4 nr_migrated=16 nr_reclaimed=0 nr_mapped=16 err_iso=0 err_mig=0 err_test=0
binder:3947_2-3963 [003] .... 29.988325: cma_release: name=vframe pfn=946080 page=000000003d6b380b count=16
It's useful to investigate CMA allocation problems.
Test: "adb bugreport" includes the trace dump in dumpstate_board.txt
Bug: 238728493
Change-Id: I5eb2f79152d32ff7dbb4b9a7ea679facb186aa00
Signed-off-by: Minchan Kim <minchan@google.com>
1 file changed
