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, Borislav Petkov <bp@alien8.de>,
	Thomas Gleixner <tglx@linutronix.de>,
	Peter Zijlstra <a.p.zijlstra@chello.nl>,
	Andrew Morton <akpm@linux-foundation.org>
Subject: [GIT PULL] x86/cpu changes for v5.5
Date: Mon, 25 Nov 2019 14:38:26 +0100	[thread overview]
Message-ID: <20191125133826.GA88582@gmail.com> (raw)

Linus,

Please pull the latest x86-cpu-for-linus git tree from:

   git://git.kernel.org/pub/scm/linux/kernel/git/tip/tip.git x86-cpu-for-linus

   # HEAD: db8c33f8b5bea59d00ca12dcd6b65d01b1ea98ef x86/cpu: Align the x86_capability array to size of unsigned long

Misc changes:

 - math-emu fixes,

 - CPUID updates,

 - sanity-check RDRAND output to see whether the CPU at least
   pretends to produce random data,

 - various unaligned-access across cachelines fixes in preparation of 
   hardware level split-lock detection,

 - Fix MAXSMP constraints to not allow !CPUMASK_OFFSTACK kernels with 
   larger than 512 NR_CPUS.


 Thanks,

	Ingo

------------------>
Arnd Bergmann (2):
      x86/math-emu: Check __copy_from_user() result
      x86/math-emu: Limit MATH_EMULATION to 486SX compatibles

Babu Moger (3):
      x86/cpufeatures: Add feature bit RDPRU on AMD
      x86/Kconfig: Rename UMIP config parameter
      x86/umip: Make the comments vendor-agnostic

Borislav Petkov (1):
      x86/rdrand: Sanity-check RDRAND output

Fenghua Yu (2):
      x86/cpu: Align cpu_caps_cleared and cpu_caps_set to unsigned long
      x86/cpu: Align the x86_capability array to size of unsigned long

Scott Wood (1):
      x86/Kconfig: Enforce limit of 512 CPUs with MAXSMP and no CPUMASK_OFFSTACK


 arch/x86/Kconfig                               | 22 +++++++++++-----------
 arch/x86/Kconfig.cpu                           | 25 ++++++++++++++++---------
 arch/x86/Makefile_32.cpu                       |  1 +
 arch/x86/include/asm/cpufeatures.h             |  1 +
 arch/x86/include/asm/disabled-features.h       |  2 +-
 arch/x86/include/asm/module.h                  |  2 ++
 arch/x86/include/asm/processor.h               | 10 +++++++++-
 arch/x86/include/asm/umip.h                    |  4 ++--
 arch/x86/kernel/Makefile                       |  2 +-
 arch/x86/kernel/cpu/common.c                   |  5 +++--
 arch/x86/kernel/cpu/rdrand.c                   | 22 +++++++++++++++++++++-
 arch/x86/kernel/umip.c                         | 12 ++++++------
 arch/x86/math-emu/fpu_system.h                 |  6 ++++--
 arch/x86/math-emu/reg_ld_str.c                 |  6 +++---
 tools/arch/x86/include/asm/disabled-features.h |  2 +-
 15 files changed, 82 insertions(+), 40 deletions(-)


             reply	other threads:[~2019-11-25 13:38 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-11-25 13:38 Ingo Molnar [this message]
2019-11-26 19:30 ` [GIT PULL] x86/cpu changes for v5.5 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=20191125133826.GA88582@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