Closed Bug 1038933 Opened 12 years ago Closed 12 years ago

Add option to retrieve kgsl memory reports in get_about_memory.py

Categories

(Firefox OS Graveyard :: General, defect)

All
Gonk (Firefox OS)
defect
Not set
normal

Tracking

(b2g-v2.1 fixed)

RESOLVED FIXED
2.0 S6 (18july)
Tracking Status
b2g-v2.1 --- fixed

People

(Reporter: erahm, Assigned: erahm)

Details

(Whiteboard: [MemShrink])

Attachments

(1 file)

On flame devices we can gather debug info on kgsl graphics memory usage from |/d/kgsl/proc/<pid>/mem|. The full report should be useful for graphics memory usage analysis.
get_about_memory.py will now attempt to retrieve kgsl memory usage files for each process that is using kgsl, the files are stored in the out_dir with the name kgsl_proc_mem. A --no-kgsl-logs flag has be been added to bypass kgsl memory info collection.
Assignee: nobody → erahm
Status: NEW → ASSIGNED
Attachment #8458213 - Flags: review?(n.nethercote)
The code looks fine, but is this something that should be read by the SystemMemoryReporter?
(In reply to Nicholas Nethercote [:njn] from comment #2) > The code looks fine, but is this something that should be read by the > SystemMemoryReporter? :BenWa requested an option to get the raw report as well, we have bug 1038921 for the SystemMemoryReporter.
I'm glad bug 1038921 exists, but this still feels like it's unnecessary duplication of function.
Comment on attachment 8458213 [details] [review] Link to Github pull-request: https://github.com/mozilla-b2g/B2G/pull/367 I'll give r+, but I'd like you and BenWa to decide if this is really necessary.
Attachment #8458213 - Flags: review?(n.nethercote) → review+
My understanding was that the memory reporter would give a general breakdown and throw away the other information. The full KGSL report has extra fields that are useful for debugging like the resource ids. They probably are not that useful outside of graphics debugging but the files should also be small and quick to collect. I say the cost of collecting this information is fairly low but I admit it wont be looked at very often.
Yes it contains more information than just the byte counts that SystemMemoryReporter will provide.
Keywords: checkin-needed
Status: ASSIGNED → RESOLVED
Closed: 12 years ago
Keywords: checkin-needed
Resolution: --- → FIXED
Target Milestone: --- → 2.0 S6 (18july)
Ok, fair enough.
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Created:
Updated:
Size: