linux-perf-users.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Arnaldo Carvalho de Melo <acme@kernel.org>
To: Jiri Olsa <jolsa@redhat.com>, Andi Kleen <ak@linux.intel.com>
Cc: Andi Kleen <andi@firstfloor.org>,
	Agustin Vega-Frias <agustinv@codeaurora.org>,
	linux-kernel@vger.kernel.org, linux-perf-users@vger.kernel.org,
	linux-arm-kernel@lists.infradead.org,
	Peter Zijlstra <peterz@infradead.org>,
	Ingo Molnar <mingo@redhat.com>,
	Alexander Shishkin <alexander.shishkin@linux.intel.com>,
	Namhyung Kim <namhyung@kernel.org>,
	timur@codeaurora.org
Subject: Re: [RFC V3 0/3] perf stat: improvements for handling of multiple PMUs
Date: Wed, 7 Mar 2018 11:30:04 -0300	[thread overview]
Message-ID: <20180307143004.GH3701@kernel.org> (raw)
In-Reply-To: <20180307135105.GA9080@krava>

Em Wed, Mar 07, 2018 at 02:51:05PM +0100, Jiri Olsa escreveu:
> On Wed, Mar 07, 2018 at 10:36:30AM -0300, Arnaldo Carvalho de Melo wrote:
> > Em Wed, Mar 07, 2018 at 11:04:08AM +0100, Jiri Olsa escreveu:
> > > On Tue, Mar 06, 2018 at 09:04:41AM -0500, Agustin Vega-Frias wrote:
> > > > This series of patches adds some simple improvements to the way perf stat
> > > > handles PMUs that have multiple instances by:
> > > > 
> > > > 1. Adding glob-like matching in addition to the prefix-based matching
> > > >    introduced previously (patch 1).
> > > > 2. Adding the ability to recover the PMU names when printing the events
> > > >    separately with the --no-merge option (patch 2).
> > > > 3. Restoring auto-merge for events created by prefix or glob-like match
> > > >    (patch 3). Note that this still keeps the behavior that disables
> > > >    auto-merging of legacy symbolic events (e.g. cycles).
> > > > 
> > > > V3:
> > > > 
> > > > - Consolidated prefix and glob matching into a single glob match with a
> > > >   trailing * to maintain prefix matching and have more consistent behavior.
> > > >   E.g., all of these match all the uncore_imc PMUs: imc, imc*, *imc, *imc*
> > > 
> > > Acked-by: Jiri Olsa <jolsa@kernel.org>
> > 
> > Thanks, applied.
> > 
> > I guess Andi had Acked or Reviewed this, no?
> 
> not the latest version.. please wait for his ack

Sure, I have this applied to my local branch, and will add his acks or
drop the patches if he still has any objection, Andi?

- Arnaldo

  reply	other threads:[~2018-03-07 14:30 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-03-06 14:04 [RFC V3 0/3] perf stat: improvements for handling of multiple PMUs Agustin Vega-Frias
2018-03-06 14:04 ` [RFC V3 1/3] perf, tools: Support wildcards on pmu name in dynamic pmu events Agustin Vega-Frias
2018-03-07 16:02   ` Arnaldo Carvalho de Melo
2018-03-07 17:39     ` Agustin Vega-Frias
2018-03-07 18:54       ` Andi Kleen
2018-03-07 19:05         ` Arnaldo Carvalho de Melo
2018-03-07 19:05           ` Arnaldo Carvalho de Melo
2018-03-07 19:39             ` Arnaldo Carvalho de Melo
2018-03-07 19:49               ` Agustin Vega-Frias
2018-03-07 19:58                 ` Arnaldo Carvalho de Melo
2018-03-07 20:09                   ` Agustin Vega-Frias
2018-03-07 20:21                     ` Jiri Olsa
2018-03-07 20:33                     ` Arnaldo Carvalho de Melo
2018-03-06 14:04 ` [RFC V3 2/3] perf, tools: Display pmu name when printing unmerged events in stat Agustin Vega-Frias
2018-03-06 14:04 ` [RFC V3 3/3] perf pmu: Auto-merge PMU events created by prefix or glob match Agustin Vega-Frias
2018-03-07 10:04 ` [RFC V3 0/3] perf stat: improvements for handling of multiple PMUs Jiri Olsa
2018-03-07 13:36   ` Arnaldo Carvalho de Melo
2018-03-07 13:51     ` Jiri Olsa
2018-03-07 14:30       ` Arnaldo Carvalho de Melo [this message]
2018-03-07 17:09         ` 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=20180307143004.GH3701@kernel.org \
    --to=acme@kernel.org \
    --cc=agustinv@codeaurora.org \
    --cc=ak@linux.intel.com \
    --cc=alexander.shishkin@linux.intel.com \
    --cc=andi@firstfloor.org \
    --cc=jolsa@redhat.com \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-perf-users@vger.kernel.org \
    --cc=mingo@redhat.com \
    --cc=namhyung@kernel.org \
    --cc=peterz@infradead.org \
    --cc=timur@codeaurora.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;
as well as URLs for NNTP newsgroup(s).