All of lore.kernel.org
 help / color / mirror / Atom feed
From: linux@armlinux.org.uk (Russell King - ARM Linux)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v2 0/5] Spectre big.Little updates
Date: Tue, 6 Nov 2018 12:37:00 +0000	[thread overview]
Message-ID: <20181106123700.GA30658@n2100.armlinux.org.uk> (raw)

This series of patches allows Spectre to be worked around on
big.Little systems, and as far as I'm aware, completes the Spectre
workarounds as were known at the beginning of the year for 32-bit
ARM.

In order to solve Spectre for such systems, we need to introduce
per-CPU indirection of the "processor" vtable, but we are unable to
use the kernel's per-CPU infrastructure as this is not initialised
early enough.

To work around that, we fall back to using a static array of
processor vtables indexed by the logical CPU number.  This should
not be a problem as 32-bit ARM systems are limited to 8 logical
CPUs.

Changes in v2:
We use CPU0's vtable for some of the function methods to avoid
using the CPU number in pre-emptable code, and validate that these
methods are identical across all CPUs in the system.

 arch/arm/include/asm/cputype.h  |  1 +
 arch/arm/include/asm/proc-fns.h | 58 ++++++++++++++++++++++++++++++++---------
 arch/arm/kernel/bugs.c          |  4 +--
 arch/arm/kernel/head-common.S   |  6 ++---
 arch/arm/kernel/setup.c         | 40 +++++++++++++++++-----------
 arch/arm/kernel/smp.c           | 31 ++++++++++++++++++++++
 arch/arm/mm/proc-v7-bugs.c      | 17 ++----------
 7 files changed, 110 insertions(+), 47 deletions(-)


-- 
RMK's Patch system: http://www.armlinux.org.uk/developer/patches/
FTTC broadband for 0.8mile line in suburbia: sync at 12.1Mbps down 622kbps up
According to speedtest.net: 11.9Mbps down 500kbps up

             reply	other threads:[~2018-11-06 12:37 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-11-06 12:37 Russell King - ARM Linux [this message]
2018-11-06 12:38 ` [PATCH 1/5] ARM: make lookup_processor_type() non-__init Russell King
2018-11-06 12:38 ` [PATCH v2 " Russell King
2018-11-06 12:38 ` [PATCH v2 2/5] ARM: split out processor lookup Russell King
2018-11-06 12:39 ` [PATCH v2 3/5] ARM: clean up per-processor check_bugs method call Russell King
2018-11-06 12:39 ` [PATCH v2 4/5] ARM: add PROC_VTABLE and PROC_TABLE macros Russell King
2018-11-06 12:39 ` [PATCH v2 5/5] ARM: spectre-v2: per-CPU vtables to work around big.Little systems Russell King
2018-11-07 17:42   ` Julien Thierry
2018-12-06  9:32   ` Marek Szyprowski
2018-12-06 10:00     ` Russell King - ARM Linux
2018-12-06 10:24       ` Krzysztof Kozlowski
2018-12-06 12:39         ` Russell King - ARM Linux
2018-12-06 13:54           ` Krzysztof Kozlowski
2018-12-06 14:07             ` Russell King - ARM Linux
2018-12-06 14:30               ` Krzysztof Kozlowski
2018-12-06 14:37                 ` Russell King - ARM Linux
2018-12-06 15:03                   ` Krzysztof Kozlowski
2018-12-06 15:31                     ` Russell King - ARM Linux
2018-12-06 15:54                       ` Marek Szyprowski
2018-12-06 15:58                       ` Krzysztof Kozlowski
2018-12-07  9:11                         ` Ard Biesheuvel
2018-12-07 10:37                           ` Russell King - ARM Linux

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=20181106123700.GA30658@n2100.armlinux.org.uk \
    --to=linux@armlinux.org.uk \
    --cc=linux-arm-kernel@lists.infradead.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 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.