All of lore.kernel.org
 help / color / mirror / Atom feed
From: Srikar Dronamraju <srikar@linux.vnet.ibm.com>
To: Ingo Molnar <mingo@elte.hu>
Cc: Jiri Olsa <jolsa@redhat.com>,
	Arnaldo Carvalho de Melo <acme@redhat.com>,
	Peter Zijlstra <peterz@infradead.org>,
	Linus Torvalds <torvalds@linux-foundation.org>,
	Oleg Nesterov <oleg@redhat.com>,
	Andrew Morton <akpm@linux-foundation.org>,
	LKML <linux-kernel@vger.kernel.org>,
	Linux-mm <linux-mm@kvack.org>, Andi Kleen <andi@firstfloor.org>,
	Christoph Hellwig <hch@infradead.org>,
	Steven Rostedt <rostedt@goodmis.org>,
	Roland McGrath <roland@hack.frob.com>,
	Thomas Gleixner <tglx@linutronix.de>,
	Masami Hiramatsu <masami.hiramatsu.pt@hitachi.com>,
	Arnaldo Carvalho de Melo <acme@infradead.org>,
	Anton Arapov <anton@redhat.com>,
	Ananth N Mavinakayanahalli <ananth@in.ibm.com>,
	Jim Keniston <jkenisto@linux.vnet.ibm.com>,
	Stephen Rothwell <sfr@canb.auug.org.au>
Subject: Re: [PATCH v9 3.2 7/9] tracing: uprobes trace_event interface
Date: Wed, 18 Jan 2012 15:37:52 +0530	[thread overview]
Message-ID: <20120118100752.GF15447@linux.vnet.ibm.com> (raw)
In-Reply-To: <20120117122133.GB4959@elte.hu>

> 
> Have you tried to use 'perf probe' to achieve any useful 
> instrumentation on a real app?
> 
> I just tried out the 'glibc:free' usecase and it's barely 
> usable.
> 

Thanks for trying.

Yes, I have actually place probes on free and malloc while building a
kernel and it has worked for me.

> Firstly, the recording very frequently produces overruns:
> 
>  $ perf record -e probe_libc:free -aR sleep 1
>  [ perf record: Woken up 169 times to write data ]
>  [ perf record: Captured and wrote 89.674 MB perf.data (~3917919 samples) ]
>  Warning:Processed 1349133 events and lost 1 chunks!
> 

I have seen the "lost chunks" but thats not always and mostly when I
have run perf record for a very long time. But I have seen this even
with just kernel probes too. So I didnt debug that.

> Using -m 4096 made it work better.
> 
> Adding -g for call-graph profiling caused 'perf report' to lock 
> up:
> 
>   perf record -m 4096 -e probe_libc:free -agR sleep 1
>   perf report
>   [ loops forever ]
> 

This actually works for me.
I had CONFIG_PREEMPT not set. So I set it and tried with and without
Jiri's fix. It still worked for me. Can you pass me your config that
shows this hang so that I can try and fix it.

> I've sent a testcase to Arnaldo separately. Note that perf 
> report --stdio appears to work.

There are no changes in perf report because of uprobes. So the data
collected from uprobes could trigger the hang. I was speculating that
not disabling preemption that Jiri pointed out could be causing this. So
I tried with and without but couldnt reproduce. Can I request you to see
if Jiri's patch helps?

Today with -g option, on one machine I do see a 
$ sudo perf report
perf: Floating point exception

I will take a look at this too. Other machines dont seem to show this
error.

> Regular '-e cycles -g' works fine, so this is a uprobes specific 
> bug.
> 

-- 
Thanks and Regards
Srikar

--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org.  For more info on Linux MM,
see: http://www.linux-mm.org/ .
Fight unfair telecom internet charges in Canada: sign http://stopthemeter.ca/
Don't email: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>

WARNING: multiple messages have this Message-ID (diff)
From: Srikar Dronamraju <srikar@linux.vnet.ibm.com>
To: Ingo Molnar <mingo@elte.hu>
Cc: Jiri Olsa <jolsa@redhat.com>,
	Arnaldo Carvalho de Melo <acme@redhat.com>,
	Peter Zijlstra <peterz@infradead.org>,
	Linus Torvalds <torvalds@linux-foundation.org>,
	Oleg Nesterov <oleg@redhat.com>,
	Andrew Morton <akpm@linux-foundation.org>,
	LKML <linux-kernel@vger.kernel.org>,
	Linux-mm <linux-mm@kvack.org>, Andi Kleen <andi@firstfloor.org>,
	Christoph Hellwig <hch@infradead.org>,
	Steven Rostedt <rostedt@goodmis.org>,
	Roland McGrath <roland@hack.frob.com>,
	Thomas Gleixner <tglx@linutronix.de>,
	Masami Hiramatsu <masami.hiramatsu.pt@hitachi.com>,
	Arnaldo Carvalho de Melo <acme@infradead.org>,
	Anton Arapov <anton@redhat.com>,
	Ananth N Mavinakayanahalli <ananth@in.ibm.com>,
	Jim Keniston <jkenisto@linux.vnet.ibm.com>,
	Stephen Rothwell <sfr@canb.auug.org.au>
Subject: Re: [PATCH v9 3.2 7/9] tracing: uprobes trace_event interface
Date: Wed, 18 Jan 2012 15:37:52 +0530	[thread overview]
Message-ID: <20120118100752.GF15447@linux.vnet.ibm.com> (raw)
In-Reply-To: <20120117122133.GB4959@elte.hu>

> 
> Have you tried to use 'perf probe' to achieve any useful 
> instrumentation on a real app?
> 
> I just tried out the 'glibc:free' usecase and it's barely 
> usable.
> 

Thanks for trying.

Yes, I have actually place probes on free and malloc while building a
kernel and it has worked for me.

> Firstly, the recording very frequently produces overruns:
> 
>  $ perf record -e probe_libc:free -aR sleep 1
>  [ perf record: Woken up 169 times to write data ]
>  [ perf record: Captured and wrote 89.674 MB perf.data (~3917919 samples) ]
>  Warning:Processed 1349133 events and lost 1 chunks!
> 

I have seen the "lost chunks" but thats not always and mostly when I
have run perf record for a very long time. But I have seen this even
with just kernel probes too. So I didnt debug that.

> Using -m 4096 made it work better.
> 
> Adding -g for call-graph profiling caused 'perf report' to lock 
> up:
> 
>   perf record -m 4096 -e probe_libc:free -agR sleep 1
>   perf report
>   [ loops forever ]
> 

This actually works for me.
I had CONFIG_PREEMPT not set. So I set it and tried with and without
Jiri's fix. It still worked for me. Can you pass me your config that
shows this hang so that I can try and fix it.

> I've sent a testcase to Arnaldo separately. Note that perf 
> report --stdio appears to work.

There are no changes in perf report because of uprobes. So the data
collected from uprobes could trigger the hang. I was speculating that
not disabling preemption that Jiri pointed out could be causing this. So
I tried with and without but couldnt reproduce. Can I request you to see
if Jiri's patch helps?

Today with -g option, on one machine I do see a 
$ sudo perf report
perf: Floating point exception

I will take a look at this too. Other machines dont seem to show this
error.

> Regular '-e cycles -g' works fine, so this is a uprobes specific 
> bug.
> 

-- 
Thanks and Regards
Srikar


  reply	other threads:[~2012-01-18 10:17 UTC|newest]

Thread overview: 88+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-01-10 11:48 [PATCH v9 3.2 0/9] Uprobes patchset with perf probe support Srikar Dronamraju
2012-01-10 11:48 ` Srikar Dronamraju
2012-01-10 11:48 ` [PATCH v9 3.2 1/9] uprobes: Install and remove breakpoints Srikar Dronamraju
2012-01-10 11:48   ` Srikar Dronamraju
2012-01-25 14:39   ` Denys Vlasenko
2012-01-25 14:39     ` Denys Vlasenko
2012-01-25 16:31     ` Oleg Nesterov
2012-01-25 16:31       ` Oleg Nesterov
2012-01-25 15:13   ` Denys Vlasenko
2012-01-25 15:13     ` Denys Vlasenko
2012-01-25 15:32     ` Denys Vlasenko
2012-01-25 15:32       ` Denys Vlasenko
2012-01-26 14:14       ` Masami Hiramatsu
2012-01-26 14:14         ` Masami Hiramatsu
2012-01-26 18:28         ` Denys Vlasenko
2012-01-26 18:28           ` Denys Vlasenko
2012-01-30  9:51           ` Masami Hiramatsu
2012-01-30  9:51             ` Masami Hiramatsu
2012-01-26 13:38     ` Masami Hiramatsu
2012-01-26 13:38       ` Masami Hiramatsu
2012-01-26 13:45   ` Masami Hiramatsu
2012-01-26 13:45     ` Masami Hiramatsu
2012-01-10 11:48 ` [PATCH v9 3.2 2/9] uprobes: handle breakpoint and signal step exception Srikar Dronamraju
2012-01-10 11:48   ` Srikar Dronamraju
2012-01-18  8:39   ` Anton Arapov
2012-01-18  8:39     ` Anton Arapov
2012-01-18  9:02     ` Srikar Dronamraju
2012-01-18  9:02       ` Srikar Dronamraju
2012-01-18 10:18       ` Mike Frysinger
2012-01-18 10:47         ` Srikar Dronamraju
2012-01-18 10:47           ` Srikar Dronamraju
2012-01-18 11:01           ` Mike Frysinger
2012-01-20 22:57             ` Mike Frysinger
2012-01-20 22:57               ` Mike Frysinger
2012-01-25  8:12               ` Srikar Dronamraju
2012-01-25  8:12                 ` Srikar Dronamraju
2012-01-10 11:48 ` [PATCH v9 3.2 3/9] uprobes: slot allocation Srikar Dronamraju
2012-01-10 11:48   ` Srikar Dronamraju
2012-01-10 11:49 ` [PATCH v9 3.2 4/9] uprobes: counter to optimize probe hits Srikar Dronamraju
2012-01-10 11:49   ` Srikar Dronamraju
2012-01-10 11:49 ` [PATCH v9 3.2 5/9] tracing: modify is_delete, is_return from ints to bool Srikar Dronamraju
2012-01-10 11:49   ` Srikar Dronamraju
2012-01-10 11:49 ` [PATCH v9 3.2 6/9] tracing: Extract out common code for kprobes/uprobes traceevents Srikar Dronamraju
2012-01-10 11:49   ` Srikar Dronamraju
2012-01-10 11:49 ` [PATCH v9 3.2 7/9] tracing: uprobes trace_event interface Srikar Dronamraju
2012-01-10 11:49   ` Srikar Dronamraju
2012-01-16 13:11   ` Jiri Olsa
2012-01-16 13:11     ` Jiri Olsa
2012-01-16 14:45     ` Srikar Dronamraju
2012-01-16 14:45       ` Srikar Dronamraju
2012-01-16 15:33       ` Jiri Olsa
2012-01-16 15:33         ` Jiri Olsa
2012-01-16 16:41         ` Srikar Dronamraju
2012-01-16 16:41           ` Srikar Dronamraju
2012-01-17  9:28     ` Ingo Molnar
2012-01-17  9:28       ` Ingo Molnar
2012-01-17 10:22       ` Srikar Dronamraju
2012-01-17 10:22         ` Srikar Dronamraju
2012-01-17 10:59         ` Ingo Molnar
2012-01-17 10:59           ` Ingo Molnar
2012-01-17 11:03           ` Srikar Dronamraju
2012-01-17 11:03             ` Srikar Dronamraju
2012-01-17 11:22         ` Ingo Molnar
2012-01-17 11:22           ` Ingo Molnar
2012-01-17 11:57           ` Srikar Dronamraju
2012-01-17 11:57             ` Srikar Dronamraju
2012-01-17 12:23             ` Ingo Molnar
2012-01-17 12:23               ` Ingo Molnar
2012-01-17 12:27               ` Ingo Molnar
2012-01-17 12:27                 ` Ingo Molnar
2012-01-17 12:11         ` Ingo Molnar
2012-01-17 12:11           ` Ingo Molnar
2012-01-17 12:21         ` Ingo Molnar
2012-01-17 12:21           ` Ingo Molnar
2012-01-18 10:07           ` Srikar Dronamraju [this message]
2012-01-18 10:07             ` Srikar Dronamraju
2012-01-10 11:49 ` [PATCH v9 3.2 8/9] perf: rename target_module to target Srikar Dronamraju
2012-01-10 11:49   ` Srikar Dronamraju
2012-01-16  8:34 ` [PATCH v9 3.2 0/9] Uprobes patchset with perf probe support Ingo Molnar
2012-01-16  8:34   ` Ingo Molnar
2012-01-16 15:17   ` Srikar Dronamraju
2012-01-16 15:17     ` Srikar Dronamraju
2012-01-17  9:39     ` Ingo Molnar
2012-01-17  9:39       ` Ingo Molnar
2012-01-25 14:11       ` Peter Zijlstra
2012-01-25 14:11         ` Peter Zijlstra
2012-01-26 11:10         ` Ingo Molnar
2012-01-26 11:10           ` Ingo Molnar

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20120118100752.GF15447@linux.vnet.ibm.com \
    --to=srikar@linux.vnet.ibm.com \
    --cc=acme@infradead.org \
    --cc=acme@redhat.com \
    --cc=akpm@linux-foundation.org \
    --cc=ananth@in.ibm.com \
    --cc=andi@firstfloor.org \
    --cc=anton@redhat.com \
    --cc=hch@infradead.org \
    --cc=jkenisto@linux.vnet.ibm.com \
    --cc=jolsa@redhat.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mm@kvack.org \
    --cc=masami.hiramatsu.pt@hitachi.com \
    --cc=mingo@elte.hu \
    --cc=oleg@redhat.com \
    --cc=peterz@infradead.org \
    --cc=roland@hack.frob.com \
    --cc=rostedt@goodmis.org \
    --cc=sfr@canb.auug.org.au \
    --cc=tglx@linutronix.de \
    --cc=torvalds@linux-foundation.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.