From: Marc Zyngier <maz@kernel.org>
To: tanze@kylinos.cn
Cc: xry111@xry111.site, james.morse@arm.com, catalin.marinas@arm.com,
linux-kernel@vger.kernel.org,
linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH v1] arm64/mpam: Replace the arm64.nompam parameter with arm64.mpam
Date: Wed, 17 Dec 2025 15:30:19 +0000 [thread overview]
Message-ID: <86wm2lm8hg.wl-maz@kernel.org> (raw)
In-Reply-To: <20251217151159.1076002-1-tanze@kylinos.cn>
On Wed, 17 Dec 2025 15:11:59 +0000,
tanze@kylinos.cn wrote:
>
> From: tanze <tanze@kylinos.cn>
>
> In practical application scenarios, some manufacturers use outdated
> firmware and do not add relevant configurations to the kernel command
> line during deployment, which will result in system boot failure.
> For manufacturers, disabling the MPAM feature by default and
> enabling it via additional boot parameters only when required
> is a more effective way to ensure compatibility.
No. I don't see the need to be overly cooperative with people who do
not care about what they ship.
If you want to run on broken systems, pass the option that allow you
to do so. But don't make it more complicated for people who have HW
that actually works.
I would rather remove the option to disable MPAM altogether and leave
these broken systems completely unsupported.
M.
--
Without deviation from the norm, progress is not possible.
prev parent reply other threads:[~2025-12-17 15:30 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-12-17 15:11 [PATCH v1] arm64/mpam: Replace the arm64.nompam parameter with arm64.mpam tanze
2025-12-17 15:30 ` Marc Zyngier [this message]
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=86wm2lm8hg.wl-maz@kernel.org \
--to=maz@kernel.org \
--cc=catalin.marinas@arm.com \
--cc=james.morse@arm.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=tanze@kylinos.cn \
--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;
as well as URLs for NNTP newsgroup(s).