[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20120412151037.GC21587@linux.vnet.ibm.com>
Date: Thu, 12 Apr 2012 20:40:37 +0530
From: Srikar Dronamraju <srikar@...ux.vnet.ibm.com>
To: Arnaldo Carvalho de Melo <acme@...radead.org>
Cc: Masami Hiramatsu <masami.hiramatsu.pt@...achi.com>,
Peter Zijlstra <peterz@...radead.org>,
Ingo Molnar <mingo@...e.hu>,
Andrew Morton <akpm@...ux-foundation.org>,
Linus Torvalds <torvalds@...ux-foundation.org>,
Ananth N Mavinakayanahalli <ananth@...ibm.com>,
Jim Keniston <jkenisto@...ux.vnet.ibm.com>,
LKML <linux-kernel@...r.kernel.org>,
Linux-mm <linux-mm@...ck.org>, Oleg Nesterov <oleg@...hat.com>,
Andi Kleen <andi@...stfloor.org>,
Christoph Hellwig <hch@...radead.org>,
Steven Rostedt <rostedt@...dmis.org>,
Thomas Gleixner <tglx@...utronix.de>,
Anton Arapov <anton@...hat.com>
Subject: Re: Re: [PATCH] perf/probe: Provide perf interface for uprobes
> $ perf probe libc malloc
>
> Makes it even easier to use.
>
> Its just when one asks for something that has ambiguities that
> the tool should ask the user to be a bit more precise to remove such
> ambiguity.
>
> After all...
>
Another case
perf probe do_fork clone_flags now looks for variable clone_flags in
kernel function do_fork.
But if we allow to trace perf probe zsh zfree; then
'perf probe do_fork clone_flags' should it check for do_fork executable
or not? If it does check and finds one, and searches for clone_flags
function and doesnt find, then should it continue with searching the
kernel?
--
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