From: Ilkka Koskinen <ilkka@os.amperecomputing.com>
To: Robin Murphy <robin.murphy@arm.com>, Will Deacon <will@kernel.org>
Cc: Mark Rutland <mark.rutland@arm.com>,
linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org,
Jing Zhang <renyu.zj@linux.alibaba.com>,
Ilkka Koskinen <ilkka@os.amperecomputing.com>
Subject: [PATCH v3 0/2] Mesh PMU: Add tertiary match group support
Date: Thu, 28 Mar 2024 18:32:13 -0700 [thread overview]
Message-ID: <20240329013215.169345-1-ilkka@os.amperecomputing.com> (raw)
Hopefully, I got it this time and the patchset starts to look better now...
v3:
* Replaced wp_cfg in arm_cmn_hw_event with wp_idx that keeps
track, whether the event uses 0 or 1 index for the given direction
* Cleaned and simplified allocation/claiming of wp config
* arm_cmn_val_add_event() can't and won't fail anymore
* Separated wp_combine from wp[] in event validation phase
* use memset()/sizeof() when clearing an event
* Still kept wp config allocator in separate functions - at least
for now
v2:
* Wp config registers are allocated on node basis, instead
of using the same one globally
* Use bitmap in the event structure to keep track on the
wp config registers assigned to the specific event.
* The bitmap tracks only either UP (wp conf 0&1) or DOWN
(wp conf 2&3) registers.
* Dropped the second patch
("The patch set v2 is now in the internal mailing list")
as perf/sysfs doesn't really support items with the same
name even if visibility would handle them.
* Addressed a bunch of other comments by the author
* https://lore.kernel.org/all/20240307230929.6233-2-ilkka@os.amperecomputing.com/
v1:
* https://lore.kernel.org/all/20240126221215.1537377-1-ilkka@os.amperecomputing.com/
Ilkka Koskinen (2):
perf/arm-cmn: Decouple wp_config registers from filter group number
perf/arm-cmn: Enable support for tertiary match group
drivers/perf/arm-cmn.c | 116 +++++++++++++++++++++++++++++++++--------
1 file changed, 93 insertions(+), 23 deletions(-)
--
2.43.0
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
next reply other threads:[~2024-03-29 1:33 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-03-29 1:32 Ilkka Koskinen [this message]
2024-03-29 1:32 ` [PATCH v3 1/2] perf/arm-cmn: Decouple wp_config registers from filter group number Ilkka Koskinen
2024-03-29 1:32 ` [PATCH v3 2/2] perf/arm-cmn: Enable support for tertiary match group Ilkka Koskinen
2024-04-23 7:29 ` [PATCH v3 0/2] Mesh PMU: Add tertiary match group support Ilkka Koskinen
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=20240329013215.169345-1-ilkka@os.amperecomputing.com \
--to=ilkka@os.amperecomputing.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mark.rutland@arm.com \
--cc=renyu.zj@linux.alibaba.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