From: Jonathan Cameron <jonathan.cameron@oss.qualcomm.com>
To: Andre Przywara <andre.przywara@arm.com>
Cc: 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>,
Ben Horgan <ben.horgan@arm.com>,
Reinette Chatre <reinette.chatre@intel.com>,
Fenghua Yu <fenghuay@nvidia.com>,
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>,
linux-acpi@vger.kernel.org, linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH v3 07/16] arm_mpam: __ris_msmon_read(): get rid of nrdy special handling
Date: Fri, 10 Jul 2026 11:56:56 -0700 [thread overview]
Message-ID: <20260710115656.00001345@oss.qualcomm.com> (raw)
In-Reply-To: <20260710144520.917375-8-andre.przywara@arm.com>
On Fri, 10 Jul 2026 16:45:11 +0200
Andre Przywara <andre.przywara@arm.com> wrote:
> Although so far MSC accesses couldn't fail, there is one special
> condition that would create an error: when the MBWU counter wouldn't be
> able to read a stable value, we were setting bit 63 to mark this value
> as unstable, and return this as an error later.
> Now since the functions can return a proper error value, we can get rid of
> this kludge and use the return value directly.
>
> Remove the "nrdy" error flag variable, and assign -EBUSY to "ret" to handle
> this case.
>
> Signed-off-by: Andre Przywara <andre.przywara@arm.com>
Hi Andre
I'm still fussing about code flow and style :(
Obviously none of this is that important, but it does help make
the code more maintainable in the long run.
Jonathan
> ---
> drivers/resctrl/mpam_devices.c | 38 +++++++++++++++-------------------
> 1 file changed, 17 insertions(+), 21 deletions(-)
>
> diff --git a/drivers/resctrl/mpam_devices.c b/drivers/resctrl/mpam_devices.c
> index 84a8715464be..530ac0fe97b5 100644
> --- a/drivers/resctrl/mpam_devices.c
> +++ b/drivers/resctrl/mpam_devices.c
> @@ -1306,7 +1306,6 @@ static void __ris_msmon_read(void *arg)
> u64 now;
> int ret;
> u32 now32;
> - bool nrdy = false;
> bool config_mismatch;
> bool overflow = false;
> struct mon_read *m = arg;
> @@ -1371,14 +1370,18 @@ static void __ris_msmon_read(void *arg)
> switch (m->type) {
> case mpam_feat_msmon_csu:
> ret = mpam_read_monsel_reg(msc, CSU, &now32);
> + if (!ret) {
> + if ((now32 & MSMON___NRDY))
> + ret = -EBUSY;
> +
> + if (mpam_has_quirk(IGNORE_CSU_NRDY, msc) &&
> + m->waited_timeout)
> + ret = 0;
Whilst it is from existing code, this pattern of set and error then clear it
is less than ideal. Maybe
if ((now32 & MSMON___NRDY) &&
!(mpam_has_quirk(IGNORE_CS_NRDY, MSC && m->waited_timeout))
ret = -EBUSY;
is clearer as that odd intermediate state of ret never happens.
> + }
> if (ret)
> goto out_unlock;
> - nrdy = now32 & MSMON___NRDY;
> - now = FIELD_GET(MSMON___VALUE, now32);
> -
> - if (mpam_has_quirk(IGNORE_CSU_NRDY, msc) && m->waited_timeout)
> - nrdy = false;
>
> + now = FIELD_GET(MSMON___VALUE, now32);
> break;
> case mpam_feat_msmon_mbwu_31counter:
> case mpam_feat_msmon_mbwu_44counter:
> @@ -1394,9 +1397,11 @@ static void __ris_msmon_read(void *arg)
> now = FIELD_GET(MSMON___L_VALUE, now);
> } else {
> ret = mpam_read_monsel_reg(msc, MBWU, &now32);
> + if (!ret && (now32 & MSMON___NRDY))
> + ret = -EBUSY;
> if (ret)
> goto out_unlock;
> - nrdy = now32 & MSMON___NRDY;
> +
> now = FIELD_GET(MSMON___VALUE, now32);
> }
>
> @@ -1404,9 +1409,6 @@ static void __ris_msmon_read(void *arg)
> m->type != mpam_feat_msmon_mbwu_63counter)
> now *= 64;
>
> - if (nrdy)
> - break;
> -
> mbwu_state = &ris->mbwu_state[ctx->mon];
>
> if (overflow)
> @@ -1419,22 +1421,16 @@ static void __ris_msmon_read(void *arg)
> now += mbwu_state->correction;
> break;
> default:
> - m->err = -EINVAL;
> + ret = -EINVAL;
> }
> - mpam_mon_sel_unlock(msc);
> -
> - if (nrdy)
> - m->err = -EBUSY;
> -
> - if (!m->err)
> - *m->val += now;
> -
> - return;
>
> out_unlock:
> mpam_mon_sel_unlock(msc);
>
> - m->err = ret;
> + if (ret)
> + m->err = ret;
> + else
> + *m->val += now;
If you do the earlier suggestion of ACQUIRE() this all get simpler, but if you do keep
this, then burn a line or two of code to make it obvious what is error and what isn't.
if (ret) {
m->err = ret;
return;
}
*m->val += now;
> }
next prev parent reply other threads:[~2026-07-10 18:57 UTC|newest]
Thread overview: 34+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-07-10 14:45 [PATCH v3 00/16] arm_mpam: Add MPAM-Fb firmware support Andre Przywara
2026-07-10 14:45 ` [PATCH v3 01/16] arm_mpam: let low level MSC read accessors return an error Andre Przywara
2026-07-10 18:11 ` Jonathan Cameron
2026-07-10 21:40 ` Andre Przywara
2026-07-10 14:45 ` [PATCH v3 02/16] arm_mpam: propagate MSC read errors for wrapper functions Andre Przywara
2026-07-10 18:21 ` Jonathan Cameron
2026-07-10 14:45 ` [PATCH v3 03/16] arm_mpam: propagate MSC read errors for hw_probe functions Andre Przywara
2026-07-10 18:31 ` Jonathan Cameron
2026-07-10 14:45 ` [PATCH v3 04/16] arm_mpam: propagate MSC read errors for mpam_msc_read_mbwu_l() Andre Przywara
2026-07-10 18:40 ` Jonathan Cameron
2026-07-10 14:45 ` [PATCH v3 05/16] arm_mpam: propagate MSC read errors for msmon helpers Andre Przywara
2026-07-10 18:44 ` Jonathan Cameron
2026-07-10 14:45 ` [PATCH v3 06/16] arm_mpam: propagate MSC read errors for __ris_msmon_read() Andre Przywara
2026-07-10 18:48 ` Jonathan Cameron
2026-07-10 14:45 ` [PATCH v3 07/16] arm_mpam: __ris_msmon_read(): get rid of nrdy special handling Andre Przywara
2026-07-10 18:56 ` Jonathan Cameron [this message]
2026-07-10 14:45 ` [PATCH v3 08/16] arm_mpam: propagate MSC read errors for state saving functions Andre Przywara
2026-07-10 19:00 ` Jonathan Cameron
2026-07-10 14:45 ` [PATCH v3 09/16] arm_mpam: let low level MSC write accessors return an error Andre Przywara
2026-07-10 19:02 ` Jonathan Cameron
2026-07-10 14:45 ` [PATCH v3 10/16] arm_mpam: propagate MSC write errors for ESR and part_sel wrappers Andre Przywara
2026-07-10 14:45 ` [PATCH v3 11/16] arm_mpam: propagate MSC write errors for hardware probe functions Andre Przywara
2026-07-10 19:04 ` Jonathan Cameron
2026-07-10 14:45 ` [PATCH v3 12/16] arm_mpam: propagate MSC write errors for remaining MSC write users Andre Przywara
2026-07-10 19:10 ` Jonathan Cameron
2026-07-10 14:45 ` [PATCH v3 13/16] arm_mpam: prepare mon_sel locking for MPAM-Fb Andre Przywara
2026-07-10 19:14 ` Jonathan Cameron
2026-07-10 14:45 ` [PATCH v3 14/16] arm_mpam: add MPAM-Fb MSC firmware access support Andre Przywara
2026-07-10 19:58 ` Jonathan Cameron
2026-07-14 12:27 ` Niyas Sait
2026-07-10 14:45 ` [PATCH v3 15/16] arm_mpam: prevent MPAM-Fb accesses inside IRQ handler Andre Przywara
2026-07-10 14:45 ` [PATCH v3 16/16] arm_mpam: detect and enable MPAM-Fb PCC support Andre Przywara
2026-07-10 20:10 ` Jonathan Cameron
2026-07-14 12:32 ` Niyas Sait
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=20260710115656.00001345@oss.qualcomm.com \
--to=jonathan.cameron@oss.qualcomm.com \
--cc=andre.przywara@arm.com \
--cc=ben.horgan@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=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 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.