* [GIT PULL] x86/cpu for v5.16
@ 2021-11-01 10:29 Borislav Petkov
2021-11-01 22:44 ` Linus Torvalds
2021-11-01 23:10 ` pr-tracker-bot
0 siblings, 2 replies; 4+ messages in thread
From: Borislav Petkov @ 2021-11-01 10:29 UTC (permalink / raw)
To: Linus Torvalds; +Cc: x86-ml, lkml
Hi Linus,
please pull x86/cpu updates for v5.16.
Thx.
---
The following changes since commit 6880fa6c56601bb8ed59df6c30fd390cc5f6dd8f:
Linux 5.15-rc1 (2021-09-12 16:28:37 -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.16_rc1
for you to fetch changes up to 415de44076640483648d6c0f6d645a9ee61328ad:
x86/cpu: Fix migration safety with X86_BUG_NULL_SEL (2021-10-21 20:49:16 +0200)
----------------------------------------------------------------
- Start checking a CPUID bit on AMD Zen3 which states that the CPU
clears the segment base when a null selector is written. Do the explicit
detection on older CPUs, zen2 and hygon specifically, which have the
functionality but do not advertize the CPUID bit. Factor in the presence
of a hypervisor underneath the kernel and avoid doing the explicit check
there which the HV might've decided to not advertize for migration
safety reasons, a.o.
- Add support for a new X86 CPU vendor: VORTEX. Needed for whitelisting
those CPUs in the hardware vulnerabilities detection
- Force the compiler to use rIP-relative addressing in the fallback path of
static_cpu_has(), in order to avoid unnecessary register pressure
----------------------------------------------------------------
Borislav Petkov (1):
x86/umip: Downgrade warning messages to debug loglevel
H. Peter Anvin (1):
x86/asm: Avoid adding register pressure for the init case in static_cpu_has()
H. Peter Anvin (Intel) (1):
x86/asm: Add _ASM_RIP() macro for x86-64 (%rip) suffix
Jane Malalane (1):
x86/cpu: Fix migration safety with X86_BUG_NULL_SEL
Marcos Del Sol Vives (1):
x86/CPU: Add support for Vortex CPUs
arch/x86/Kconfig.cpu | 13 +++++++++++
arch/x86/include/asm/asm.h | 5 +++++
arch/x86/include/asm/cpufeature.h | 13 +++++++----
arch/x86/include/asm/processor.h | 3 ++-
arch/x86/kernel/cpu/Makefile | 1 +
arch/x86/kernel/cpu/amd.c | 2 ++
arch/x86/kernel/cpu/common.c | 46 +++++++++++++++++++++++++++++++++------
arch/x86/kernel/cpu/cpu.h | 1 +
arch/x86/kernel/cpu/hygon.c | 2 ++
arch/x86/kernel/cpu/vortex.c | 39 +++++++++++++++++++++++++++++++++
arch/x86/kernel/umip.c | 8 +++----
11 files changed, 117 insertions(+), 16 deletions(-)
create mode 100644 arch/x86/kernel/cpu/vortex.c
--
Regards/Gruss,
Boris.
SUSE Software Solutions Germany GmbH, GF: Ivo Totev, HRB 36809, AG Nürnberg
^ permalink raw reply [flat|nested] 4+ messages in thread
* Re: [GIT PULL] x86/cpu for v5.16
2021-11-01 10:29 [GIT PULL] x86/cpu for v5.16 Borislav Petkov
@ 2021-11-01 22:44 ` Linus Torvalds
2021-11-02 5:42 ` Borislav Petkov
2021-11-01 23:10 ` pr-tracker-bot
1 sibling, 1 reply; 4+ messages in thread
From: Linus Torvalds @ 2021-11-01 22:44 UTC (permalink / raw)
To: Borislav Petkov; +Cc: x86-ml, lkml
On Mon, Nov 1, 2021 at 3:29 AM Borislav Petkov <bp@suse.de> wrote:
>
> - Start checking a CPUID bit on AMD Zen3 which states that the CPU
> clears the segment base when a null selector is written. Do the explicit
> detection on older CPUs, zen2 and hygon specifically, which have the
> functionality but do not advertize the CPUID bit. Factor in the presence
> of a hypervisor underneath the kernel and avoid doing the explicit check
> there which the HV might've decided to not advertize for migration
> safety reasons, a.o.
"a.o."? Is that a common German shorthand, possibly anglicized?
I'm assuming - and rewrote it - that it stands for "or similar".
Possibly "among other" aka "inter alia"? Very occasionally shortened
"i.a.", although "e.g." is the _much_ more common form of much the
same thing.
Never seen that "a.o." thing.
Linus
^ permalink raw reply [flat|nested] 4+ messages in thread
* Re: [GIT PULL] x86/cpu for v5.16
2021-11-01 10:29 [GIT PULL] x86/cpu for v5.16 Borislav Petkov
2021-11-01 22:44 ` Linus Torvalds
@ 2021-11-01 23:10 ` pr-tracker-bot
1 sibling, 0 replies; 4+ messages in thread
From: pr-tracker-bot @ 2021-11-01 23:10 UTC (permalink / raw)
To: Borislav Petkov; +Cc: Linus Torvalds, x86-ml, lkml
The pull request you sent on Mon, 1 Nov 2021 11:29:24 +0100:
> git://git.kernel.org/pub/scm/linux/kernel/git/tip/tip.git tags/x86_cpu_for_v5.16_rc1
has been merged into torvalds/linux.git:
https://git.kernel.org/torvalds/c/e0f4c59dc4d39b3e9fa61ceb4cf2384787bcd09d
Thank you!
--
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/prtracker.html
^ permalink raw reply [flat|nested] 4+ messages in thread
* Re: [GIT PULL] x86/cpu for v5.16
2021-11-01 22:44 ` Linus Torvalds
@ 2021-11-02 5:42 ` Borislav Petkov
0 siblings, 0 replies; 4+ messages in thread
From: Borislav Petkov @ 2021-11-02 5:42 UTC (permalink / raw)
To: Linus Torvalds; +Cc: x86-ml, lkml
On Mon, Nov 01, 2021 at 03:44:46PM -0700, Linus Torvalds wrote:
> "a.o."? Is that a common German shorthand, possibly anglicized?
Haha, exactly. :-)
> I'm assuming - and rewrote it - that it stands for "or similar".
Apparently, the "proper" thing to write is https://en.wiktionary.org/wiki/i.a.
> Possibly "among other" aka "inter alia"? Very occasionally shortened
> "i.a.", although "e.g." is the _much_ more common form of much the
> same thing.
Yeah, I saw "e.g." being suggested also for "among others".
> Never seen that "a.o." thing.
Sorry about that - I'll make sure to avoid such misguided abbreviations
in the future. We have enough confusion as it is - no reason for me to
add more.
--
Regards/Gruss,
Boris.
SUSE Software Solutions Germany GmbH, GF: Ivo Totev, HRB 36809, AG Nürnberg
^ permalink raw reply [flat|nested] 4+ messages in thread
end of thread, other threads:[~2021-11-02 5:42 UTC | newest]
Thread overview: 4+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2021-11-01 10:29 [GIT PULL] x86/cpu for v5.16 Borislav Petkov
2021-11-01 22:44 ` Linus Torvalds
2021-11-02 5:42 ` Borislav Petkov
2021-11-01 23:10 ` pr-tracker-bot
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).