From: Arnaldo Carvalho de Melo <acme@kernel.org>
To: Ravi Bangoria <ravi.bangoria@linux.vnet.ibm.com>
Cc: sukadev@linux.vnet.ibm.com, alexander.shishkin@linux.intel.com,
jolsa@redhat.com, namhyung@kernel.org, maddy@linux.vnet.ibm.com,
shriyak@linux.vnet.ibm.com, linux-kernel@vger.kernel.org,
peterz@infradead.org, mingo@kernel.org, mpetlan@redhat.com,
William Cohen <wcohen@redhat.com>
Subject: Re: [PATCH] perf tool powerpc: Add Power9 DD2.1 PVR
Date: Wed, 22 Nov 2017 16:24:41 -0300 [thread overview]
Message-ID: <20171122192441.GA2383@kernel.org> (raw)
In-Reply-To: <20171122160850.1878-1-ravi.bangoria@linux.vnet.ibm.com>
Em Wed, Nov 22, 2017 at 09:38:50PM +0530, Ravi Bangoria escreveu:
> From: Madhavan Srinivasan <maddy@linux.vnet.ibm.com>
>
> This will enable parsing JSON files on Power9 DD2.1.
Ravi,
Can you take a look at this patch posted today by Will Cohen:
Subject: [PATCH] Use more flexible pattern matching for CPU identification for mapfile.csv
Message-Id: <20171122160849.8400-1-wcohen@redhat.com>
Oops, he forgot to send it to lkml, I'll reply to his message and add
you and lkml, please check that approach.
- Arnaldo
> Signed-off-by: Madhavan Srinivasan <maddy@linux.vnet.ibm.com>
> Signed-off-by: Ravi Bangoria <ravi.bangoria@linux.vnet.ibm.com>
> ---
> tools/perf/pmu-events/arch/powerpc/mapfile.csv | 1 +
> 1 file changed, 1 insertion(+)
>
> diff --git a/tools/perf/pmu-events/arch/powerpc/mapfile.csv b/tools/perf/pmu-events/arch/powerpc/mapfile.csv
> index a0f3a11ca19f..83b98ec8dbab 100644
> --- a/tools/perf/pmu-events/arch/powerpc/mapfile.csv
> +++ b/tools/perf/pmu-events/arch/powerpc/mapfile.csv
> @@ -23,3 +23,4 @@
> 004e0100,1,power9,core
> 004e0200,1,power9,core
> 004e1200,1,power9,core
> +004e1201,1,power9,core
> --
> 2.13.6
prev parent reply other threads:[~2017-11-22 19:24 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-11-22 16:08 [PATCH] perf tool powerpc: Add Power9 DD2.1 PVR Ravi Bangoria
2017-11-22 19:24 ` 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=20171122192441.GA2383@kernel.org \
--to=acme@kernel.org \
--cc=alexander.shishkin@linux.intel.com \
--cc=jolsa@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=maddy@linux.vnet.ibm.com \
--cc=mingo@kernel.org \
--cc=mpetlan@redhat.com \
--cc=namhyung@kernel.org \
--cc=peterz@infradead.org \
--cc=ravi.bangoria@linux.vnet.ibm.com \
--cc=shriyak@linux.vnet.ibm.com \
--cc=sukadev@linux.vnet.ibm.com \
--cc=wcohen@redhat.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