From: Xi Ruoyao <xry111@xry111.site>
To: Ben Horgan <ben.horgan@arm.com>, Fuad Tabba <fuad.tabba@linux.dev>
Cc: James Morse <james.morse@arm.com>,
Catalin Marinas <catalin.marinas@arm.com>,
Will Deacon <will@kernel.org>, Marc Zyngier <maz@kernel.org>,
"moderated list:ARM64 PORT (AARCH64 ARCHITECTURE)"
<linux-arm-kernel@lists.infradead.org>,
open list <linux-kernel@vger.kernel.org>
Subject: Re: arm64: MPAM2_EL2 and MPAMHCR_EL2 are left UNKNOWN under arm64.nompam
Date: Wed, 02 Sep 2026 23:26:55 +0800 [thread overview]
Message-ID: <2368f72ea9a447057456eb37450e1c25f4bdddff.camel@xry111.site> (raw)
In-Reply-To: <0b2c58d2-cc82-4c68-aaa2-83449d0b48c1@arm.com>
On Thu, 2026-08-27 at 09:41 +0100, Ben Horgan wrote:
> > not, could the caveat go the other way round: arm64.nompam is for
> > systems where firmware ignores MPAM, and should only be set on a
> > machine that does not boot without it?
>
> Yes, seems fine.
Sorry for the late reply. This is indeed the original purpose for
arm64.nompam, a dirty hack when we have no other ways to make the system
boot. If you think it causes an inconsistent state I'd not complain
against adding a loud warning or something.
--
Xi Ruoyao <xry111@xry111.site>
next prev parent reply other threads:[~2026-09-02 15:27 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-08-25 19:18 arm64: MPAM2_EL2 and MPAMHCR_EL2 are left UNKNOWN under arm64.nompam Fuad Tabba
2026-08-26 14:48 ` Ben Horgan
2026-08-26 22:08 ` Fuad Tabba
2026-08-27 8:41 ` Ben Horgan
2026-09-02 15:26 ` Xi Ruoyao [this message]
2026-09-02 15:29 ` Bradley Morgan
[not found] ` <CA+EHjTxrJB_3ks_rqGAFyihyFwKJEEJYk2ZTMLLXgoMWM+GO_w@mail.gmail.com>
2026-09-02 15:33 ` Bradley Morgan
2026-09-02 15:42 ` Fuad Tabba
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=2368f72ea9a447057456eb37450e1c25f4bdddff.camel@xry111.site \
--to=xry111@xry111.site \
--cc=ben.horgan@arm.com \
--cc=catalin.marinas@arm.com \
--cc=fuad.tabba@linux.dev \
--cc=james.morse@arm.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=maz@kernel.org \
--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