public inbox for linux-arm-kernel@lists.infradead.org
 help / color / mirror / Atom feed
From: Ilkka Koskinen <ilkka@os.amperecomputing.com>
To: Robin Murphy <robin.murphy@arm.com>
Cc: Ilkka Koskinen <ilkka@os.amperecomputing.com>,
	will@kernel.org,  mark.rutland@arm.com,
	linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH 2/4] perf/arm-cmn: Add CMN-650 support
Date: Thu, 21 Apr 2022 14:26:53 -0700 (PDT)	[thread overview]
Message-ID: <alpine.DEB.2.22.394.2204211414390.3571@ubuntu200401> (raw)
In-Reply-To: <3e51c8c1-c753-27ee-7bd2-b50c9306a6c2@arm.com>

[-- Attachment #1: Type: text/plain, Size: 3330 bytes --]



On Thu, 21 Apr 2022, Robin Murphy wrote:

> On 2022-04-21 08:25, Ilkka Koskinen wrote:
>> 
>> I still have a couple tiny comments. Otherwise the patch set looks good to 
>> me.
>> 
>> On Mon, 18 Apr 2022, Robin Murphy wrote:
>>> Add the identifiers and events for CMN-650, which slots into its
>>> evolutionary position between CMN-600 and the 700-series products.
>>> Imagine CMN-600 made bigger, and with most of the rough edges smoothed
>>> off, but that then balanced out by some bonkers PMU functionality for
>>> the new HN-P enhancement in CMN-650r2.
>>> 
>>> Most of the CXG events are actually common to newer revisions of CMN-600
>>> too, so they're arguably a little late; oh well.
>>> 
>>> Signed-off-by: Robin Murphy <robin.murphy@arm.com>
>>> ---
>>> drivers/perf/arm-cmn.c | 222 ++++++++++++++++++++++++++++++++---------
>>> 1 file changed, 176 insertions(+), 46 deletions(-)
>>> 
>>> diff --git a/drivers/perf/arm-cmn.c b/drivers/perf/arm-cmn.c
>>> index 9c1d82be7a2f..cce8516d465c 100644
>>> --- a/drivers/perf/arm-cmn.c
>>> +++ b/drivers/perf/arm-cmn.c


>>> @@ -607,12 +624,29 @@ static umode_t arm_cmn_event_attr_is_visible(struct 
>>> kobject *kobj,
>>>     }
>>> 
>>>     /* Revision-specific differences */
>>> -    if (cmn->model == CMN600 && cmn->rev < CMN600_R1P2) {
>>> -        if (eattr->type == CMN_TYPE_HNF && eattr->eventid == 0x1b)
>>> -            return 0;
>>> +    if (cmn->model == CMN600) {
>>> +        if (cmn->rev < CMN600_R1P3) {
>>> +            if (type == CMN_TYPE_CXRA && eventid > 0x10)
>>> +                return 0;
>>> +        }
>>> +        if (cmn->rev < CMN600_R1P2) {
>>> +            if (type == CMN_TYPE_HNF && eventid == 0x1b)
>>> +                return 0;
>>> +            if (type == CMN_TYPE_CXRA || type == CMN_TYPE_CXHA)
>>> +                return 0;
>>> +        }
>>> +    } else if (cmn->model == CMN650) {
>>> +        if (cmn->rev < CMN650_R2P0 || cmn->rev == CMN650_R1P2) {
>>> +            if (type == CMN_TYPE_HNF && eventid > 0x22)
>>> +                return 0;
>>> +            if (type == CMN_TYPE_SBSX && eventid == 0x17)
>>> +                return 0;
>>> +            if (type == CMN_TYPE_RNI && eventid > 0x10)
>>> +                return 0;
>>> +        }
>> 
>> What's the plan with cmn-650 r2p0 event settings? There seem to be a few 
>> extra ones made visible now. I'm fine with updating this patch or taking 
>> care of them in a separate one, which ever makes more sense.
>
> arm_cmn_event_attrs *should* contain all the events supported by r2p0, with 
> the ones not present on earlier revisions then being filtered out here. Have 
> I missed anything? Note that HN-Ps don't need per-event filtering since that 
> node type simply doesn't exist prior to CMN-650 r2, so is already filtered by 
> arm_cmn_node().

Ah, I was comparing the code and perf output to HN-F and RN-I event 
summary tables in TRM. The tables are missing some of the events where as 
the event_sel register descriptions have all of them listed. So, that was 
my mistake and everything looks good.

Cheers, Ilkka

>
> Thanks,
> Robin.
>

[-- Attachment #2: Type: text/plain, Size: 176 bytes --]

_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel

  reply	other threads:[~2022-04-21 21:28 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-04-18 22:57 [PATCH 0/4] perf/arm-cmn: Add CMN-650 and CMN-700 Robin Murphy
2022-04-18 22:57 ` [PATCH 1/4] dt-bindings: perf: arm-cmn: " Robin Murphy
2022-04-26 20:12   ` Rob Herring
2022-04-18 22:57 ` [PATCH 2/4] perf/arm-cmn: Add CMN-650 support Robin Murphy
2022-04-19 23:05   ` Ilkka Koskinen
2022-04-19 23:47     ` Ilkka Koskinen
2022-04-20  9:26       ` Will Deacon
2022-04-20 10:12     ` Robin Murphy
2022-04-21  7:09       ` Ilkka Koskinen
2022-04-21  7:25   ` Ilkka Koskinen
2022-04-21  9:46     ` Robin Murphy
2022-04-21 21:26       ` Ilkka Koskinen [this message]
2022-04-18 22:57 ` [PATCH 3/4] perf/arm-cmn: Refactor occupancy filter selector Robin Murphy
2022-04-18 22:57 ` [PATCH 4/4] perf/arm-cmn: Add CMN-700 support Robin Murphy
2022-04-21  7:54 ` [PATCH 0/4] perf/arm-cmn: Add CMN-650 and CMN-700 Ilkka Koskinen
2022-05-06 14:43 ` Will Deacon
2022-05-10 17:15 ` Qian Cai
2022-05-10 17:50   ` Robin Murphy
2022-05-10 19:38     ` Qian Cai
2022-05-10 21:05       ` Robin Murphy
2022-05-10 20:09     ` Qian Cai

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=alpine.DEB.2.22.394.2204211414390.3571@ubuntu200401 \
    --to=ilkka@os.amperecomputing.com \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=mark.rutland@arm.com \
    --cc=robin.murphy@arm.com \
    --cc=will@kernel.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