public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Arnaldo Carvalho de Melo <acme@kernel.org>
To: Namhyung Kim <namhyung@kernel.org>
Cc: Jiri Olsa <jolsa@redhat.com>, Ingo Molnar <mingo@kernel.org>,
	Peter Zijlstra <peterz@infradead.org>,
	LKML <linux-kernel@vger.kernel.org>,
	Andi Kleen <ak@linux.intel.com>, Ian Rogers <irogers@google.com>,
	Stephane Eranian <eranian@google.com>,
	Changbin Du <changbin.du@gmail.com>
Subject: Re: [PATCH 1/2] perf ftrace: Add -n/--use-nsec option for latency
Date: Tue, 22 Mar 2022 17:42:57 -0300	[thread overview]
Message-ID: <Yjo00URy0mhUnNxL@kernel.org> (raw)
In-Reply-To: <20220321234609.90455-1-namhyung@kernel.org>

Em Mon, Mar 21, 2022 at 04:46:08PM -0700, Namhyung Kim escreveu:
> Sometimes we want to see nano-second granularity.
> 
>   $ sudo perf ftrace latency -T dput -a -n sleep 1
>   #   DURATION     |      COUNT | GRAPH                          |
>        0 - 1    us |          0 |                                |
>        1 - 2    ns |          0 |                                |
>        2 - 4    ns |          0 |                                |
>        4 - 8    ns |          0 |                                |
>        8 - 16   ns |          0 |                                |
>       16 - 32   ns |          0 |                                |
>       32 - 64   ns |          0 |                                |
>       64 - 128  ns |    1163434 | ##############                 |
>      128 - 256  ns |     914102 | #############                  |
>      256 - 512  ns |        884 |                                |
>      512 - 1024 ns |        613 |                                |
>        1 - 2    us |         31 |                                |
>        2 - 4    us |         17 |                                |
>        4 - 8    us |          7 |                                |
>        8 - 16   us |        123 |                                |


Thanks, applied.

- Arnaldo


      parent reply	other threads:[~2022-03-22 20:43 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-03-21 23:46 [PATCH 1/2] perf ftrace: Add -n/--use-nsec option for latency Namhyung Kim
2022-03-21 23:46 ` [PATCH 2/2] perf ftrace: Update documentation of ftrace command Namhyung Kim
2022-03-22 20:42 ` Arnaldo Carvalho de Melo [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=Yjo00URy0mhUnNxL@kernel.org \
    --to=acme@kernel.org \
    --cc=ak@linux.intel.com \
    --cc=changbin.du@gmail.com \
    --cc=eranian@google.com \
    --cc=irogers@google.com \
    --cc=jolsa@redhat.com \
    --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