From: Arnaldo Carvalho de Melo <acme@kernel.org>
To: kajoljain <kjain@linux.ibm.com>
Cc: Nageswara Sastry <rnsastry@linux.ibm.com>,
"Paul A. Clarke" <pc@us.ibm.com>,
maddy@linux.vnet.ibm.com,
Athira Rajeev <atrajeev@linux.vnet.ibm.com>,
linux-kernel@vger.kernel.org, jolsa@redhat.com,
mpe@ellerman.id.au, ravi.bangoria@linux.ibm.com,
linux-perf-users@vger.kernel.org, linuxppc-dev@lists.ozlabs.org
Subject: Re: [PATCH] perf vendor events: Fix eventcode of power10 json events
Date: Fri, 28 May 2021 09:21:27 -0300 [thread overview]
Message-ID: <YLDgRyvhJt+bbmn/@kernel.org> (raw)
In-Reply-To: <da7617f8-050e-c597-ec3d-5e803775252c@linux.ibm.com>
Em Fri, May 28, 2021 at 01:26:50PM +0530, kajoljain escreveu:
>
>
> On 5/26/21 11:42 AM, Nageswara Sastry wrote:
> >
> >
> >> On 25-May-2021, at 8:57 PM, Paul A. Clarke <pc@us.ibm.com> wrote:
> >>>
> >> I lost the original message, but Nageswara Sastry said:
> >>> 1. Extracted all the 244 events from the patch.
> >>> 2. Check them in 'perf list' - all 244 events found
> >>> 3. Ran all the events with 'perf stat -e "event name" sleep 1', all ran fine.
> >>> No errors were seen in 'dmesg'
> >>
> >> I count 255 events.
> >>
> >> PC
> >
> > Seems while extracting I filtered out newly added ones, so I got 244(255-11).
> > Now checked with all 255 events. Thanks for pointing out.
> >
> > Thanks!!
> > R.Nageswara Sastry
> >
>
> Hi Paul/Nageswara,
> Yes we currently have 255 power10 json events which is updated in this patch.
> Thanks for reviewing the patch.
>
> Arnaldo can you pull this patch if changes looks fine to you.
Applied to test/urgent, thanks everybody for the tests and reviews, all
tags collected.
- Arnaldo
prev parent reply other threads:[~2021-05-28 12:21 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-05-25 6:37 [PATCH] perf vendor events: Fix eventcode of power10 json events Kajol Jain
2021-05-25 13:18 ` Nageswara Sastry
2021-05-25 14:42 ` Paul A. Clarke
2021-05-25 15:27 ` Paul A. Clarke
2021-05-26 6:12 ` Nageswara Sastry
2021-05-28 7:56 ` kajoljain
2021-05-28 12:21 ` 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=YLDgRyvhJt+bbmn/@kernel.org \
--to=acme@kernel.org \
--cc=atrajeev@linux.vnet.ibm.com \
--cc=jolsa@redhat.com \
--cc=kjain@linux.ibm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-perf-users@vger.kernel.org \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=maddy@linux.vnet.ibm.com \
--cc=mpe@ellerman.id.au \
--cc=pc@us.ibm.com \
--cc=ravi.bangoria@linux.ibm.com \
--cc=rnsastry@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).