Memtrack HAL: Report global total GPU-private memory

Update memtrack hal documentation to allow reporting the global
total GPU-private memory from the getMemory() API.

Specify how to handle unsupported memtrack operations.

Bug: 193226716
Bug: 193465681
Bug: 192621117
Test: N/A
Change-Id: I6fcebd16fafdc34cc662137784e86750ee907eee
This commit is contained in:
Kalesh Singh 2021-07-13 01:45:41 +00:00
parent 45cb33bf7a
commit eeac52c8f1

View file

@ -44,6 +44,12 @@ import android.hardware.memtrack.MemtrackType;
* This category should report all GPU private allocations for the specified
* PID that are not accounted in /proc/<pid>/smaps.
*
* getMemory() called with PID 0 should report the global total GPU-private
* memory, for MemtrackType::GL and MemtrackRecord::FLAG_SMAPS_UNACCOUNTED.
*
* getMemory() called with PID 0 for a MemtrackType other than GL should
* report 0.
*
* - MemtrackType::OTHER and MemtrackRecord::FLAG_SMAPS_UNACCOUNTED
* Any other memory not accounted for in /proc/<pid>/smaps if any, otherwise
* this should return 0.
@ -52,6 +58,9 @@ import android.hardware.memtrack.MemtrackType;
* 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.
*
* Any memtrack operation that is not supported should return a binder status with
* exception code EX_UNSUPPORTED_OPERATION.
*
* Constructor for the interface should be used to perform memtrack management
* setup actions and must be called once before any calls to getMemory().
*/