From: Ben Horgan <ben.horgan@arm.com>
To: Andre Przywara <andre.przywara@arm.com>,
Lorenzo Pieralisi <lpieralisi@kernel.org>,
Hanjun Guo <guohanjun@huawei.com>,
Sudeep Holla <sudeep.holla@kernel.org>,
Catalin Marinas <catalin.marinas@arm.com>,
Will Deacon <will@kernel.org>,
"Rafael J . Wysocki" <rafael@kernel.org>,
Len Brown <lenb@kernel.org>, James Morse <james.morse@arm.com>,
Reinette Chatre <reinette.chatre@intel.com>,
Fenghua Yu <fenghuay@nvidia.com>
Cc: Jonathan Cameron <jic23@kernel.org>,
Srivathsa L Rao <srivathsa.rao@oss.qualcomm.com>,
Ganapatrao Kulkarni <ganapatrao.kulkarni@oss.qualcomm.com>,
Trilok Soni <tsoni@quicinc.com>,
Srinivas Ramana <sramana@qti.qualcomm.com>,
Niyas Sait <niyas.sait@arm.com>, Lee Trager <lee@trager.us>,
linux-acpi@vger.kernel.org, linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH v5 05/10] arm_mpam: propagate MSC access errors for __ris_msmon_read()
Date: Thu, 30 Jul 2026 10:52:25 +0100 [thread overview]
Message-ID: <fad866fe-45d1-40a5-8870-67fa702890ec@arm.com> (raw)
In-Reply-To: <20260729134124.2506269-6-andre.przywara@arm.com>
Hi Andre,
On 7/29/26 14:41, Andre Przywara wrote:
> Allow the function for RIS accesses to return an error, and propagate
> read and write errors from the lower level up.
> This function is a bit special, since it can be called via an SMP
> helper, so the prototype must stay as void. So propagate any errors
> using the "err" field in the struct passed in as the sole argument to
> that function.
>
> Signed-off-by: Andre Przywara <andre.przywara@arm.com>
> Reviewed-by: Jonathan Cameron <jonathan.cameron@oss.qualcomm.com>
> ---
> drivers/resctrl/mpam_devices.c | 36 +++++++++++++++++++++++++---------
> 1 file changed, 27 insertions(+), 9 deletions(-)
>
> diff --git a/drivers/resctrl/mpam_devices.c b/drivers/resctrl/mpam_devices.c
> index 9d9f0c635527..44eafef1e7ab 100644
> --- a/drivers/resctrl/mpam_devices.c
> +++ b/drivers/resctrl/mpam_devices.c
> @@ -1333,6 +1333,10 @@ static u64 mpam_msmon_overflow_val(enum mpam_device_features type,
> return overflow_val;
> }
>
> +/*
> + * This function might be called via smp_call_function_any(), so propagate
> + * errors inside the arg struct.
> + */
> static void __ris_msmon_read(void *arg)
> {
> u64 now;
> @@ -1356,7 +1360,9 @@ static void __ris_msmon_read(void *arg)
>
> mon_sel = FIELD_PREP(MSMON_CFG_MON_SEL_MON_SEL, ctx->mon) |
> FIELD_PREP(MSMON_CFG_MON_SEL_RIS, ris->ris_idx);
> - mpam_write_monsel_reg(msc, CFG_MON_SEL, mon_sel);
> + m->err = mpam_write_monsel_reg(msc, CFG_MON_SEL, mon_sel);
> + if (m->err)
> + return;
>
> switch (m->type) {
> case mpam_feat_msmon_mbwu_31counter:
> @@ -1376,7 +1382,9 @@ static void __ris_msmon_read(void *arg)
> * Read the existing configuration to avoid re-writing the same values.
> * This saves waiting for 'nrdy' on subsequent reads.
> */
> - read_msmon_ctl_flt_vals(m, &cur_ctl, &cur_flt);
> + m->err = read_msmon_ctl_flt_vals(m, &cur_ctl, &cur_flt);
> + if (m->err)
> + return;
>
> if (mpam_feat_msmon_mbwu_31counter == m->type)
> overflow = cur_ctl & MSMON_CFG_x_CTL_OFLOW_STATUS;
> @@ -1390,18 +1398,24 @@ static void __ris_msmon_read(void *arg)
> cur_ctl != (ctl_val | MSMON_CFG_x_CTL_EN);
>
> if (config_mismatch || reset_on_next_read) {
> - write_msmon_ctl_flt_vals(m, ctl_val, flt_val);
> + m->err = write_msmon_ctl_flt_vals(m, ctl_val, flt_val);
> + if (m->err)
> + return;
> overflow = false;
> } else if (overflow) {
> - mpam_write_monsel_reg(msc, CFG_MBWU_CTL,
> - cur_ctl &
> - ~(MSMON_CFG_x_CTL_OFLOW_STATUS |
> - MSMON_CFG_MBWU_CTL_OFLOW_STATUS_L));
> + m->err = mpam_write_monsel_reg(msc, CFG_MBWU_CTL,
> + cur_ctl &
> + ~(MSMON_CFG_x_CTL_OFLOW_STATUS |
> + MSMON_CFG_MBWU_CTL_OFLOW_STATUS_L));
> + if (m->err)
> + return;
> }
>
> switch (m->type) {
> case mpam_feat_msmon_csu:
> - mpam_read_monsel_reg(msc, CSU, &now32);
> + m->err = mpam_read_monsel_reg(msc, CSU, &now32);
> + if (m->err)
> + return;
> nrdy = now32 & MSMON___NRDY;
> now = FIELD_GET(MSMON___VALUE, now32);
>
> @@ -1423,7 +1437,9 @@ static void __ris_msmon_read(void *arg)
> else
> now = FIELD_GET(MSMON___L_VALUE, now);
> } else {
> - mpam_read_monsel_reg(msc, MBWU, &now32);
> + m->err = mpam_read_monsel_reg(msc, MBWU, &now32);
> + if (m->err)
> + return;
> nrdy = now32 & MSMON___NRDY;
> now = FIELD_GET(MSMON___VALUE, now32);
> }
> @@ -1792,6 +1808,8 @@ static int mpam_restore_mbwu_state(void *_ris)
> mwbu_arg.val = &val;
>
> __ris_msmon_read(&mwbu_arg);
> + if (mwbu_arg.err)
> + return mwbu_arg.err;
As sashiko points out [1], this is a change of behaviour as mbwu_arg.err could already be non-zero
previous to this patch. In particular, -EBUSY when NRDY is set. When this is the case we should
continue restoring the other counters rather than changing to bailing out early.
As -EBUSY is only used in the NRDY case you could change the condition to be:
if (mbwu_arg.err && mbwu_arg.err != -EBUSY)
return mwbu_arg.err;
[1] https://sashiko.dev/#/patchset/20260729134124.2506269-1-andre.przywara%40arm.com
Thanks,
Ben
> }
> }
>
next prev parent reply other threads:[~2026-07-30 9:54 UTC|newest]
Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-07-29 13:41 [PATCH v5 00/10] arm_mpam: Add MPAM-Fb firmware support Andre Przywara
2026-07-29 13:41 ` [PATCH v5 01/10] arm_mpam: let low level MSC accessors return an error Andre Przywara
2026-07-30 11:20 ` Ben Horgan
2026-07-29 13:41 ` [PATCH v5 02/10] arm_mpam: propagate MSC access errors for hw_probe functions Andre Przywara
2026-07-30 11:21 ` Ben Horgan
2026-07-29 13:41 ` [PATCH v5 03/10] arm_mpam: propagate MSC access errors for MBWU counters Andre Przywara
2026-07-30 1:33 ` Lee Trager
2026-07-30 8:20 ` Ben Horgan
2026-07-30 11:23 ` Ben Horgan
2026-07-29 13:41 ` [PATCH v5 04/10] arm_mpam: propagate MSC access errors for msmon helpers Andre Przywara
2026-07-30 11:25 ` Ben Horgan
2026-07-29 13:41 ` [PATCH v5 05/10] arm_mpam: propagate MSC access errors for __ris_msmon_read() Andre Przywara
2026-07-30 9:52 ` Ben Horgan [this message]
2026-07-29 13:41 ` [PATCH v5 06/10] arm_mpam: propagate MSC access errors for state saving function Andre Przywara
2026-07-30 11:28 ` Ben Horgan
2026-07-29 13:41 ` [PATCH v5 07/10] arm_mpam: prepare mon_sel locking for MPAM-Fb Andre Przywara
2026-07-29 13:41 ` [PATCH v5 08/10] arm_mpam: add MPAM-Fb MSC firmware access support Andre Przywara
2026-07-29 14:51 ` Ben Horgan
2026-07-29 15:17 ` Andre Przywara
2026-07-29 16:10 ` Ben Horgan
2026-07-29 16:13 ` Srivathsa L Rao
2026-07-30 9:55 ` Andre Przywara
2026-07-30 10:59 ` Ben Horgan
2026-07-30 12:28 ` Andre Przywara
2026-07-29 13:41 ` [PATCH v5 09/10] arm_mpam: change error IRQ to use a threaded IRQ handler Andre Przywara
2026-07-29 15:23 ` Ben Horgan
2026-07-30 12:07 ` Andre Przywara
2026-07-29 13:41 ` [PATCH v5 10/10] arm_mpam: detect and enable MPAM-Fb PCC support Andre Przywara
2026-07-30 1:34 ` Lee Trager
2026-07-30 9:58 ` Srivathsa L Rao
2026-07-30 10:05 ` Andre Przywara
2026-07-30 11:06 ` [PATCH v5 00/10] arm_mpam: Add MPAM-Fb firmware support Ritwick Sharma
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=fad866fe-45d1-40a5-8870-67fa702890ec@arm.com \
--to=ben.horgan@arm.com \
--cc=andre.przywara@arm.com \
--cc=catalin.marinas@arm.com \
--cc=fenghuay@nvidia.com \
--cc=ganapatrao.kulkarni@oss.qualcomm.com \
--cc=guohanjun@huawei.com \
--cc=james.morse@arm.com \
--cc=jic23@kernel.org \
--cc=lee@trager.us \
--cc=lenb@kernel.org \
--cc=linux-acpi@vger.kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=lpieralisi@kernel.org \
--cc=niyas.sait@arm.com \
--cc=rafael@kernel.org \
--cc=reinette.chatre@intel.com \
--cc=sramana@qti.qualcomm.com \
--cc=srivathsa.rao@oss.qualcomm.com \
--cc=sudeep.holla@kernel.org \
--cc=tsoni@quicinc.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