From: Will Deacon <will@kernel.org>
To: Marc Zyngier <maz@kernel.org>,
Mark Rutland <mark.rutland@arm.com>,
Suzuki K Poulose <suzuki.poulose@arm.com>,
Catalin Marinas <catalin.marinas@arm.com>,
Shreyas K K <quic_shrekk@quicinc.com>
Cc: kernel-team@android.com, Will Deacon <will@kernel.org>,
linux-kernel@vger.kernel.org,
Prasanna Kumar <quic_kprasan@quicinc.com>,
linux-arm-msm@vger.kernel.org,
Andre Przywara <andre.przywara@arm.com>,
linux-arm-kernel@lists.infradead.org,
Sai Prakash Ranjan <quic_saipraka@quicinc.com>,
Jeffrey Hugo <quic_jhugo@quicinc.com>,
Rajendra Nayak <quic_rjendra@quicinc.com>
Subject: Re: [PATCH V3] arm64: Enable repeat tlbi workaround on KRYO4XX gold CPUs
Date: Thu, 12 May 2022 14:05:06 +0100 [thread overview]
Message-ID: <165235773290.1834134.2218780460929548936.b4-ty@kernel.org> (raw)
In-Reply-To: <20220512110134.12179-1-quic_shrekk@quicinc.com>
On Thu, 12 May 2022 16:31:34 +0530, Shreyas K K wrote:
> Add KRYO4XX gold/big cores to the list of CPUs that need the
> repeat TLBI workaround. Apply this to the affected
> KRYO4XX cores (rcpe to rfpe).
>
> The variant and revision bits are implementation defined and are
> different from the their Cortex CPU counterparts on which they are
> based on, i.e., (r0p0 to r3p0) is equivalent to (rcpe to rfpe).
>
> [...]
Applied to arm64 (for-next/fixes), thanks!
[1/1] arm64: Enable repeat tlbi workaround on KRYO4XX gold CPUs
https://git.kernel.org/arm64/c/51f559d66527
Cheers,
--
Will
https://fixes.arm64.dev
https://next.arm64.dev
https://will.arm64.dev
prev parent reply other threads:[~2022-05-12 13:05 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-05-12 11:01 Shreyas K K
2022-05-12 11:05 ` Sai Prakash Ranjan
2022-05-12 13:05 ` Will Deacon [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=165235773290.1834134.2218780460929548936.b4-ty@kernel.org \
--to=will@kernel.org \
--cc=andre.przywara@arm.com \
--cc=catalin.marinas@arm.com \
--cc=kernel-team@android.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mark.rutland@arm.com \
--cc=maz@kernel.org \
--cc=quic_jhugo@quicinc.com \
--cc=quic_kprasan@quicinc.com \
--cc=quic_rjendra@quicinc.com \
--cc=quic_saipraka@quicinc.com \
--cc=quic_shrekk@quicinc.com \
--cc=suzuki.poulose@arm.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 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®