From: Arnaldo Carvalho de Melo <acme@kernel.org>
To: Jiri Olsa <jolsa@redhat.com>
Cc: Andi Kleen <andi@firstfloor.org>,
jolsa@kernel.org, eranian@google.com,
linux-kernel@vger.kernel.org, Andi Kleen <ak@linux.intel.com>
Subject: Re: [PATCH 1/6] perf, tools, stat: Check existence of frontend/backed stalled cycles
Date: Mon, 29 Feb 2016 11:44:24 -0300 [thread overview]
Message-ID: <20160229144424.GA32719@kernel.org> (raw)
In-Reply-To: <20160229101035.GA14521@krava.redhat.com>
Em Mon, Feb 29, 2016 at 11:10:35AM +0100, Jiri Olsa escreveu:
> On Fri, Feb 26, 2016 at 04:27:56PM -0800, Andi Kleen wrote:
> > From: Andi Kleen <ak@linux.intel.com>
> >
> > Only put the frontend/backend stalled cycles into the default
> > perf stat events when the CPU actually supports them.
> >
> > This avoids empty columns with --metric-only on newer Intel CPUs.
> >
> > Signed-off-by: Andi Kleen <ak@linux.intel.com>
>
> Acked-by: Jiri Olsa <jolsa@kernel.org>
Applied and tested, thanks!
- Arnaldo
next prev parent reply other threads:[~2016-02-29 14:44 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-02-27 0:27 perf, tools: Refactor and support interval and CSV metrics Andi Kleen
2016-02-27 0:27 ` [PATCH 1/6] perf, tools, stat: Check existence of frontend/backed stalled cycles Andi Kleen
2016-02-29 10:10 ` Jiri Olsa
2016-02-29 14:44 ` Arnaldo Carvalho de Melo [this message]
2016-03-05 8:14 ` [tip:perf/core] perf " tip-bot for Andi Kleen
2016-02-27 0:27 ` [PATCH 2/6] perf, tools, stat: Implement CSV metrics output Andi Kleen
2016-02-29 10:20 ` Jiri Olsa
2016-02-29 14:43 ` Arnaldo Carvalho de Melo
2016-02-27 0:27 ` [PATCH 3/6] perf, tools, stat: Support metrics in --per-core/socket mode Andi Kleen
2016-02-27 0:27 ` [PATCH 4/6] perf, tools, stat: Document CSV format in manpage Andi Kleen
2016-02-27 0:28 ` [PATCH 5/6] perf, tools, stat: Implement --metric-only mode Andi Kleen
2016-02-27 0:28 ` [PATCH 6/6] perf, tools, stat: Add --metric-only support for -A Andi Kleen
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=20160229144424.GA32719@kernel.org \
--to=acme@kernel.org \
--cc=ak@linux.intel.com \
--cc=andi@firstfloor.org \
--cc=eranian@google.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 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.