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>,
linux-acpi@vger.kernel.org, linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2 02/15] arm_mpam: propagate MSC read errors for wrapper functions
Date: Wed, 1 Jul 2026 20:56:53 +0100 [thread overview]
Message-ID: <029910c3-e90f-4a35-8b01-4d3ff548deea@arm.com> (raw)
In-Reply-To: <20260702162229.4008659-3-andre.przywara@arm.com>
Hi Andre,
On 7/2/26 17:22, Andre Przywara wrote:
> Allow the wrapper functions for IDR and ESR accesses to return an
> error, and propagate read errors from the lower level up.
>
> Signed-off-by: Andre Przywara <andre.przywara@arm.com>
> ---
> drivers/resctrl/mpam_devices.c | 51 +++++++++++++++++++++++-----------
> 1 file changed, 35 insertions(+), 16 deletions(-)
>
> diff --git a/drivers/resctrl/mpam_devices.c b/drivers/resctrl/mpam_devices.c
> index df14b4513382..ce8738adb6ff 100644
> --- a/drivers/resctrl/mpam_devices.c
> +++ b/drivers/resctrl/mpam_devices.c
> @@ -247,27 +247,34 @@ static bool mpam_msc_check_aidr(struct mpam_msc *msc)
> return true;
> }
>
> -static u64 mpam_msc_read_idr(struct mpam_msc *msc)
> +static int mpam_msc_read_idr(struct mpam_msc *msc, u64 *res)
> {
> u32 idr_high = 0, idr_low;
> + int ret;
>
> lockdep_assert_held(&msc->part_sel_lock);
>
> - mpam_read_partsel_reg(msc, IDR, &idr_low);
> - if (FIELD_GET(MPAMF_IDR_EXT, idr_low))
> - mpam_read_partsel_reg(msc, IDR + 4, &idr_high);
> + ret = mpam_read_partsel_reg(msc, IDR, &idr_low);
> + if (!ret && FIELD_GET(MPAMF_IDR_EXT, idr_low))
> + ret = mpam_read_partsel_reg(msc, IDR + 4, &idr_high);
>
> - return ((u64)idr_high << 32) | idr_low;
> + if (!ret)
> + *res = ((u64)idr_high << 32) | idr_low;
> +
> + return ret;
> }
Why does the pattern here, use of !ret rather than early return, differ
from the one you've used in mpam_msc_read_esr()?
Thanks,
Ben
>
> -static void mpam_msc_clear_esr(struct mpam_msc *msc)
> +static int mpam_msc_clear_esr(struct mpam_msc *msc)
> {
> u32 esr_low;
> + int ret;
>
> - __mpam_read_reg(msc, MPAMF_ESR, &esr_low);
> + ret = __mpam_read_reg(msc, MPAMF_ESR, &esr_low);
> + if (ret)
> + return ret;
>
> if (!esr_low)
> - return;
> + return 0;
>
> /*
> * Clearing the high/low bits of MPAMF_ESR can not be atomic.
> @@ -277,18 +284,30 @@ static void mpam_msc_clear_esr(struct mpam_msc *msc)
> */
> if (msc->has_extd_esr)
> __mpam_write_reg(msc, MPAMF_ESR + 4, 0);
> +
> __mpam_write_reg(msc, MPAMF_ESR, 0);
> +
> + return 0;
> }
>
> -static u64 mpam_msc_read_esr(struct mpam_msc *msc)
> +static int mpam_msc_read_esr(struct mpam_msc *msc, u64 *res)
> {
> u32 esr_high = 0, esr_low;
> + int ret;
>
> - __mpam_read_reg(msc, MPAMF_ESR, &esr_low);
> - if (msc->has_extd_esr)
> - __mpam_read_reg(msc, MPAMF_ESR + 4, &esr_high);
> + ret = __mpam_read_reg(msc, MPAMF_ESR, &esr_low);
> + if (ret)
> + return ret;
> +
> + if (msc->has_extd_esr) {
> + ret = __mpam_read_reg(msc, MPAMF_ESR + 4, &esr_high);
> + if (ret)
> + return ret;
> + }
>
> - return ((u64)esr_high << 32) | esr_low;
> + *res = ((u64)esr_high << 32) | esr_low;
> +
> + return 0;
> }
>
> static void __mpam_part_sel_raw(u32 partsel, struct mpam_msc *msc)
> @@ -993,7 +1012,7 @@ static int mpam_msc_hw_probe(struct mpam_msc *msc)
>
> /* Grab an IDR value to find out how many RIS there are */
> mutex_lock(&msc->part_sel_lock);
> - idr = mpam_msc_read_idr(msc);
> + mpam_msc_read_idr(msc, &idr);
> mpam_read_partsel_reg(msc, IIDR, &msc->iidr);
>
> mutex_unlock(&msc->part_sel_lock);
> @@ -1009,7 +1028,7 @@ static int mpam_msc_hw_probe(struct mpam_msc *msc)
> for (ris_idx = 0; ris_idx <= msc->ris_max; ris_idx++) {
> mutex_lock(&msc->part_sel_lock);
> __mpam_part_sel(ris_idx, 0, msc);
> - idr = mpam_msc_read_idr(msc);
> + mpam_msc_read_idr(msc, &idr);
> mutex_unlock(&msc->part_sel_lock);
>
> partid_max = FIELD_GET(MPAMF_IDR_PARTID_MAX, idr);
> @@ -2492,7 +2511,7 @@ static irqreturn_t __mpam_irq_handler(int irq, struct mpam_msc *msc)
> &msc->accessibility)))
> return IRQ_NONE;
>
> - reg = mpam_msc_read_esr(msc);
> + mpam_msc_read_esr(msc, ®);
>
> errcode = FIELD_GET(MPAMF_ESR_ERRCODE, reg);
> if (!errcode)
next prev parent reply other threads:[~2026-07-03 8:38 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-07-02 16:22 [PATCH v2 00/15] arm_mpam: Add MPAM-Fb firmware support Andre Przywara
2026-07-02 16:22 ` [PATCH v2 01/15] arm_mpam: let low level MSC read accessors return an error Andre Przywara
2026-07-02 16:22 ` [PATCH v2 02/15] arm_mpam: propagate MSC read errors for wrapper functions Andre Przywara
2026-07-01 19:56 ` Ben Horgan [this message]
2026-07-02 16:22 ` [PATCH v2 03/15] arm_mpam: propagate MSC read errors for hw_probe functions Andre Przywara
2026-07-01 20:00 ` Ben Horgan
2026-07-02 16:22 ` [PATCH v2 04/15] arm_mpam: propagate MSC read errors for mpam_msc_read_mbwu_l() Andre Przywara
2026-07-01 20:06 ` Ben Horgan
2026-07-02 16:22 ` [PATCH v2 05/15] arm_mpam: propagate MSC read errors for msmon helpers Andre Przywara
2026-07-02 16:22 ` [PATCH v2 06/15] arm_mpam: propagate MSC read errors for __ris_msmon_read() Andre Przywara
2026-07-01 20:14 ` Ben Horgan
2026-07-02 16:22 ` [PATCH v2 07/15] arm_mpam: propagate MSC read errors for state saving functions Andre Przywara
2026-07-01 20:19 ` Ben Horgan
2026-07-02 16:22 ` [PATCH v2 08/15] arm_mpam: let low level MSC write accessors return an error Andre Przywara
2026-07-02 16:22 ` [PATCH v2 09/15] arm_mpam: propagate MSC write errors for ESR and part_sel wrappers Andre Przywara
2026-07-02 16:22 ` [PATCH v2 10/15] arm_mpam: propagate MSC write errors for hardware probe functions Andre Przywara
2026-07-02 16:22 ` [PATCH v2 11/15] arm_mpam: propagate MSC write errors for remaining MSC write users Andre Przywara
2026-07-02 16:22 ` [PATCH v2 12/15] arm_mpam: Split the locking around the mon_sel registers Andre Przywara
2026-07-01 21:01 ` Ben Horgan
2026-07-02 16:22 ` [PATCH v2 13/15] arm_mpam: add MPAM-Fb MSC firmware access support Andre Przywara
2026-07-02 16:22 ` [PATCH v2 14/15] arm_mpam: prevent MPAM-Fb accesses inside IRQ handler Andre Przywara
2026-07-03 10:54 ` Ben Horgan
2026-07-02 16:22 ` [PATCH v2 15/15] arm_mpam: detect and enable MPAM-Fb PCC support Andre Przywara
2026-07-03 11:00 ` Ben Horgan
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=029910c3-e90f-4a35-8b01-4d3ff548deea@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=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