From: Will Deacon <will@kernel.org>
To: Robin Murphy <robin.murphy@arm.com>,
Ilkka Koskinen <ilkka@os.amperecomputing.com>
Cc: catalin.marinas@arm.com, kernel-team@android.com,
Will Deacon <will@kernel.org>,
Mark Rutland <mark.rutland@arm.com>,
linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org,
Jing Zhang <renyu.zj@linux.alibaba.com>
Subject: Re: [PATCH v4 0/2] Mesh PMU: Add tertiary match group support
Date: Mon, 1 Jul 2024 16:35:42 +0100 [thread overview]
Message-ID: <171984210889.916169.4034955157375868268.b4-ty@kernel.org> (raw)
In-Reply-To: <20240618005056.3092866-1-ilkka@os.amperecomputing.com>
On Mon, 17 Jun 2024 17:50:54 -0700, Ilkka Koskinen wrote:
> v4: * No changes, only rebased on top of v6.10-rc4
>
> 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
> * https://lore.kernel.org/all/20240329013215.169345-1-ilkka@os.amperecomputing.com/
>
> [...]
Applied to will (for-next/perf), thanks!
[1/2] perf/arm-cmn: Decouple wp_config registers from filter group number
https://git.kernel.org/will/c/4a112585ebe8
[2/2] perf/arm-cmn: Enable support for tertiary match group
https://git.kernel.org/will/c/f9a7a91f6406
Cheers,
--
Will
https://fixes.arm64.dev
https://next.arm64.dev
https://will.arm64.dev
prev parent reply other threads:[~2024-07-01 15:35 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-06-18 0:50 Ilkka Koskinen
2024-06-18 0:50 ` [PATCH v4 1/2] perf/arm-cmn: Decouple wp_config registers from filter group number Ilkka Koskinen
2024-06-18 0:50 ` [PATCH v4 2/2] perf/arm-cmn: Enable support for tertiary match group Ilkka Koskinen
2024-07-01 15:35 ` Will Deacon [this message]
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=171984210889.916169.4034955157375868268.b4-ty@kernel.org \
--to=will@kernel.org \
--cc=catalin.marinas@arm.com \
--cc=ilkka@os.amperecomputing.com \
--cc=kernel-team@android.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 \
/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
all inboxes | Powered by JetHome®