Donate to e Foundation | Murena handsets with /e/OS | Own a part of Murena! Learn more

Commit be53a67a authored by Kalesh Singh's avatar Kalesh Singh Committed by Automerger Merge Worker
Browse files

Merge "memtrack: Update AIDL memtrack hal documentation" am: 55305df1

Original change: https://android-review.googlesource.com/c/platform/hardware/interfaces/+/1751681

Change-Id: I7c20edd812cb4713c7d5ea0fb567646c3cc7b1bb
parents a5a924db 55305df1
Loading
Loading
Loading
Loading
+10 −4
Original line number Diff line number Diff line
@@ -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().
 */