From: Jiri Olsa <jolsa@redhat.com>
To: Namhyung Kim <namhyung@kernel.org>
Cc: Arnaldo Carvalho de Melo <acme@kernel.org>,
Peter Zijlstra <a.p.zijlstra@chello.nl>,
Ingo Molnar <mingo@kernel.org>, Paul Mackerras <paulus@samba.org>,
Namhyung Kim <namhyung.kim@lge.com>,
LKML <linux-kernel@vger.kernel.org>,
David Ahern <dsahern@gmail.com>,
Adrian Hunter <adrian.hunter@intel.com>,
Andi Kleen <andi@firstfloor.org>, Milian Wolff <mail@milianw.de>
Subject: Re: [PATCH v2 2/2] perf record: Show precise number of samples
Date: Fri, 28 Nov 2014 13:44:26 +0100 [thread overview]
Message-ID: <20141128124426.GE27703@krava.brq.redhat.com> (raw)
In-Reply-To: <1417158859-31538-1-git-send-email-namhyung@kernel.org>
On Fri, Nov 28, 2014 at 04:14:19PM +0900, Namhyung Kim wrote:
> After perf record finishes, it prints file size and number of samples
> in the file but this info is wrong since it assumes typical sample
> size of 24 bytes and divides file size by the value.
>
> However as we post-process recorded samples for build-id, it can show
> correct number like below. If build-id post-processing is not requested
> just omit the wrong number of samples.
>
> $ perf record noploop 1
> [ perf record: Woken up 1 times to write data ]
> [ perf record: Captured and wrote 0.159 MB perf.data (3989 samples) ]
>
> $ perf report --stdio -n
> # To display the perf.data header info, please use --header/--header-only options.
> #
> # Samples: 3K of event 'cycles'
> # Event count (approx.): 3771330663
> #
> # Overhead Samples Command Shared Object Symbol
> # ........ ............ ....... ................ ..........................
> #
> 99.90% 3982 noploop noploop [.] main
> 0.09% 1 noploop ld-2.17.so [.] _dl_check_map_versions
> 0.01% 1 noploop [kernel.vmlinux] [k] setup_arg_pages
> 0.00% 5 noploop [kernel.vmlinux] [k] intel_pmu_enable_all
>
> Reported-by: Milian Wolff <mail@milianw.de>
> Signed-off-by: Namhyung Kim <namhyung@kernel.org>
eeeey great, I mean.. finally ;-)
Reviewed-by: Jiri Olsa <jolsa@kernel.org>
thanks,
jirka
next prev parent reply other threads:[~2014-11-28 12:45 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-11-28 7:11 [PATCH 1/2] perf tools: Do not use __perf_session__process_events() directly Namhyung Kim
2014-11-28 7:11 ` [PATCH 2/2] perf record: Show precise number of samples Namhyung Kim
2014-11-28 7:14 ` [PATCH v2 " Namhyung Kim
2014-11-28 12:44 ` Jiri Olsa [this message]
2014-11-28 17:56 ` Andi Kleen
2014-11-28 21:48 ` Arnaldo Carvalho de Melo
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=20141128124426.GE27703@krava.brq.redhat.com \
--to=jolsa@redhat.com \
--cc=a.p.zijlstra@chello.nl \
--cc=acme@kernel.org \
--cc=adrian.hunter@intel.com \
--cc=andi@firstfloor.org \
--cc=dsahern@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mail@milianw.de \
--cc=mingo@kernel.org \
--cc=namhyung.kim@lge.com \
--cc=namhyung@kernel.org \
--cc=paulus@samba.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
all inboxes | Powered by JetHome®