[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20120116164146.GI10189@linux.vnet.ibm.com>
Date: Mon, 16 Jan 2012 22:11:46 +0530
From: Srikar Dronamraju <srikar@...ux.vnet.ibm.com>
To: Jiri Olsa <jolsa@...hat.com>
Cc: Peter Zijlstra <peterz@...radead.org>,
Linus Torvalds <torvalds@...ux-foundation.org>,
Oleg Nesterov <oleg@...hat.com>, Ingo Molnar <mingo@...e.hu>,
Andrew Morton <akpm@...ux-foundation.org>,
LKML <linux-kernel@...r.kernel.org>,
Linux-mm <linux-mm@...ck.org>, Andi Kleen <andi@...stfloor.org>,
Christoph Hellwig <hch@...radead.org>,
Steven Rostedt <rostedt@...dmis.org>,
Roland McGrath <roland@...k.frob.com>,
Thomas Gleixner <tglx@...utronix.de>,
Masami Hiramatsu <masami.hiramatsu.pt@...achi.com>,
Arnaldo Carvalho de Melo <acme@...radead.org>,
Anton Arapov <anton@...hat.com>,
Ananth N Mavinakayanahalli <ananth@...ibm.com>,
Jim Keniston <jkenisto@...ux.vnet.ibm.com>,
Stephen Rothwell <sfr@...b.auug.org.au>
Subject: Re: [PATCH v9 3.2 7/9] tracing: uprobes trace_event interface
* Jiri Olsa <jolsa@...hat.com> [2012-01-16 16:33:27]:
> On Mon, Jan 16, 2012 at 08:15:38PM +0530, Srikar Dronamraju wrote:
> > >
> > > I've tested following event:
> > > echo "p:probe_libc/free /lib64/libc-2.13.so:0x7a4f0 %ax" > ./uprobe_events
> > >
> > > and commands like:
> > > perf record -a -e probe_libc:free --filter "common_pid == 1127"
> > > perf record -e probe_libc:free --filter "arg1 == 0xa" ls
> > >
> > > got me proper results.
> > >
> >
> > Okay thanks for the inputs.
> >
> > > thanks,
> > > jirka
> > >
> > > ---
> > > The preemption needs to be disabled when submitting data into perf.
> >
> > I actually looked at other places where perf_trace_buf_prepare and
> > perf_trace_buf_submit are being called. for example perf_syscall_enter
> > and perf_syscall_exit both call the above routines and they didnt seem
> > to be called with premption disabled. Is that the way perf probe is
> > called in our case that needs us to call pre-emption here? Did you see a
> > case where calling these without preemption disabled caused a problem?
>
> the perf_trace_buf_prepare touches per cpu variables,
> hence the preemption disabling
>
> the perf_trace_buf_prepare code is used by syscalls,
> kprobes, and trace events
>
> - both syscalls and trace events are implemented by
> tracepoints which disable preemption before calling the probe
> (see __DO_TRACE macro in include/linux/tracepoint.h)
>
> - kprobes disable preemption as well
> (kprobe_handler in arch/x86/kernel/kprobes.c)
> haven't checked the optimalized kprobes,
> but should be the same case
>
> jirka
>
Okay, thanks for the clarification, I will pick the fix.
--
Thanks and Regards
Srikar
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists