All of lore.kernel.org
 help / color / mirror / Atom feed
From: Robin Murphy <robin.murphy@arm.com>
To: will@kernel.org
Cc: mark.rutland@arm.com, linux-arm-kernel@lists.infradead.org,
	linux-kernel@vger.kernel.org, ilkka@os.amperecomputing.com,
	blakgeof@amazon.com
Subject: [PATCH 0/3] perf: Arm CMN updates
Date: Fri,  7 Jul 2023 17:38:10 +0100	[thread overview]
Message-ID: <cover.1688746690.git.robin.murphy@arm.com> (raw)

Hi all,

Here's another CMN update which unfortunately due to circumstances
didn't manage to be ready in time for 6.5. I realise it's a bit early
now, but I'm about to be offline for 4 weeks so hey. For anyone playing
along at home, the HN-S is not documented not in the CMN-700 TRM, but
in its own special supplement[1].

Thanks,
Robin.

[1] https://developer.arm.com/documentation/108055/0301/?lang=en

Robin Murphy (3):
  perf/arm-cmn: Remove spurious event aliases
  perf/arm-cmn: Refactor HN-F event selector macros
  perf/arm-cmn: Add CMN-700 r3 support

 drivers/perf/arm-cmn.c | 163 ++++++++++++++++++++++++++++++++++-------
 1 file changed, 138 insertions(+), 25 deletions(-)

-- 
2.39.2.101.g768bb238c484.dirty


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

WARNING: multiple messages have this Message-ID (diff)
From: Robin Murphy <robin.murphy@arm.com>
To: will@kernel.org
Cc: mark.rutland@arm.com, linux-arm-kernel@lists.infradead.org,
	linux-kernel@vger.kernel.org, ilkka@os.amperecomputing.com,
	blakgeof@amazon.com
Subject: [PATCH 0/3] perf: Arm CMN updates
Date: Fri,  7 Jul 2023 17:38:10 +0100	[thread overview]
Message-ID: <cover.1688746690.git.robin.murphy@arm.com> (raw)

Hi all,

Here's another CMN update which unfortunately due to circumstances
didn't manage to be ready in time for 6.5. I realise it's a bit early
now, but I'm about to be offline for 4 weeks so hey. For anyone playing
along at home, the HN-S is not documented not in the CMN-700 TRM, but
in its own special supplement[1].

Thanks,
Robin.

[1] https://developer.arm.com/documentation/108055/0301/?lang=en

Robin Murphy (3):
  perf/arm-cmn: Remove spurious event aliases
  perf/arm-cmn: Refactor HN-F event selector macros
  perf/arm-cmn: Add CMN-700 r3 support

 drivers/perf/arm-cmn.c | 163 ++++++++++++++++++++++++++++++++++-------
 1 file changed, 138 insertions(+), 25 deletions(-)

-- 
2.39.2.101.g768bb238c484.dirty


             reply	other threads:[~2023-07-07 16:39 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-07-07 16:38 Robin Murphy [this message]
2023-07-07 16:38 ` [PATCH 0/3] perf: Arm CMN updates Robin Murphy
2023-07-07 16:38 ` [PATCH 1/3] perf/arm-cmn: Remove spurious event aliases Robin Murphy
2023-07-07 16:38   ` Robin Murphy
2023-07-07 16:38 ` [PATCH 2/3] perf/arm-cmn: Refactor HN-F event selector macros Robin Murphy
2023-07-07 16:38   ` Robin Murphy
2023-07-07 16:38 ` [PATCH 3/3] perf/arm-cmn: Add CMN-700 r3 support Robin Murphy
2023-07-07 16:38   ` Robin Murphy
2023-07-28 15:40 ` [PATCH 0/3] perf: Arm CMN updates Will Deacon
2023-07-28 15:40   ` Will Deacon

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=cover.1688746690.git.robin.murphy@arm.com \
    --to=robin.murphy@arm.com \
    --cc=blakgeof@amazon.com \
    --cc=ilkka@os.amperecomputing.com \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mark.rutland@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.