From: Greg KH <gregkh@linuxfoundation.org>
To: Nikolay Borisov <nik.borisov@suse.com>
Cc: stable@vger.kernel.org
Subject: Re: [PATCH 0/7] 5.4 backport of recent mds improvement patches
Date: Mon, 26 Feb 2024 11:36:03 +0100 [thread overview]
Message-ID: <2024022641-nearest-engraving-ed9c@gregkh> (raw)
In-Reply-To: <20240226101239.17633-1-nik.borisov@suse.com>
On Mon, Feb 26, 2024 at 12:12:32PM +0200, Nikolay Borisov wrote:
> Here's the recently merged mds improvement patches adapted to latest stable tree.
> I've only compile tested them, but since I have also done similar backports for
> older kernels I'm sure they should work.
> The main difference is in the definition of the CLEAR_CPU_BUFFERS macro since
> 5.4 doesn't contains the alternative relocation handling logic hence the verw
> instruction is moved out of the alternative definition and instead we have a jump which
> skips the verw instruction there. That way the relocation will be handled by the
> toolchain rather than the kernel.
>
> H. Peter Anvin (Intel) (1):
> x86/asm: Add _ASM_RIP() macro for x86-64 (%rip) suffix
>
> Pawan Gupta (5):
> x86/bugs: Add asm helpers for executing VERW
> x86/entry_64: Add VERW just before userspace transition
> x86/entry_32: Add VERW just before userspace transition
> x86/bugs: Use ALTERNATIVE() instead of mds_user_clear static key
> KVM/VMX: Move VERW closer to VMentry for MDS mitigation
>
> Sean Christopherson (1):
> KVM/VMX: Use BT+JNC, i.e. EFLAGS.CF to select VMRESUME vs. VMLAUNCH
>
> Documentation/x86/mds.rst | 38 ++++++++++++++++++++--------
> arch/x86/entry/Makefile | 2 +-
> arch/x86/entry/common.c | 2 --
> arch/x86/entry/entry.S | 23 +++++++++++++++++
> arch/x86/entry/entry_32.S | 3 +++
> arch/x86/entry/entry_64.S | 10 ++++++++
> arch/x86/entry/entry_64_compat.S | 1 +
> arch/x86/include/asm/asm.h | 6 ++++-
> arch/x86/include/asm/cpufeatures.h | 2 +-
> arch/x86/include/asm/irqflags.h | 1 +
> arch/x86/include/asm/nospec-branch.h | 26 ++++++++++---------
> arch/x86/kernel/cpu/bugs.c | 15 +++++------
> arch/x86/kernel/nmi.c | 3 ---
> arch/x86/kvm/vmx/run_flags.h | 7 +++--
> arch/x86/kvm/vmx/vmenter.S | 9 ++++---
> arch/x86/kvm/vmx/vmx.c | 12 ++++++---
> 16 files changed, 111 insertions(+), 49 deletions(-)
> create mode 100644 arch/x86/entry/entry.S
I don't see the git commit id in any of these patches, can you fix that
up and resend them?
thanks,
greg k-h
prev parent reply other threads:[~2024-02-26 10:36 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-02-26 10:12 [PATCH 0/7] 5.4 backport of recent mds improvement patches Nikolay Borisov
2024-02-26 10:12 ` [PATCH 1/7] x86/asm: Add _ASM_RIP() macro for x86-64 (%rip) suffix Nikolay Borisov
2024-02-26 10:12 ` [PATCH 2/7] x86/bugs: Add asm helpers for executing VERW Nikolay Borisov
2024-02-26 10:12 ` [PATCH 3/7] x86/entry_64: Add VERW just before userspace transition Nikolay Borisov
2024-02-26 10:12 ` [PATCH 4/7] x86/entry_32: " Nikolay Borisov
2024-02-26 10:12 ` [PATCH 5/7] x86/bugs: Use ALTERNATIVE() instead of mds_user_clear static key Nikolay Borisov
2024-02-26 10:12 ` [PATCH 6/7] KVM/VMX: Use BT+JNC, i.e. EFLAGS.CF to select VMRESUME vs. VMLAUNCH Nikolay Borisov
2024-02-26 10:12 ` [PATCH 7/7] KVM/VMX: Move VERW closer to VMentry for MDS mitigation Nikolay Borisov
2024-02-26 10:36 ` Greg KH [this message]
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=2024022641-nearest-engraving-ed9c@gregkh \
--to=gregkh@linuxfoundation.org \
--cc=nik.borisov@suse.com \
--cc=stable@vger.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.