From: Bradley Morgan <brads@mainlining.org>
To: Fuad Tabba <fuad.tabba@linux.dev>
Cc: xry111@xry111.site, ben.horgan@arm.com, catalin.marinas@arm.com,
james.morse@arm.com, linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org, maz@kernel.org, will@kernel.org
Subject: Re: arm64: MPAM2_EL2 and MPAMHCR_EL2 are left UNKNOWN under arm64.nompam
Date: Wed, 02 Sep 2026 16:33:43 +0100 [thread overview]
Message-ID: <22876BF5-AAA3-4ABE-9BD0-E4D3D97B123D@mainlining.org> (raw)
In-Reply-To: <CA+EHjTxrJB_3ks_rqGAFyihyFwKJEEJYk2ZTMLLXgoMWM+GO_w@mail.gmail.com>
On 2 September 2026 16:31:02 BST, Fuad Tabba <fuad.tabba@linux.dev> wrote:
>On Wed, 2 Sept 2026 at 16:29, Bradley Morgan <brads@mainlining.org> wrote:
>>
>> On 2 September 2026 16:26:55 BST, Xi Ruoyao <xry111@xry111.site> wrote:
>> >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.
>>
>> Sorry to impede in the discussion, would you like me to submit a patch
>for
>> that?
>
>No, thanks. It's written already in the form Ben suggested. Will send it
>soon.
>
>/fuad
>
>>
>> >
>> >
>>
>> --- Thanks!
>>
>https://lore.kernel.org/all/EE579805-42F2-4C58-B752-F28779EEB717@grrlz.net/
Ok, could you cc me in it?
--- Thanks!
https://lore.kernel.org/all/EE579805-42F2-4C58-B752-F28779EEB717@grrlz.net/
next prev parent reply other threads:[~2026-09-02 15:34 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
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 [this message]
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=22876BF5-AAA3-4ABE-9BD0-E4D3D97B123D@mainlining.org \
--to=brads@mainlining.org \
--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 \
--cc=xry111@xry111.site \
/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