From: sashiko-bot@kernel.org
To: "Vladimir Kondratiev" <vladimir.kondratiev@mobileye.com>
Cc: linux-perf-users@vger.kernel.org
Subject: Re: [PATCH 2/5] MIPS: CM: export the symbols needed to access the GCRs from a module
Date: Sun, 08 Nov 2026 13:28:06 +0000 [thread overview]
Message-ID: <sashiko-outbox-203779@kernel.org> (raw)
In-Reply-To: <20261108-i6500-cm3-pmu-v1-2-bd119584891a@mobileye.com>
> Allow modules to use the GCR and CPC accessors from asm/mips-cm.h and
> asm/mips-cpc.h:
>
> - mips_gcr_base and mips_cpc_base are the mapped register blocks;
> - the CPS_ACCESSOR macros consult mips_cm_is64 on every 64-bit register
> access;
> - mips_cm_lock_other() / mips_cm_unlock_other() are the only way to
> reach the registers of another cluster through the redirect block.
>
> This is a prerequisite for building the CM3 PMU driver as a module.
>
> Signed-off-by: Vladimir Kondratiev <vladimir.kondratiev@mobileye.com>
Sashiko has reviewed this patch and found no issues.
--
Sashiko AI review · https://sashiko.dev/#/patchset/20261108-i6500-cm3-pmu-v1-0-bd119584891a@mobileye.com?part=2
next prev parent reply other threads:[~2026-11-08 13:28 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-11-08 13:20 [PATCH 0/5] perf: add PMU driver for the MIPS Coherence Manager 3 performance counters Vladimir Kondratiev
2026-11-08 13:20 ` [PATCH 1/5] MIPS: CM: add CM3 performance counter GCR definitions Vladimir Kondratiev
2026-11-08 13:24 ` sashiko-bot
2026-11-08 13:20 ` [PATCH 2/5] MIPS: CM: export the symbols needed to access the GCRs from a module Vladimir Kondratiev
2026-11-08 13:28 ` sashiko-bot [this message]
2026-11-08 13:20 ` [PATCH 3/5] dt-bindings: mips: mti,mips-cm: add performance counter interrupt Vladimir Kondratiev
2026-11-08 13:22 ` sashiko-bot
2026-11-08 13:20 ` [PATCH 4/5] perf: add MIPS Coherence Manager 3 (CM3) PMU driver Vladimir Kondratiev
2026-11-08 13:45 ` sashiko-bot
2026-11-08 13:20 ` [PATCH 5/5] MIPS: eyeq6_defconfig: enable the CM3 PMU Vladimir Kondratiev
2026-11-08 13:24 ` sashiko-bot
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=sashiko-outbox-203779@kernel.org \
--to=sashiko-bot@kernel.org \
--cc=linux-perf-users@vger.kernel.org \
--cc=sashiko-reviews@lists.linux.dev \
--cc=vladimir.kondratiev@mobileye.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 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.