[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20131025125921.GA29424@linux.vnet.ibm.com>
Date: Fri, 25 Oct 2013 18:29:21 +0530
From: Srikar Dronamraju <srikar@...ux.vnet.ibm.com>
To: Pekka Enberg <penberg@...nel.org>
Cc: 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, Ingo Molnar <mingo@...hat.com>,
anton@...hat.com, systemtap@...rceware.org,
Namhyung Kim <namhyung@...nel.org>,
Masami Hiramatsu <masami.hiramatsu.pt@...achi.com>,
aravinda@...ux.vnet.ibm.com
Subject: Re: [PATCH v4 2/3] Support for perf to probe into SDT markers:
Hi Pekka,
> >
> > You can now use it in all perf tools, such as:
> >
> > perf record -e libc:my_event -aR sleep 1
>
> Is there a technical reason why 'perf list' could not show all the
> available SDT markers on a system and that the 'market to event'
> mapping cannot happen automatically?
>
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.
Also if a binary exists in a path thats is not covered in the default
search, an user might believe that his binary may not have markers.
I know the above reason is more of a user folly than a tooling issue.
> So instead of doing all the command line magic above I'd do:
>
> perf list
>
> libc:setjmp [SDT marker]
>
> and I could just do
>
> perf record -e libc:setjmp -AR sleep 1
>
> ?
--
Thanks and Regards
Srikar Dronamraju
--
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