New issue
Advanced search Search tips

Issue 865162 link

Starred by 1 user

Issue metadata

Status: Available
Owner: ----
Cc:
EstimatedDays: ----
NextAction: ----
OS: Android
Pri: 2
Type: Feature



Sign in to add a comment

Dump driver-specific allocation info to android_memtrack

Project Member Reported by ericrk@chromium.org, Jul 18

Issue description

On Adreno devices, we can read /d/kgsl/proc/[pid]/mem to get a list of all active driver objects.

This info is pretty useful, and it would be helpful to update our android_memtrack dumping logic to read this file on Adreno devices and include its output in the memory dump.

I haven't looked at this tool recently, but if I remember, it requires root anyway, so I imagine it could just read the file in question.
 
Summary: Dump driver-specific allocation info to android_memtrack (was: Dump additional info to android_memtrack)
> I haven't looked at this tool recently, but if I remember, it requires root anyway
Yup

> so I imagine it could just read the file in question.
The only (not huge) challenge is that the protocol over the socket is super dumb and uses SOCK_SEQPACKET which has a max len per datagram. I guess we could batch them though.
 

Sign in to add a comment