Evolution-x/hardware_interfaces
1
0
Fork 0
mirror of https://github.com/Evolution-X/hardware_interfaces synced 2026-02-01 11:36:00 +00:00
Code Issues Packages Projects Releases Wiki Activity

Merge "memtrack: Update AIDL memtrack hal documentation"

Browse Source
This commit is contained in:
Kalesh Singh
2021-06-30 18:45:42 +00:00
committed by Gerrit Code Review
parent 229d55513b 30fa141c80
commit 55305df1ff
1 changed files with 10 additions and 4 deletions
Download Patch File Download Diff File Expand all files Collapse all files

14
memtrack/aidl/android/hardware/memtrack/IMemtrack.aidl
View File

@@ -31,12 +31,14 @@ import android.hardware.memtrack.MemtrackType;
* accounting for stride, bit depth, rounding up to page size, etc.
*
* The following getMemory() categories are important for memory accounting in
* `dumpsys meminfo` and should be reported as described below:
* Android frameworks (e.g. `dumpsys meminfo`) and should be reported as described
* below:
*
* - MemtrackType::GRAPHICS and MemtrackRecord::FLAG_SMAPS_UNACCOUNTED
* This should report the PSS of all DMA buffers mapped by the process
* with the specified PID. This PSS can be calculated using ReadDmaBufPss()
* form libdmabufinfo.
* This should report the PSS of all CPU-Mapped DMA-BUFs (buffers mapped into
* the process address space) and all GPU-Mapped DMA-BUFs (buffers mapped into
* the GPU device address space on behalf of the process), removing any overlap
* between the CPU-mapped and GPU-mapped sets.
*
* - MemtrackType::GL and MemtrackRecord::FLAG_SMAPS_UNACCOUNTED
* This category should report all GPU private allocations for the specified
@@ -46,6 +48,10 @@ import android.hardware.memtrack.MemtrackType;
* Any other memory not accounted for in /proc/<pid>/smaps if any, otherwise
* this should return 0.
*
* SMAPS_UNACCOUNTED memory should also include memory that is mapped with
* VM_PFNMAP flag set. For these mappings PSS and RSS are reported as 0 in smaps.
* Such mappings have no backing page structs from which PSS/RSS can be calculated.
*
* Constructor for the interface should be used to perform memtrack management
* setup actions and must be called once before any calls to getMemory().
*/