From: Michael Ellerman <mpe@ellerman.id.au>
To: Segher Boessenkool <segher@kernel.crashing.org>,
"Paul A. Clarke" <pc@us.ibm.com>
Cc: Kajol Jain <kjain@linux.ibm.com>,
maddy@linux.vnet.ibm.com, rnsastry@linux.ibm.com,
linuxppc-dev@lists.ozlabs.org, linux-kernel@vger.kernel.org,
acme@kernel.org, linux-perf-users@vger.kernel.org,
atrajeev@linux.vnet.ibm.com, jolsa@redhat.com
Subject: Re: [PATCH] perf vendor events power10: Add metric events json file for power10 platform
Date: Fri, 08 Oct 2021 16:58:52 +1100 [thread overview]
Message-ID: <875yu8njkz.fsf@mpe.ellerman.id.au> (raw)
In-Reply-To: <20211007184337.GN10333@gate.crashing.org>
Segher Boessenkool <segher@kernel.crashing.org> writes:
> On Thu, Oct 07, 2021 at 08:47:50AM -0500, Paul A. Clarke wrote:
>> On Wed, Oct 06, 2021 at 12:32:48PM -0500, Paul A. Clarke wrote:
>> > > + {
>> > > + "BriefDescription": "Average cycles per instruction when the instruction finishes at dispatch",
>> >
>> > I'm not sure what that means.
>>
>> After doing a bit of research, I think it might be a bit more clear as:
>> "Average cycles per instruction when the NTF instruction finishes at dispatch"
>
> Is "next to finish" some defined and/or sensible term in this context?
> Or do you mean NTC here? Or what :-)
Yeah I am also more familiar with NTC.
But those descriptions originally come from a spreadsheet we're given,
and they do include NTF as an acronym.
eg. search for NTF in here:
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/tree/tools/perf/pmu-events/arch/powerpc/power9/metrics.json
From the context it does presumably mean "next to finish".
cheers
next prev parent reply other threads:[~2021-10-08 5:58 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-10-06 7:31 [PATCH] perf vendor events power10: Add metric events json file for power10 platform Kajol Jain
2021-10-06 17:32 ` Paul A. Clarke
2021-10-07 13:47 ` Paul A. Clarke
2021-10-07 18:43 ` Segher Boessenkool
2021-10-08 5:58 ` Michael Ellerman [this message]
2021-10-08 7:48 ` kajoljain
2021-10-08 10:23 ` James Clark
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=875yu8njkz.fsf@mpe.ellerman.id.au \
--to=mpe@ellerman.id.au \
--cc=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=pc@us.ibm.com \
--cc=rnsastry@linux.ibm.com \
--cc=segher@kernel.crashing.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