From: Douglas Anderson <dianders@chromium.org>
To: Catalin Marinas <catalin.marinas@arm.com>,
Will Deacon <will@kernel.org>,
Mark Rutland <mark.rutland@arm.com>
Cc: Julius Werner <jwerner@chromium.org>,
Jeffrey Hugo <quic_jhugo@quicinc.com>,
Roxana Bradescu <roxabee@google.com>,
bjorn.andersson@oss.qualcomm.com,
linux-arm-kernel@lists.infradead.org,
Trilok Soni <quic_tsoni@quicinc.com>,
linux-arm-msm@vger.kernel.org,
Douglas Anderson <dianders@chromium.org>,
Anshuman Khandual <anshuman.khandual@arm.com>,
Besar Wicaksono <bwicaksono@nvidia.com>,
D Scott Phillips <scott@os.amperecomputing.com>,
Easwar Hariharan <eahariha@linux.microsoft.com>,
Oliver Upton <oliver.upton@linux.dev>,
linux-kernel@vger.kernel.org
Subject: [PATCH 0/6] arm64: errata: Add Qualcomm CPUs to the Spectre mitigation lists
Date: Mon, 9 Dec 2024 09:43:10 -0800 [thread overview]
Message-ID: <20241209174430.2904353-1-dianders@chromium.org> (raw)
Since Qualcomm CPUs are all derivatives of ARM cores they all have
unique MIDR values. This means that the tables listing necessary
Spectre mitigations need special entries for them. However, those
entries are not present and that means that some Spectre mitigations
are lacking for Qualcomm CPUs.
I've made an attempt at **GUESSING** what the right patches should be
to enable mitigations for Qualcomm CPUs. This is mostly me searching
the web to figure out what ARM cores various Qualcomm cores are based
off of.
These patches get more and more sketchy as the series progresses and I
have noted that the later patces DON'T EVEN COMPILE. I have included
them to make it obvious that I think these cores are affected even if
I don't have all the right information to mitigate them. Hopefully
Qualcomm can come and fix this mess for me.
I'll note that I am certainly no expert on Spectre. Mostly I ended up
here running `lscpu` on a device and noticing that it thought that it
wasn't affected by Spectre v2 when I thought it was.
Douglas Anderson (6):
arm64: errata: Add QCOM_KRYO_4XX_GOLD to the spectre_bhb_k24_list
arm64: errata: Add QCOM_KRYO_2XX_GOLD to the
spectre_bhb_firmware_mitigated_list
arm64: cputype: Add QCOM_CPU_PART_KRYO_3XX_GOLD
arm64: errata: Add QCOM_KRYO_3XX_GOLD to the
spectre_bhb_firmware_mitigated_list
arm64: errata: Add QCOM_KRYO_5XX_GOLD to the spectre_bhb_k24_list
arm64: errata: Add QCOM_KRYO_6XX_GOLD/PRIME to the
spectre_bhb_k32_list
arch/arm64/include/asm/cputype.h | 2 ++
arch/arm64/kernel/proton-pack.c | 6 ++++++
2 files changed, 8 insertions(+)
--
2.47.0.338.g60cca15819-goog
next reply other threads:[~2024-12-09 17:46 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-12-09 17:43 Douglas Anderson [this message]
2024-12-09 17:43 ` [PATCH 1/6] arm64: errata: Add QCOM_KRYO_4XX_GOLD to the spectre_bhb_k24_list Douglas Anderson
2024-12-09 17:43 ` [PATCH 2/6] arm64: errata: Add QCOM_KRYO_2XX_GOLD to the spectre_bhb_firmware_mitigated_list Douglas Anderson
2024-12-09 23:13 ` Dmitry Baryshkov
2024-12-09 23:34 ` Julius Werner
2024-12-09 23:52 ` Dmitry Baryshkov
2024-12-09 17:43 ` [PATCH 3/6] arm64: cputype: Add QCOM_CPU_PART_KRYO_3XX_GOLD Douglas Anderson
2024-12-09 23:02 ` Dmitry Baryshkov
2024-12-09 17:43 ` [PATCH 4/6] arm64: errata: Add QCOM_KRYO_3XX_GOLD to the spectre_bhb_firmware_mitigated_list Douglas Anderson
2024-12-09 17:43 ` [PATCH 5/6] arm64: errata: Add QCOM_KRYO_5XX_GOLD to the spectre_bhb_k24_list Douglas Anderson
2024-12-09 23:07 ` Dmitry Baryshkov
2024-12-14 0:53 ` Doug Anderson
2024-12-14 1:28 ` Julius Werner
2024-12-14 11:39 ` Dmitry Baryshkov
2024-12-16 21:53 ` Doug Anderson
2024-12-10 14:45 ` kernel test robot
2024-12-10 14:45 ` kernel test robot
2024-12-09 17:43 ` [PATCH 6/6] arm64: errata: Add QCOM_KRYO_6XX_GOLD/PRIME to the spectre_bhb_k32_list Douglas Anderson
2024-12-09 23:09 ` Dmitry Baryshkov
2024-12-14 0:53 ` Doug Anderson
2024-12-10 17:02 ` kernel test robot
2024-12-10 15:56 ` [PATCH 0/6] arm64: errata: Add Qualcomm CPUs to the Spectre mitigation lists Will Deacon
2024-12-10 16:53 ` Doug Anderson
2024-12-11 21:34 ` 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=20241209174430.2904353-1-dianders@chromium.org \
--to=dianders@chromium.org \
--cc=anshuman.khandual@arm.com \
--cc=bjorn.andersson@oss.qualcomm.com \
--cc=bwicaksono@nvidia.com \
--cc=catalin.marinas@arm.com \
--cc=eahariha@linux.microsoft.com \
--cc=jwerner@chromium.org \
--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=oliver.upton@linux.dev \
--cc=quic_jhugo@quicinc.com \
--cc=quic_tsoni@quicinc.com \
--cc=roxabee@google.com \
--cc=scott@os.amperecomputing.com \
--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;
as well as URLs for NNTP newsgroup(s).