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 for v5.17
Date: Mon, 10 Jan 2022 12:16:39 +0100 [thread overview]
Message-ID: <YdwVl0H54fmUIux0@zn.tnic> (raw)
Hi Linus,
please pull two x86/cpu updates for 5.17.
Thx.
---
The following changes since commit 136057256686de39cc3a07c2e39ef6bc43003ff6:
Linux 5.16-rc2 (2021-11-21 13:47:39 -0800)
are available in the Git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/tip/tip.git tags/x86_cpu_for_v5.17_rc1
for you to fetch changes up to 244122b4d2e5221e6abd6e21d6a58170104db781:
x86/lib: Add fast-short-rep-movs check to copy_user_enhanced_fast_string() (2021-12-29 13:46:02 +0100)
----------------------------------------------------------------
- Enable the short string copies for CPUs which support them, in
copy_user_enhanced_fast_string()
- Avoid writing MSR_CSTAR on Intel due to TDX guests raising a #VE trap
----------------------------------------------------------------
Andi Kleen (1):
x86/cpu: Don't write CSTAR MSR on Intel CPUs
Tony Luck (1):
x86/lib: Add fast-short-rep-movs check to copy_user_enhanced_fast_string()
arch/x86/kernel/cpu/common.c | 15 +++++++++++++--
arch/x86/lib/copy_user_64.S | 4 ++--
2 files changed, 15 insertions(+), 4 deletions(-)
--
Regards/Gruss,
Boris.
SUSE Software Solutions Germany GmbH, GF: Ivo Totev, HRB 36809, AG Nürnberg
next reply other threads:[~2022-01-10 11:16 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-10 11:16 Borislav Petkov [this message]
2022-01-10 18:18 ` [GIT PULL] x86/cpu for v5.17 Linus Torvalds
2022-01-10 18:35 ` Borislav Petkov
2022-01-10 19:32 ` Linus Torvalds
2022-01-10 20:10 ` Dave Hansen
2022-01-10 20:15 ` Linus Torvalds
2022-01-11 22:48 ` Sean Christopherson
2022-01-10 18:27 ` 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=YdwVl0H54fmUIux0@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;
as well as URLs for NNTP newsgroup(s).