Hi Jiri,
On Thu, 11 Jul 2013 16:56:54 +0900, Namhyung Kim wrote:
> On Wed, 10 Jul 2013 16:18:20 +0200, Jiri Olsa wrote:
>> On Wed, Jun 26, 2013 at 04:14:09PM +0900, Namhyung Kim wrote:
>>> From: Namhyung Kim
>>>
>>> The -p (--pid) option enables to trace existing process by its pid.
>>
>> hi,
>>
On Wed, 10 Jul 2013 16:18:20 +0200, Jiri Olsa wrote:
> On Wed, Jun 26, 2013 at 04:14:09PM +0900, Namhyung Kim wrote:
>> From: Namhyung Kim
>>
>> The -p (--pid) option enables to trace existing process by its pid.
>
> hi,
> I can't get any output from -p for live subcommand:
>
> [jolsa@krava perf]
On Wed, Jun 26, 2013 at 04:14:09PM +0900, Namhyung Kim wrote:
> From: Namhyung Kim
>
> The -p (--pid) option enables to trace existing process by its pid.
hi,
I can't get any output from -p for live subcommand:
[jolsa@krava perf]$ pgrep yes
6443
[jolsa@krava perf]$ sudo ./perf ftrace live -p `p
2013-06-27 (목), 07:56 -0600, David Ahern:
> On 6/26/13 11:23 PM, Namhyung Kim wrote:
> > The pid filtering in ftrace is done via set_ftrace_pid file under the
> > tracing debugfs directory. IIRC It only supports process filtering not
> > thread filtering by iterating all threads in the kernel code
On 6/26/13 11:23 PM, Namhyung Kim wrote:
On Wed, 26 Jun 2013 11:12:19 -0600, David Ahern wrote:
On 6/26/13 1:14 AM, Namhyung Kim wrote:
@@ -196,6 +222,8 @@ int cmd_ftrace(int argc, const char **argv, const char
*prefix __maybe_unused)
const struct option ftrace_options[] = {
OP
On Wed, 26 Jun 2013 11:12:19 -0600, David Ahern wrote:
> On 6/26/13 1:14 AM, Namhyung Kim wrote:
>> @@ -196,6 +222,8 @@ int cmd_ftrace(int argc, const char **argv, const char
>> *prefix __maybe_unused)
>> const struct option ftrace_options[] = {
>> OPT_STRING('t', "tracer", &ftrace.trace
On 6/26/13 1:14 AM, Namhyung Kim wrote:
@@ -196,6 +222,8 @@ int cmd_ftrace(int argc, const char **argv, const char
*prefix __maybe_unused)
const struct option ftrace_options[] = {
OPT_STRING('t', "tracer", &ftrace.tracer, "tracer",
"tracer to use"),
+ OPT
7 matches
Mail list logo
