From: Marc Zyngier <maz@kernel.org>
To: Xi Ruoyao <xry111@xry111.site>
Cc: James Morse <james.morse@arm.com>,
Anshuman Khandual <anshuman.khandual@arm.com>,
Ben Horgan <ben.horgan@arm.com>, Will Deacon <will@kernel.org>,
linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org,
Shameer Kolothum <shameerali.kolothum.thodi@huawei.com>,
Mingcong Bai <jeffbai@aosc.io>,
Shaopeng Tan <tan.shaopeng@fujitsu.com>
Subject: Re: [PATCH v4] arm64: Add override for MPAM
Date: Mon, 02 Jun 2025 07:38:30 +0100 [thread overview]
Message-ID: <87o6v6ejh5.wl-maz@kernel.org> (raw)
In-Reply-To: <20250602043723.216338-1-xry111@xry111.site>
On Mon, 02 Jun 2025 05:33:21 +0100,
Xi Ruoyao <xry111@xry111.site> wrote:
>
> As the message of the commit 09e6b306f3ba ("arm64: cpufeature: discover
> CPU support for MPAM") already states, if a buggy firmware fails to
> either enable MPAM or emulate the trap as if it were disabled, the
> kernel will just fail to boot. While upgrading the firmware should be
> the best solution, we have some hardware of which the vendor have made
> no response 2 months after we requested a firmware update. Allow
> overriding it so our devices don't become some e-waste.
>
> Cc: James Morse <james.morse@arm.com>
> Cc: Marc Zyngier <maz@kernel.org>
> Cc: Will Deacon <will@kernel.org>
> Cc: Shameer Kolothum <shameerali.kolothum.thodi@huawei.com>
> Cc: Mingcong Bai <jeffbai@aosc.io>
> Cc: Shaopeng Tan <tan.shaopeng@fujitsu.com>
> Cc: Ben Horgan <ben.horgan@arm.com>
> Signed-off-by: Xi Ruoyao <xry111@xry111.site>
Reviewed-by: Marc Zyngier <maz@kernel.org>
M.
--
Jazz isn't dead. It just smells funny.
next prev parent reply other threads:[~2025-06-02 6:41 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-06-02 4:33 [PATCH v4] arm64: Add override for MPAM Xi Ruoyao
2025-06-02 6:38 ` Marc Zyngier [this message]
2025-06-02 13:42 ` Will Deacon
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=87o6v6ejh5.wl-maz@kernel.org \
--to=maz@kernel.org \
--cc=anshuman.khandual@arm.com \
--cc=ben.horgan@arm.com \
--cc=james.morse@arm.com \
--cc=jeffbai@aosc.io \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=shameerali.kolothum.thodi@huawei.com \
--cc=tan.shaopeng@fujitsu.com \
--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 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.