From: Andre Przywara <andre.przywara@arm.com>
To: Srivathsa L Rao <srivathsa.rao@oss.qualcomm.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>,
Ben Horgan <ben.horgan@arm.com>,
Reinette Chatre <reinette.chatre@intel.com>,
Fenghua Yu <fenghuay@nvidia.com>
Cc: Jonathan Cameron <jic23@kernel.org>,
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>,
Ritwick Sharma <ritwick.sharma@arm.com>,
linux-acpi@vger.kernel.org, linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH v7 07/11] arm_mpam: propagate MSC access errors for mpam_reprogram_ris_partid()
Date: Tue, 4 Aug 2026 11:54:33 +0200 [thread overview]
Message-ID: <2aa75a48-d514-42a2-afda-d7b3357c585a@arm.com> (raw)
In-Reply-To: <836c6c2b-6ab0-4dba-9964-aa65ddcb7381@oss.qualcomm.com>
Hi,
On 8/4/26 07:57, Srivathsa L Rao wrote:
> Hi Andre,
>
> mpam_reprogram_ris_partid() writes hardware registers sequentially.
> If a write fails midway (possible on PCC MSCs via SCMI), the earlier
> writes are already committed and the hardware is left in a partially
> configured state.
> Currently this is safe only because mpam_fb_disable_mpam() tears
> everything down on any firmware error. If that behavior is ever
> relaxed (e.g. for transient BUSY handling), a partial state could
> persist and produce weird behavior?
>
> I wanted to point this as a design note.
Yes, this might be a potential problem, but as you said at the moment we
tear down MPAM anyway.
I don't know if we can ever really handle MPAM-Fb errors in a meaningful
way, but indeed a retry-if-busy seems a worthwhile addition - at a later
time ;-)
Thanks for all the reviews and comments!
Cheers,
Andre
> On 7/31/2026 10:33 PM, Andre Przywara wrote:
>> Allow the mpam_reprogram_ris_partid() function check for and return
>> errors, and propagate MSC read and write errors from the lower level up.
>> This also covers the callers of this function: mpam_reset_ris() and
>> apply_config().
>>
>> Signed-off-by: Andre Przywara <andre.przywara@arm.com>
>> ---
>> drivers/resctrl/mpam_devices.c | 136 ++++++++++++++++++++++-----------
>> 1 file changed, 93 insertions(+), 43 deletions(-)
>>
>> diff --git a/drivers/resctrl/mpam_devices.c b/drivers/resctrl/
>> mpam_devices.c
>> index 38450c55e45e..32088ad1d67e 100644
>> --- a/drivers/resctrl/mpam_devices.c
>> +++ b/drivers/resctrl/mpam_devices.c
>> @@ -1601,7 +1601,7 @@ void mpam_msmon_reset_mbwu(struct mpam_component
>> *comp, struct mon_cfg *ctx)
>> }
>> }
>> ...
>
>> +static int mpam_reprogram_ris_partid(struct mpam_msc_ris *ris, u16
>> partid,
>> + struct mpam_config *cfg)
>> {
>> u32 pri_val = 0;
>> ..
>> - mutex_unlock(&msc->part_sel_lock);
>> + return 0;
>> }
> --
>
> Best Regards,
> Srivathsa
next prev parent reply other threads:[~2026-08-04 9:54 UTC|newest]
Thread overview: 42+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-07-31 17:03 [PATCH v7 00/11] arm_mpam: Add MPAM-Fb firmware support Andre Przywara
2026-07-31 17:03 ` [PATCH v7 01/11] arm_mpam: let low level MSC accessors return an error Andre Przywara
2026-08-04 3:38 ` Gavin Shan
2026-07-31 17:03 ` [PATCH v7 02/11] arm_mpam: propagate MSC access errors for hw_probe functions Andre Przywara
2026-08-04 3:42 ` Gavin Shan
2026-07-31 17:03 ` [PATCH v7 03/11] arm_mpam: propagate MSC access errors for MBWU counters Andre Przywara
2026-08-04 3:43 ` Gavin Shan
2026-07-31 17:03 ` [PATCH v7 04/11] arm_mpam: propagate MSC access errors for msmon helpers Andre Przywara
2026-08-04 3:48 ` Gavin Shan
2026-07-31 17:03 ` [PATCH v7 05/11] arm_mpam: propagate MSC access errors for __ris_msmon_read() Andre Przywara
2026-08-03 17:23 ` Ben Horgan
2026-08-03 22:13 ` Jonathan Cameron
2026-08-04 3:51 ` Gavin Shan
2026-07-31 17:03 ` [PATCH v7 06/11] arm_mpam: propagate MSC access errors for state saving function Andre Przywara
2026-08-03 22:17 ` Jonathan Cameron
2026-08-04 3:53 ` Gavin Shan
2026-07-31 17:03 ` [PATCH v7 07/11] arm_mpam: propagate MSC access errors for mpam_reprogram_ris_partid() Andre Przywara
2026-08-03 17:22 ` Ben Horgan
2026-08-03 22:28 ` Jonathan Cameron
2026-08-04 9:15 ` Andre Przywara
2026-08-04 3:56 ` Gavin Shan
2026-08-04 5:57 ` Srivathsa L Rao
2026-08-04 9:54 ` Andre Przywara [this message]
2026-07-31 17:03 ` [PATCH v7 08/11] arm_mpam: prepare mon_sel locking for MPAM-Fb Andre Przywara
2026-08-03 17:24 ` Ben Horgan
2026-08-04 3:58 ` Gavin Shan
2026-07-31 17:03 ` [PATCH v7 09/11] arm_mpam: add MPAM-Fb MSC firmware access support Andre Przywara
2026-08-04 6:09 ` Gavin Shan
2026-08-04 6:36 ` Gavin Shan
2026-07-31 17:03 ` [PATCH v7 10/11] arm_mpam: change MPAM-Fb error IRQ to use a threaded IRQ handler Andre Przywara
2026-08-03 17:30 ` Ben Horgan
2026-08-03 22:46 ` Jonathan Cameron
2026-08-04 8:09 ` Andre Przywara
2026-07-31 17:03 ` [PATCH v7 11/11] arm_mpam: detect and enable MPAM-Fb PCC support Andre Przywara
2026-08-03 10:49 ` Srivathsa L Rao
2026-08-03 13:37 ` Andre Przywara
2026-08-03 14:53 ` Andre Przywara
2026-08-03 17:04 ` [PATCH] FIX: avoid using mailbox client dev pointer for error prints Andre Przywara
2026-08-03 17:35 ` Ben Horgan
2026-08-04 3:29 ` [PATCH v7 00/11] arm_mpam: Add MPAM-Fb firmware support Gavin Shan
2026-08-04 8:50 ` Andre Przywara
2026-08-04 8:56 ` Gavin Shan
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=2aa75a48-d514-42a2-afda-d7b3357c585a@arm.com \
--to=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=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=ritwick.sharma@arm.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