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/cpu updates for v5.10
Date: Mon, 12 Oct 2020 11:57:56 +0200 [thread overview]
Message-ID: <20201012095756.GC25311@zn.tnic> (raw)
Hi Linus,
please pull the x86/cpu changes collected this time.
Thx.
---
The following changes since commit 9123e3a74ec7b934a4a099e98af6a61c2f80bbf5:
Linux 5.9-rc1 (2020-08-16 13:04:57 -0700)
are available in the Git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/tip/tip.git tags/x86_cpu_for_v5.10
for you to fetch changes up to e1ebb2b49048c4767cfa0d8466f9c701e549fa5e:
KVM: SVM: Don't flush cache if hardware enforces cache coherency across encryption domains (2020-09-19 20:46:59 +0200)
----------------------------------------------------------------
* Add support for hardware-enforced cache coherency on AMD which
obviates the need to flush cachelines before changing the PTE encryption
bit, by Krish Sadhukhan.
* Add Centaur initialization support for families >= 7, by Tony W
Wang-oc.
* Add a feature flag for, and expose TSX suspend load tracking feature
to KVM, by Cathy Zhang.
* Emulate SLDT and STR so that windows programs don't crash on UMIP
machines, by Brendan Shanks and Ricardo Neri.
* Use the new SERIALIZE insn on Intel hardware which supports it, by
Ricardo Neri.
* Misc cleanups and fixes.
----------------------------------------------------------------
Brendan Shanks (1):
x86/umip: Add emulation/spoofing for SLDT and STR instructions
Cathy Zhang (1):
x86/kvm: Expose TSX Suspend Load Tracking feature
Ingo Molnar (1):
x86/cpu: Fix typos and improve the comments in sync_core()
Krish Sadhukhan (3):
x86/cpu: Add hardware-enforced cache coherency as a CPUID feature
x86/mm/pat: Don't flush cache if hardware enforces cache coherency across encryption domnains
KVM: SVM: Don't flush cache if hardware enforces cache coherency across encryption domains
Kyung Min Park (1):
x86/cpufeatures: Enumerate TSX suspend load address tracking instructions
Ricardo Neri (1):
x86/cpu: Use SERIALIZE in sync_core() when available
Tony W Wang-oc (2):
x86/cpu/centaur: Replace two-condition switch-case with an if statement
x86/cpu/centaur: Add Centaur family >=7 CPUs initialization support
Uros Bizjak (1):
x86/cpu: Use XGETBV and XSETBV mnemonics in fpu/internal.h
arch/x86/include/asm/cpufeatures.h | 3 ++-
arch/x86/include/asm/fpu/internal.h | 7 ++-----
arch/x86/include/asm/special_insns.h | 6 ++++++
arch/x86/include/asm/sync_core.h | 34 +++++++++++++++++++-----------
arch/x86/kernel/cpu/centaur.c | 27 +++++++++++-------------
arch/x86/kernel/cpu/scattered.c | 1 +
arch/x86/kernel/umip.c | 40 ++++++++++++++++++++++++------------
arch/x86/kvm/cpuid.c | 2 +-
arch/x86/kvm/svm/sev.c | 3 ++-
arch/x86/mm/pat/set_memory.c | 2 +-
10 files changed, 76 insertions(+), 49 deletions(-)
--
Regards/Gruss,
Boris.
SUSE Software Solutions Germany GmbH, GF: Felix Imendörffer, HRB 36809, AG Nürnberg
next reply other threads:[~2020-10-12 9:58 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-10-12 9:57 Borislav Petkov [this message]
2020-10-12 18:21 ` [GIT PULL] x86/cpu updates for v5.10 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=20201012095756.GC25311@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