From: Arnaldo Carvalho de Melo <acme@kernel.org>
To: Jiri Olsa <jolsa@redhat.com>
Cc: kan.liang@intel.com, linux-kernel@vger.kernel.org, ak@linux.intel.com
Subject: Re: [PATCH V8 0/4] perf tools: pmu event new style format fix
Date: Wed, 15 Oct 2014 16:13:26 -0300 [thread overview]
Message-ID: <20141015191326.GO3198@kernel.org> (raw)
In-Reply-To: <20141015150054.GA20818@krava.redhat.com>
Em Wed, Oct 15, 2014 at 05:00:54PM +0200, Jiri Olsa escreveu:
> On Tue, Oct 07, 2014 at 11:08:48AM -0400, kan.liang@intel.com wrote:
> > From: Kan Liang <kan.liang@intel.com>
> >
> > There are two types of pmu event stytle formats, "pmu_event_name"
> > or "cpu/pmu_event_name/". However, there is a bug on supporting these
> > two formats, especially when they mixed with other perf events.
> > The patch set intends to fix this issue.
> >
> > The patch set has been tested by perf automated test "./perf test parse -v"
> > on haswell, ivybridge and Romley platform.
> > The patch set also has been tested on haswell by the following script.
> > (Note: please make sure that your test system support TSX and
> > L1-dcache-loads events. Otherwise, you may want to change the events
> > to other pmu events.)
>
> Acked-by: Jiri Olsa <jolsa@kernel.org>
Thanks, applied the series.
- Arnaldo
prev parent reply other threads:[~2014-10-15 19:13 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-10-07 15:08 kan.liang
2014-10-07 15:08 ` [PATCH V8 1/4] Revert "perf tools: Default to cpu// for events v5" kan.liang
2014-10-16 5:22 ` [tip:perf/urgent] " tip-bot for Kan Liang
2014-10-07 15:08 ` [PATCH V8 2/4] perf tools: parse the pmu event prefix and suffix kan.liang
2014-10-16 5:22 ` [tip:perf/urgent] perf tools: Parse " tip-bot for Kan Liang
2014-10-07 15:08 ` [PATCH V8 3/4] perf tools: Add support to new style format of kernel PMU event kan.liang
2014-10-16 5:22 ` [tip:perf/urgent] " tip-bot for Kan Liang
2014-10-07 15:08 ` [PATCH V8 4/4] perf tools: Add test case for pmu event new style format kan.liang
2014-10-16 5:23 ` [tip:perf/urgent] perf test: " tip-bot for Kan Liang
2014-10-13 15:43 ` [PATCH V8 0/4] perf tools: pmu event new style format fix Liang, Kan
2014-10-13 17:05 ` Jiri Olsa
2014-10-14 14:02 ` [PATCH] perf tools: Do not call pevent_free_format when deleting tracepoint Jiri Olsa
2014-10-15 15:00 ` [PATCH V8 0/4] perf tools: pmu event new style format fix Jiri Olsa
2014-10-15 19:13 ` 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=20141015191326.GO3198@kernel.org \
--to=acme@kernel.org \
--cc=ak@linux.intel.com \
--cc=jolsa@redhat.com \
--cc=kan.liang@intel.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
Powered by JetHome