From: Madhavan Srinivasan <maddy@linux.vnet.ibm.com>
To: Michael Ellerman <mpe@ellerman.id.au>
Cc: linuxppc-dev@lists.ozlabs.org
Subject: Re: [PATCH v3 3/4] powerpc/perf: PowerISA v3.0 raw event format encoding
Date: Wed, 30 Nov 2016 20:15:17 +0530 [thread overview]
Message-ID: <32855b39-76c5-7bc2-cc73-9e25c4fb13a7@linux.vnet.ibm.com> (raw)
In-Reply-To: <87bmwyrjgv.fsf@concordia.ellerman.id.au>
On Tuesday 29 November 2016 10:06 AM, Michael Ellerman wrote:
> Madhavan Srinivasan <maddy@linux.vnet.ibm.com> writes:
>
>> Patch to update the PowerISA v3.0 raw event encoding format
>> information and add support for the same in Power9-pmu.c.
> I'm not sure if calling this the "PowerISA v3.0" encoding is right. It's
> not actually specified in the ISA anywhere right?
Yes will make the changes.
Maddy
>
> Maybe it should just be the "P9 encoding" ?
>
> Though admittedly that is slightly confusing because P9 DD1 doesn't
> implement it.
>
> cheers
>
next prev parent reply other threads:[~2016-11-30 14:45 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-11-28 1:21 [PATCH v3 0/4] Support PowerISA v3.0 PMU Raw event format Madhavan Srinivasan
2016-11-28 1:21 ` [PATCH v3 1/4] powerpc/perf: factor out the event format field Madhavan Srinivasan
2016-11-28 1:21 ` [PATCH v3 2/4] powerpc/perf: update attribute_group data structure Madhavan Srinivasan
2016-11-28 1:21 ` [PATCH v3 3/4] powerpc/perf: PowerISA v3.0 raw event format encoding Madhavan Srinivasan
2016-11-29 4:36 ` Michael Ellerman
2016-11-30 14:45 ` Madhavan Srinivasan [this message]
2016-11-28 1:21 ` [PATCH v3 4/4] powerpc/perf: macros for PowerISA v3.0 " Madhavan Srinivasan
2016-11-29 4:45 ` Michael Ellerman
2016-11-30 14:48 ` Madhavan Srinivasan
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=32855b39-76c5-7bc2-cc73-9e25c4fb13a7@linux.vnet.ibm.com \
--to=maddy@linux.vnet.ibm.com \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=mpe@ellerman.id.au \
/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).