From: Andi Kleen <andi@firstfloor.org>
To: Jiri Olsa <jolsa@redhat.com>
Cc: Andi Kleen <andi@firstfloor.org>,
acme@kernel.org, jolsa@kernel.org, linux-kernel@vger.kernel.org,
Andi Kleen <ak@linux.intel.com>
Subject: Re: [PATCH] perf, tools, stat: Print warning when no metric with --metric-only
Date: Sat, 12 Mar 2016 00:04:39 +0100 [thread overview]
Message-ID: <20160311230439.GJ5083@two.firstfloor.org> (raw)
In-Reply-To: <20160311080634.GA1052@krava.redhat.com>
> [jolsa@krava perf]$ sudo ./perf stat -a -I 1000 --metric-only
> time insn per cycle branch-misses of all branches
> 1.000370422 0.30 6.77%
> 2.000749536 0.40 5.75%
> 3.001007542 0.28 5.38%
> 4.001324779 0.57 5.83%
> ^C 4.011558899 0.01 0.12%
>
> [jolsa@krava perf]$ sudo ./perf stat -a -I 1000 --metric-only -e cycles
> time No metrics defined by configured events
> 1.000211156
> 2.000432519
Looks good to me. Please submit it.
-Andi
prev parent reply other threads:[~2016-03-11 23:04 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-03-10 14:27 [PATCH] perf, tools, stat: Print warning when no metric with --metric-only Andi Kleen
2016-03-11 8:06 ` Jiri Olsa
2016-03-11 23:04 ` Andi Kleen [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=20160311230439.GJ5083@two.firstfloor.org \
--to=andi@firstfloor.org \
--cc=acme@kernel.org \
--cc=ak@linux.intel.com \
--cc=jolsa@kernel.org \
--cc=jolsa@redhat.com \
--cc=linux-kernel@vger.kernel.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