public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Ingo Molnar <mingo@kernel.org>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: linux-kernel@vger.kernel.org,
	Thomas Gleixner <tglx@linutronix.de>,
	Borislav Petkov <bp@alien8.de>,
	Peter Zijlstra <a.p.zijlstra@chello.nl>,
	Andrew Morton <akpm@linux-foundation.org>
Subject: [GIT PULL] x86/cpu changes for v5.9
Date: Mon, 3 Aug 2020 20:03:36 +0200	[thread overview]
Message-ID: <20200803180336.GA1041383@gmail.com> (raw)

Linus,

Please pull the latest x86/cpu git tree from:

   git://git.kernel.org/pub/scm/linux/kernel/git/tip/tip.git x86-cpu-2020-08-03

   # HEAD: f69ca629d89d65737537e05308ac531f7bb07d5c x86/cpu: Refactor sync_core() for readability

Misc changes:

 - Prepare for Intel's new SERIALIZE instruction
 - Enable split-lock debugging on more CPUs
 - Add more Intel CPU models
 - Optimize stack canary initialization a bit
 - Simplify the Spectre logic a bit

  out-of-topic modifications in x86-cpu-2020-08-03:
  ---------------------------------------------------
  drivers/misc/sgi-gru/grufault.c    # 9998a9832c40: x86/cpu: Relocate sync_core(
  drivers/misc/sgi-gru/gruhandles.c  # 9998a9832c40: x86/cpu: Relocate sync_core(
  drivers/misc/sgi-gru/grukservices.c# 9998a9832c40: x86/cpu: Relocate sync_core(

 Thanks,

	Ingo

------------------>
Borislav Petkov (1):
      x86/speculation: Merge one test in spectre_v2_user_select_mitigation()

Brian Gerst (1):
      x86/stackprotector: Pre-initialize canary for secondary CPUs

Fenghua Yu (1):
      x86/split_lock: Enable the split lock feature on Sapphire Rapids and Alder Lake CPUs

Ricardo Neri (3):
      x86/cpufeatures: Add enumeration for SERIALIZE instruction
      x86/cpu: Relocate sync_core() to sync_core.h
      x86/cpu: Refactor sync_core() for readability

Tony Luck (1):
      x86/cpu: Add Lakefield, Alder Lake and Rocket Lake models to the to Intel CPU family


 arch/x86/include/asm/cpufeatures.h    |  1 +
 arch/x86/include/asm/intel-family.h   |  7 ++++
 arch/x86/include/asm/processor.h      | 64 -------------------------------
 arch/x86/include/asm/special_insns.h  |  1 -
 arch/x86/include/asm/stackprotector.h | 12 ++++++
 arch/x86/include/asm/sync_core.h      | 72 +++++++++++++++++++++++++++++++++++
 arch/x86/kernel/alternative.c         |  1 +
 arch/x86/kernel/cpu/bugs.c            | 13 ++-----
 arch/x86/kernel/cpu/intel.c           |  2 +
 arch/x86/kernel/cpu/mce/core.c        |  1 +
 arch/x86/kernel/smpboot.c             | 14 +------
 arch/x86/xen/smp_pv.c                 |  2 -
 drivers/misc/sgi-gru/grufault.c       |  1 +
 drivers/misc/sgi-gru/gruhandles.c     |  1 +
 drivers/misc/sgi-gru/grukservices.c   |  1 +
 15 files changed, 105 insertions(+), 88 deletions(-)

             reply	other threads:[~2020-08-03 18:03 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-08-03 18:03 Ingo Molnar [this message]
2020-08-04  0:50 ` [GIT PULL] x86/cpu changes for v5.9 pr-tracker-bot

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=20200803180336.GA1041383@gmail.com \
    --to=mingo@kernel.org \
    --cc=a.p.zijlstra@chello.nl \
    --cc=akpm@linux-foundation.org \
    --cc=bp@alien8.de \
    --cc=linux-kernel@vger.kernel.org \
    --cc=tglx@linutronix.de \
    --cc=torvalds@linux-foundation.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