From: Catalin Marinas <catalin.marinas@arm.com>
To: Peng Fan <peng.fan@oss.nxp.com>
Cc: Will Deacon <will@kernel.org>,
Mark Rutland <mark.rutland@arm.com>,
Jonathan Corbet <corbet@lwn.net>,
Shuah Khan <skhan@linuxfoundation.org>,
Randy Dunlap <rdunlap@infradead.org>,
Marc Zyngier <maz@kernel.org>, Oliver Upton <oupton@kernel.org>,
Fuad Tabba <fuad.tabba@linux.dev>,
Joey Gouly <joey.gouly@arm.com>,
Steffen Eiden <seiden@linux.ibm.com>,
Suzuki K Poulose <suzuki.poulose@arm.com>,
Zenghui Yu <yuzenghui@huawei.com>,
"Ivan T. Ivanov" <iivanov@suse.de>,
Francesco Dolcini <francesco@dolcini.it>,
Frank Li <frank.li@nxp.com>,
linux-arm-kernel@lists.infradead.org, linux-doc@vger.kernel.org,
linux-kernel@vger.kernel.org, kvmarm@lists.linux.dev,
imx@lists.linux.dev, Peng Fan <peng.fan@nxp.com>
Subject: Re: [PATCH v4] arm64: errata: Add NXP iMX8QM workaround for A53 cache coherency issue
Date: Fri, 9 Oct 2026 08:22:55 +0100 [thread overview]
Message-ID: <asiWTxgGxJ5JIFcl@arm.com> (raw)
In-Reply-To: <aseZUwi0CYTXuE/I@shlinux89>
On Thu, Oct 08, 2026 at 09:23:31PM +0800, Peng Fan wrote:
> On Tue, Oct 06, 2026 at 12:18:42PM +0100, Catalin Marinas wrote:
> >On Mon, Aug 24, 2026 at 12:02:04PM +0800, Peng Fan (OSS) wrote:
> >> - Disabling KVM since correct TLB maintenance cannot be guaranteed
> >> for guests.
> >
> >Do you need virtualisation on such platform? An alternative would be for
>
> We not have KVM support in our software release for i.MX8QM.
>
> >the guests to be aware of the erratum as well and use the right TLBI/IC
> >ops. But you'd also need to upgrade the VMID-aware ops in KVM (unless
> >the hardware can't work around stage 2 TLBI at all).
>
> We not have test cases for this since KVM is not in our release scope.
> Could we take this as a future enablement to avoid uneccessary churn
Yes, you can leave it out if you don't care about the KVM use-cases.
> >There's a precedent with 4311569 to wire up a SoC erratum into the CPU
> >errata framework. That one is a system wide feature, so only probed once
> >for the CPUs coming up at boot (though still probed for each late CPUs).
> >For iMX, you need this turned on early, hence the boot probing. But
> >calling it a strict boot CPU feature is a bit of a stretch. It also gets
> >probed on every CPU, unnecessarily.
> >
> >I think we could do with something like below (maybe as a preparatory
> >patch). We could also add it to 4311569 even if it changes its scope
> >from system to boot CPU (the early param is available).
> >
> >Only compile-tested and haven't tried wiring up your workaround:
>
> With type set to ARM64_CPUCAP_SOC_ERRATUM for i.MX8QM and your patch
> applied, I not see issues in my test.
>
> Would you post it as a formal patch or need me to include your patch
> with i.MX8QM errata patch in a patchset?
Please post it with your patchset. Feel free to add a co-developed-by or
suggested-by me on the new cpucap proposal.
--
Catalin
prev parent reply other threads:[~2026-10-09 7:23 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-08-24 4:02 [PATCH v4] arm64: errata: Add NXP iMX8QM workaround for A53 cache coherency issue Peng Fan (OSS)
2026-08-25 7:06 ` Franz Schnyder
2026-09-15 15:04 ` Peng Fan
2026-09-15 15:02 ` Peng Fan
2026-10-05 8:08 ` Francesco Dolcini
2026-10-06 11:18 ` Catalin Marinas
2026-10-08 13:23 ` Peng Fan
2026-10-09 7:22 ` Catalin Marinas [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=asiWTxgGxJ5JIFcl@arm.com \
--to=catalin.marinas@arm.com \
--cc=corbet@lwn.net \
--cc=francesco@dolcini.it \
--cc=frank.li@nxp.com \
--cc=fuad.tabba@linux.dev \
--cc=iivanov@suse.de \
--cc=imx@lists.linux.dev \
--cc=joey.gouly@arm.com \
--cc=kvmarm@lists.linux.dev \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mark.rutland@arm.com \
--cc=maz@kernel.org \
--cc=oupton@kernel.org \
--cc=peng.fan@nxp.com \
--cc=peng.fan@oss.nxp.com \
--cc=rdunlap@infradead.org \
--cc=seiden@linux.ibm.com \
--cc=skhan@linuxfoundation.org \
--cc=suzuki.poulose@arm.com \
--cc=will@kernel.org \
--cc=yuzenghui@huawei.com \
/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.