All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jiri Olsa <jolsa@redhat.com>
To: Hyeim Yang <yanghyeimm@gmail.com>
Cc: Arnaldo Carvalho de Melo <acme@kernel.org>,
	linux-kernel@vger.kernel.org, Jiri Olsa <jolsa@kernel.org>,
	Namhyung Kim <namhyung@kernel.org>,
	Taeung Song <taeung@kosslab.kr>
Subject: Re: [PATCH] perf report/top: Add a tip about source line matching
Date: Mon, 20 Nov 2017 08:45:41 +0100	[thread overview]
Message-ID: <20171120074541.GA5684@krava> (raw)
In-Reply-To: <1510988479-2772-1-git-send-email-yanghyeimm@gmail.com>

On Sat, Nov 18, 2017 at 04:01:19PM +0900, Hyeim Yang wrote:
> Cc: Jiri Olsa <jolsa@kernel.org>
> Cc: Namhyung Kim <namhyung@kernel.org>
> Cc: Taeung Song <taeung@kosslab.kr>
> ---
>  tools/perf/Documentation/tips.txt | 1 +
>  1 file changed, 1 insertion(+)
> 
> diff --git a/tools/perf/Documentation/tips.txt b/tools/perf/Documentation/tips.txt
> index db0ca30..b60616a 100644
> --- a/tools/perf/Documentation/tips.txt
> +++ b/tools/perf/Documentation/tips.txt
> @@ -32,3 +32,4 @@ Order by the overhead of source file name and line number: perf report -s srclin
>  System-wide collection from all CPUs: perf record -a
>  Show current config key-value pairs: perf config --list
>  Show user configuration overrides: perf config --user --list
> +Print matching source lines (may be slow): perf annotate --print-line <symbol>

this works only in stdio, so we need to add --stdio option as well

jirka

      reply	other threads:[~2017-11-20  7:45 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-11-18  7:01 [PATCH] perf report/top: Add a tip about source line matching Hyeim Yang
2017-11-20  7:45 ` Jiri Olsa [this message]

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=20171120074541.GA5684@krava \
    --to=jolsa@redhat.com \
    --cc=acme@kernel.org \
    --cc=jolsa@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=namhyung@kernel.org \
    --cc=taeung@kosslab.kr \
    --cc=yanghyeimm@gmail.com \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.