[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <526A8C2B.7000401@gmail.com>
Date: Fri, 25 Oct 2013 09:20:11 -0600
From: David Ahern <dsahern@...il.com>
To: Pekka Enberg <penberg@....fi>,
Srikar Dronamraju <srikar@...ux.vnet.ibm.com>
CC: Pekka Enberg <penberg@...nel.org>,
Hemant Kumar <hkshaw@...ux.vnet.ibm.com>,
LKML <linux-kernel@...r.kernel.org>,
Peter Zijlstra <peterz@...radead.org>,
Oleg Nesterov <oleg@...hat.com>,
"hegdevasant@...ux.vnet.ibm.com" <hegdevasant@...ux.vnet.ibm.com>,
Ingo Molnar <mingo@...hat.com>,
"anton@...hat.com" <anton@...hat.com>,
"systemtap@...rceware.org" <systemtap@...rceware.org>,
Namhyung Kim <namhyung@...nel.org>,
Masami Hiramatsu <masami.hiramatsu.pt@...achi.com>,
"aravinda@...ux.vnet.ibm.com" <aravinda@...ux.vnet.ibm.com>
Subject: Re: [PATCH v4 2/3] Support for perf to probe into SDT markers:
On 10/25/13 8:20 AM, Pekka Enberg wrote:
>> Technically feasible. But then we would have to parse each of the
>> libraries and executables to list them. Right? I am not sure if such a
>> delay is acceptable.
>
> You could do it at 'perf list' time or even build time and cache it. And add lazy discovery to 'perf record' and friends.
Instead searching all the known files or building a cache, how about
just having an option like: perf list <DSO>. perf-record could still do
the probe magic behind the scenes.
David
--
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