From: Randy Dunlap <rdunlap@infradead.org>
To: Lucas Wei <lucaswei@google.com>
Cc: Catalin Marinas <catalin.marinas@arm.com>,
Will Deacon <will@kernel.org>, Jonathan Corbet <corbet@lwn.net>,
sjadavani@google.com, stable@vger.kernel.org,
kernel-team@android.com, linux-arm-kernel@lists.infradead.org,
linux-doc@vger.kernel.org, linux-kernel@vger.kernel.org,
robin.murphy@arm.com, maz@kernel.org
Subject: Re: [PATCH v3] arm64: errata: Workaround for SI L1 downstream coherency issue
Date: Wed, 14 Jan 2026 22:26:16 -0800 [thread overview]
Message-ID: <e08ada29-556e-4251-b4bb-c122ca3ec3e0@infradead.org> (raw)
In-Reply-To: <CAPTxkvRXmVB9MbPX2vkyhAnLDyJX7YviekOH=y3EcS_1e796Zg@mail.gmail.com>
On 1/14/26 6:11 PM, Lucas Wei wrote:
> Hi Randy,
>
>>> +/*
>>> + * We have some earlier use cases to call cache maintenance operation functions, for example,
>>> + * dcache_inval_poc() and dcache_clean_poc() in head.S, before making decision to turn on this
>>> + * workaround. Since the scope of this workaround is limited to non-coherent DMA agents, its
>>> + * safe to have the workaround off by default.
>>
>> But it's not off by default...
>
> I think it's off by default.
> Would you point me to where the workaround was enabled without cmdline?
I'm probably confused by the Kconfig option defaulting to 'y' but the run-time option
itself is still off by default. Sorry for the noise.
+config ARM64_ERRATUM_4311569
+ bool "SI L1: 4311569: workaround for premature CMO completion erratum"
+ default y
+ help
+ This option adds the workaround for ARM SI L1 erratum 4311569.
--
~Randy
next prev parent reply other threads:[~2026-01-15 6:26 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-01-14 14:52 Lucas Wei
2026-01-14 18:25 ` Randy Dunlap
2026-01-15 2:11 ` Lucas Wei
2026-01-15 6:26 ` Randy Dunlap [this message]
2026-01-23 17:49 ` 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=e08ada29-556e-4251-b4bb-c122ca3ec3e0@infradead.org \
--to=rdunlap@infradead.org \
--cc=catalin.marinas@arm.com \
--cc=corbet@lwn.net \
--cc=kernel-team@android.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=lucaswei@google.com \
--cc=maz@kernel.org \
--cc=robin.murphy@arm.com \
--cc=sjadavani@google.com \
--cc=stable@vger.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
all inboxes | Powered by JetHome®