linux-perf-users.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Arnaldo Carvalho de Melo <acme@kernel.org>
To: Paul Clarke <pc@us.ibm.com>
Cc: linux-perf-users@vger.kernel.org, linux-kernel@vger.kernel.org,
	ananth@linux.vnet.ibm.com, maddy@linux.vnet.ibm.com,
	naveen.n.rao@linux.vnet.ibm.com, sukadev@linux.ibm.com,
	mpe@ellerman.id.au, cel@us.ibm.com,
	Peter Zijlstra <peterz@infradead.org>,
	Ingo Molnar <mingo@redhat.com>,
	Alexander Shishkin <alexander.shishkin@linux.intel.com>,
	Jiri Olsa <jolsa@redhat.com>, Namhyung Kim <namhyung@kernel.org>
Subject: Re: [PATCH v2 0/4] [powerpc] perf vendor events: Add JSON metrics for POWER8
Date: Mon, 11 Feb 2019 12:52:05 -0300	[thread overview]
Message-ID: <20190211155205.GD3269@kernel.org> (raw)
In-Reply-To: <20190207175314.31813-1-pc@us.ibm.com>

Em Thu, Feb 07, 2019 at 12:53:10PM -0500, Paul Clarke escreveu:
> The patches define metrics and metric groups for computation by "perf" for
> POWER8 processors.
> 
> Paul Clarke (4):
>   [powerpc] perf vendor events: Add JSON metrics for POWER8 1/4
>   [powerpc] perf vendor events: Add JSON metrics for POWER8 2/4
>   [powerpc] perf vendor events: Add JSON metrics for POWER8 3/4
>   [powerpc] perf vendor events: Add JSON metrics for POWER8 4/4
> 
> v2:
> The content of these patches was sent previously, to LKML and linux-perf-users,
> but never showed up at linux-perf-users, so I split it into smaller patches
> and am resending.
> 
>  .../arch/powerpc/power8/metrics.json          | 2245 +++++++++++++++++
>  1 file changed, 2245 insertions(+)
>  create mode 100644 tools/perf/pmu-events/arch/powerpc/power8/metrics.json

Thanks, applied, next time please CC:

[acme@quaco perf]$ scripts/get_maintainer.pl tools/perf
Peter Zijlstra <peterz@infradead.org> (supporter:PERFORMANCE EVENTS SUBSYSTEM)
Ingo Molnar <mingo@redhat.com> (supporter:PERFORMANCE EVENTS SUBSYSTEM)
Arnaldo Carvalho de Melo <acme@kernel.org> (supporter:PERFORMANCE EVENTS SUBSYSTEM)
Alexander Shishkin <alexander.shishkin@linux.intel.com> (reviewer:PERFORMANCE EVENTS SUBSYSTEM)
Jiri Olsa <jolsa@redhat.com> (reviewer:PERFORMANCE EVENTS SUBSYSTEM)
Namhyung Kim <namhyung@kernel.org> (reviewer:PERFORMANCE EVENTS SUBSYSTEM)
linux-kernel@vger.kernel.org (open list:PERFORMANCE EVENTS SUBSYSTEM)
[acme@quaco perf]$

So that it gets to my main inbox and may get slightly faster processing.

- Arnaldo

      parent reply	other threads:[~2019-02-11 15:52 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-02-07 17:53 [PATCH v2 0/4] [powerpc] perf vendor events: Add JSON metrics for POWER8 Paul Clarke
2019-02-07 17:53 ` [PATCH v2 1/4] " Paul Clarke
2019-02-07 17:53 ` [PATCH v2 2/4] " Paul Clarke
2019-02-07 17:53 ` [PATCH v2 3/4] " Paul Clarke
2019-02-07 17:53 ` [PATCH v2 4/4] " Paul Clarke
2019-02-11 15:52 ` 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=20190211155205.GD3269@kernel.org \
    --to=acme@kernel.org \
    --cc=alexander.shishkin@linux.intel.com \
    --cc=ananth@linux.vnet.ibm.com \
    --cc=cel@us.ibm.com \
    --cc=jolsa@redhat.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-perf-users@vger.kernel.org \
    --cc=maddy@linux.vnet.ibm.com \
    --cc=mingo@redhat.com \
    --cc=mpe@ellerman.id.au \
    --cc=namhyung@kernel.org \
    --cc=naveen.n.rao@linux.vnet.ibm.com \
    --cc=pc@us.ibm.com \
    --cc=peterz@infradead.org \
    --cc=sukadev@linux.ibm.com \
    /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).