lkml.org 
[lkml]   [2009]   [Aug]   [5]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
/
SubjectRe: [PATCH 4/4] tracing, page-allocator: Add a postprocessing script for page-allocator-related ftrace events
From
Date
On Tue, 2009-08-04 at 22:35 +0200, Ingo Molnar wrote:

> Did you never want to see whether firefox is leaking [any sort of]
> memory, and if yes, on what callsites? Try something like on an
> already running firefox context:
>
> perf stat -e kmem:mm_page_alloc \
> -e kmem:mm_pagevec_free \
> -e kmem:mm_page_free_direct \
> -p $(pidof firefox-bin) sleep 10
>
> .... and "perf record" for the specific callsites.

If these tracepoints were to use something like (not yet in mainline)

TP_perf_assign(
__perf_data(obj);
),

Where obj was the thing being allocated/freed, you could, when using
PERF_SAMPLE_ADDR even match up alloc/frees, combined with
PERF_SAMPLE_CALLCHAIN you could then figure out where the unmatched
entries came from.

Might be useful, dunno.




\
 
 \ /
  Last update: 2009-08-05 15:07    [W:2.081 / U:0.728 seconds]
©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site