From: Andre Przywara <andre.przywara@arm.com>
To: Sasha Levin <sashal@kernel.org>,
stable@vger.kernel.org, stable-commits@vger.kernel.org
Cc: James Morse <james.morse@arm.com>,
Ben Horgan <ben.horgan@arm.com>,
Reinette Chatre <reinette.chatre@intel.com>,
Fenghua Yu <fenghuay@nvidia.com>
Subject: Re: Patch "arm_mpam: let low level MSC accessors return an error" has been added to the 7.3-stable tree
Date: Wed, 18 Nov 2026 17:48:42 +0100 [thread overview]
Message-ID: <cd17d0fc-2859-4969-9677-692aaa2db0b7@arm.com> (raw)
In-Reply-To: <20261118124002.3727477-3-sashal@kernel.org>
Hi Sasha,
On 11/18/26 13:39, Sasha Levin wrote:
> On Wed, Nov 18, 2026 at 11:03:40AM +0100, Andre Przywara wrote:
>> I will send the stable backport patch ASAP.
>
> Dropped 84e8795c271a ("arm_mpam: let low level MSC accessors return an error"),
> a3a94c13c442 ("arm_mpam: propagate MSC access errors for state saving
> function") and 197a7a41e6e0 ("arm_mpam: On saving mbwu state read the monitors
> before clearing CFG_MBWU_CTL") from the 7.3 queue. I'll pick up your adapted
> 7.3 backport of 197a7a41e6e0 once it's posted.
Thanks! It turns out that this backport patch here logically depends on
another fix (197a7a41e6e0, you mention above). So I need a bit more time
to figure out what's exactly going on here, will try to send something
tomorrow.
Cheers,
Andre
> Also dropped 643b64025650 ("arm_mpam: Release the mon_sel lock on
> mpam_save_mbwu_state() errors"), which needs the mon_sel_lock guard class that
> 7.3 does not have.
>
next prev parent reply other threads:[~2026-11-18 16:48 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20261117143200.1638480-1-sashal@kernel.org>
2026-11-17 16:47 ` Patch "arm_mpam: let low level MSC accessors return an error" has been added to the 7.3-stable tree Andre Przywara
2026-11-18 0:20 ` Sasha Levin
2026-11-18 0:23 ` Sasha Levin
2026-11-18 10:03 ` Andre Przywara
2026-11-18 12:39 ` Sasha Levin
2026-11-18 16:48 ` Andre Przywara [this message]
2026-11-19 15:03 ` Andre Przywara
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=cd17d0fc-2859-4969-9677-692aaa2db0b7@arm.com \
--to=andre.przywara@arm.com \
--cc=ben.horgan@arm.com \
--cc=fenghuay@nvidia.com \
--cc=james.morse@arm.com \
--cc=reinette.chatre@intel.com \
--cc=sashal@kernel.org \
--cc=stable-commits@vger.kernel.org \
--cc=stable@vger.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.