From: Borislav Petkov <bp@suse.de>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: x86-ml <x86@kernel.org>, lkml <linux-kernel@vger.kernel.org>
Subject: [GIT PULL] x86/urgent for v5.16-rc1
Date: Sun, 14 Nov 2021 11:00:38 +0100 [thread overview]
Message-ID: <YZDeRkX012h/ZJzR@zn.tnic> (raw)
Hi Linus,
please pull a couple of x86/urgent fixes which accumulated during the
merge window.
Thx.
---
The following changes since commit 879dbe9ffebc1328717cd66eab7e4918a3f499bd:
Merge tag 'x86_sgx_for_v5.16_rc1' of git://git.kernel.org/pub/scm/linux/kernel/git/tip/tip (2021-11-01 15:54:07 -0700)
are available in the Git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/tip/tip.git tags/x86_urgent_for_v5.16_rc1
for you to fetch changes up to fbdb5e8f2926ae9636c9fa6f42c7426132ddeeb2:
x86/cpu: Add Raptor Lake to Intel family (2021-11-12 11:46:06 -0800)
----------------------------------------------------------------
- Add the model number of a new, Raptor Lake CPU, to intel-family.h
- Do not log spurious corrected MCEs on SKL too, due to an erratum
- Clarify the path of paravirt ops patches upstream
- Add an optimization to avoid writing out AMX components to sigframes
when former are in init state
----------------------------------------------------------------
Dave Hansen (1):
x86/fpu: Optimize out sigframe xfeatures when in init state
Dave Jones (1):
x86/mce: Add errata workaround for Skylake SKX37
Juergen Gross (1):
MAINTAINERS: Add some information to PARAVIRT_OPS entry
Tony Luck (1):
x86/cpu: Add Raptor Lake to Intel family
Documentation/x86/xstate.rst | 9 +++++++++
MAINTAINERS | 2 ++
arch/x86/include/asm/fpu/xcr.h | 12 ++++++++++++
arch/x86/include/asm/fpu/xstate.h | 7 +++++++
arch/x86/include/asm/intel-family.h | 2 ++
arch/x86/kernel/cpu/cpuid-deps.c | 1 +
arch/x86/kernel/cpu/mce/intel.c | 5 +++--
arch/x86/kernel/fpu/xstate.h | 37 +++++++++++++++++++++++++++++++++++--
8 files changed, 71 insertions(+), 4 deletions(-)
--
Regards/Gruss,
Boris.
SUSE Software Solutions Germany GmbH, GF: Ivo Totev, HRB 36809, AG Nürnberg
next reply other threads:[~2021-11-14 10:01 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-11-14 10:00 Borislav Petkov [this message]
2021-11-14 17:52 ` pr-tracker-bot
2021-11-21 15:09 [GIT pull] perf/urgent " Thomas Gleixner
2021-11-21 15:09 ` [GIT pull] x86/urgent " Thomas Gleixner
2021-11-21 19:39 ` 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=YZDeRkX012h/ZJzR@zn.tnic \
--to=bp@suse.de \
--cc=linux-kernel@vger.kernel.org \
--cc=torvalds@linux-foundation.org \
--cc=x86@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
all inboxes | Powered by JetHome®