mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Marc Zyngier <marc.zyngier@arm.com>
To: linux-arm-kernel@lists.infradead.org, linux-kernel@vger.kernel.org
Cc: Jeremy Linton <jeremy.linton@arm.com>,
	Will Deacon <will.deacon@arm.com>,
	Catalin Marinas <catalin.marinas@arm.com>
Subject: [PATCH v2 0/2] Spectre-v2 detection fixes
Date: Mon, 14 Jan 2019 10:35:26 +0000	[thread overview]
Message-ID: <20190114103528.52931-1-marc.zyngier@arm.com> (raw)

These two patches, now built on top of Jeremy's sysfs series, tweak
the way we detect the Spectre-v2 vulnerability by switching from a
blacklist to a whitelist, making sure we correctly detect unmitigated
systems.

We further improve things by relying on firmware to tell us about CPUs
that are part of an affected system, but that are not affected
themselves (big-little type).

For convenience, I've pushed out a branch containing both Jeremy's v3
series and these patches at [1].

[1] git://git.kernel.org/pub/scm/linux/kernel/git/maz/arm-platforms.git arm64/spectre-sysfs

Marc Zyngier (2):
  arm64: Advertise mitigation of Spectre-v2, or lack thereof
  arm64: Use firmware to detect CPUs that are not affected by Spectre-v2

 arch/arm64/kernel/cpu_errata.c | 141 +++++++++++++++++----------------
 1 file changed, 73 insertions(+), 68 deletions(-)

-- 
2.20.1


             reply	other threads:[~2019-01-14 10:35 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-01-14 10:35 Marc Zyngier [this message]
2019-01-14 10:35 ` [PATCH v2 1/2] arm64: Advertise mitigation of Spectre-v2, or lack thereof Marc Zyngier
2019-01-14 17:06   ` Jeremy Linton
2019-01-14 10:35 ` [PATCH v2 2/2] arm64: Use firmware to detect CPUs that are not affected by Spectre-v2 Marc Zyngier

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=20190114103528.52931-1-marc.zyngier@arm.com \
    --to=marc.zyngier@arm.com \
    --cc=catalin.marinas@arm.com \
    --cc=jeremy.linton@arm.com \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=will.deacon@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®