mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: David Ahern <dsahern@gmail.com>
To: Namhyung Kim <namhyung@kernel.org>, acme@kernel.org
Cc: mingo@kernel.org, peterz@infradead.org, jolsa@kernel.org,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2] perf sched timehist: Improve error message when analyzing wrong file
Date: Mon, 5 Dec 2016 15:41:54 -0800	[thread overview]
Message-ID: <0b7e62e2-ef1d-6ad1-86c7-16c32c83a94f@gmail.com> (raw)
In-Reply-To: <CAM9d7ciJ3GV=OX3osZOjxQZe7V18iN2OavSJ7H5=+jShcWXSZw@mail.gmail.com>

On 11/29/16 9:31 PM, Namhyung Kim wrote:
> On 11/30/16, David Ahern <dsahern@gmail.com> wrote:
>> Arnaldo reported an unhelpful error message when running perf sched
>> timehist on a file that did not contain sched tracepoints:
>>
>>     [root@jouet ~]# perf sched timehist
>>     No trace sample to read. Did you call 'perf record -R'?
>>
>>     [root@jouet ~]# perf evlist -v
>>     cycles:ppp: size: 112, { sample_period, sample_freq }: 4000,
>> sample_type: IP|TID|TIME|CALLCHAIN|CPU|PERIOD, disabled: 1, inherit: 1,
>> mmap: 1, comm: 1, freq: 1, task: 1, precise_ip: 3, sample_id_all: 1,
>> exclude_guest: 1, mmap2: 1, comm_exec: 1
>>
>> Change the has_traces check to look for the sched_switch event. Analysis
>> for perf sched timehist requires at least this event.
>>
>> Now when analyzing a file without sched tracepoints you get:
>>
>>     root@f21-vbox:/tmp$ perf sched timehist
>>     No sched_switch events found. Have you run 'perf sched record'?
>>
>> Signed-off-by: David Ahern <dsahern@gmail.com>
> 
> Acked-by: Namhyung Kim <namhyung@kernel.org>
> 
> Thanks,
> Namhyung
> 

Arnaldo: I think this one has been overlooked

  reply	other threads:[~2016-12-05 23:41 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-11-29 20:39 David Ahern
2016-11-30  5:31 ` Namhyung Kim
2016-12-05 23:41   ` David Ahern [this message]
2016-12-06 16:14     ` Arnaldo Carvalho de Melo
2016-12-07 18:24 ` [tip:perf/core] " tip-bot for David Ahern

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=0b7e62e2-ef1d-6ad1-86c7-16c32c83a94f@gmail.com \
    --to=dsahern@gmail.com \
    --cc=acme@kernel.org \
    --cc=jolsa@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@kernel.org \
    --cc=namhyung@kernel.org \
    --cc=peterz@infradead.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox

Powered by JetHome