From: Sean Christopherson <seanjc@google.com>
To: Borislav Petkov <bp@alien8.de>
Cc: Paolo Bonzini <pbonzini@redhat.com>,
Thomas Gleixner <tglx@linutronix.de>,
Peter Zijlstra <peterz@infradead.org>,
Josh Poimboeuf <jpoimboe@kernel.org>,
kvm@vger.kernel.org, linux-kernel@vger.kernel.org,
Pawan Gupta <pawan.kumar.gupta@linux.intel.com>,
Brendan Jackman <jackmanb@google.com>
Subject: Re: [PATCH v5 3/9] x86/bugs: Decouple ALTERNATIVE usage from VERW macro definition
Date: Mon, 17 Nov 2025 07:33:12 -0800 [thread overview]
Message-ID: <aRtAOM040vM9RGfK@google.com> (raw)
In-Reply-To: <20251117101129.GGaRr00XgEln3XzR5N@fat_crate.local>
On Mon, Nov 17, 2025, Borislav Petkov wrote:
> On Thu, Nov 13, 2025 at 03:37:40PM -0800, Sean Christopherson wrote:
> > +#define __CLEAR_CPU_BUFFERS __stringify(VERW)
>
> Let's get rid of one indirection level pls:
>
> diff --git a/arch/x86/include/asm/nospec-branch.h b/arch/x86/include/asm/nospec-branch.h
> index 8b4885a1b2ef..59945cb5e5f9 100644
> --- a/arch/x86/include/asm/nospec-branch.h
> +++ b/arch/x86/include/asm/nospec-branch.h
> @@ -309,23 +309,21 @@
> * Note: Only the memory operand variant of VERW clears the CPU buffers.
> */
> #ifdef CONFIG_X86_64
> -#define VERW verw x86_verw_sel(%rip)
> +#define VERW __stringify(verw x86_verw_sel(%rip))
> #else
> /*
> * In 32bit mode, the memory operand must be a %cs reference. The data segments
> * may not be usable (vm86 mode), and the stack segment may not be flat (ESPFIX32).
> */
> -#define VERW verw %cs:x86_verw_sel
> +#define VERW __stringify(verw %cs:x86_verw_sel)
> #endif
Brendan also brought this up in v4[*]. Unless there's a way to coerce ALTERNATIVE_2
into working with multiple strings, the layer of indirection is needed so that KVM
can emit __stringify() for the entire sequence.
: Heh, I tried that, and AFAICT it simply can't work with the way ALTERNATIVE and
: friends are implemented, as each paramater needs to be a single unbroken string.
:
: E.g. this
:
: diff --git a/arch/x86/kvm/vmx/vmenter.S b/arch/x86/kvm/vmx/vmenter.S
: index 61a809790a58..ffa6bc2345e3 100644
: --- a/arch/x86/kvm/vmx/vmenter.S
: +++ b/arch/x86/kvm/vmx/vmenter.S
: @@ -63,6 +63,8 @@
: RET
: .endm
:
: +#define CLEAR_CPU_BUFFERS_SEQ_STRING "verw x86_verw_sel(%rip)"
: +
: .section .noinstr.text, "ax"
:
: /**
: @@ -169,9 +171,9 @@ SYM_FUNC_START(__vmx_vcpu_run)
:
: /* Clobbers EFLAGS.ZF */
: ALTERNATIVE_2 "", \
: - __stringify(jz .Lskip_clear_cpu_buffers; \
: - CLEAR_CPU_BUFFERS_SEQ; \
: - .Lskip_clear_cpu_buffers:), \
: + "jz .Lskip_clear_cpu_buffers; " \
: + CLEAR_CPU_BUFFERS_SEQ_STRING; \
: + ".Lskip_clear_cpu_buffers:", \
: X86_FEATURE_CLEAR_CPU_BUF_MMIO, \
: __CLEAR_CPU_BUFFERS, X86_FEATURE_CLEAR_CPU_BUF_VM
:
: yields wonderfully helpful error messages like so:
:
: arch/x86/kvm/vmx/vmenter.S: Assembler messages:
: arch/x86/kvm/vmx/vmenter.S:173: Error: too many positional arguments
:
: If there's a magic incanation to get things to work, it's unknown to me.
[*] https://lore.kernel.org/all/aQT1JgdgiNae3Ybl@google.com
next prev parent reply other threads:[~2025-11-17 15:33 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-11-13 23:37 [PATCH v5 0/9] x86/bugs: KVM: L1TF and MMIO Stale Data cleanups Sean Christopherson
2025-11-13 23:37 ` [PATCH v5 1/9] KVM: VMX: Use on-stack copy of @flags in __vmx_vcpu_run() Sean Christopherson
2025-11-14 12:36 ` Brendan Jackman
2025-11-14 15:06 ` Uros Bizjak
2025-11-19 0:29 ` Sean Christopherson
2025-11-14 16:40 ` Borislav Petkov
2025-11-13 23:37 ` [PATCH v5 2/9] x86/bugs: Use VM_CLEAR_CPU_BUFFERS in VMX as well Sean Christopherson
2025-11-14 12:40 ` Brendan Jackman
2025-11-13 23:37 ` [PATCH v5 3/9] x86/bugs: Decouple ALTERNATIVE usage from VERW macro definition Sean Christopherson
2025-11-17 10:11 ` Borislav Petkov
2025-11-17 15:33 ` Sean Christopherson [this message]
2025-11-18 10:32 ` Borislav Petkov
2025-11-13 23:37 ` [PATCH v5 4/9] x86/bugs: Use an x86 feature to track the MMIO Stale Data mitigation Sean Christopherson
2025-11-13 23:37 ` [PATCH v5 5/9] KVM: VMX: Handle MMIO Stale Data in VM-Enter assembly via ALTERNATIVES_2 Sean Christopherson
2025-11-14 12:55 ` Brendan Jackman
2025-11-13 23:37 ` [PATCH v5 6/9] x86/bugs: KVM: Move VM_CLEAR_CPU_BUFFERS into SVM as SVM_CLEAR_CPU_BUFFERS Sean Christopherson
2025-11-13 23:37 ` [PATCH v5 7/9] KVM: VMX: Bundle all L1 data cache flush mitigation code together Sean Christopherson
2025-11-13 23:37 ` [PATCH v5 8/9] KVM: VMX: Disable L1TF L1 data cache flush if CONFIG_CPU_MITIGATIONS=n Sean Christopherson
2025-11-13 23:37 ` [PATCH v5 9/9] KVM: x86: Unify L1TF flushing under per-CPU variable Sean Christopherson
2025-11-21 18:55 ` [PATCH v5 0/9] x86/bugs: KVM: L1TF and MMIO Stale Data cleanups Sean Christopherson
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=aRtAOM040vM9RGfK@google.com \
--to=seanjc@google.com \
--cc=bp@alien8.de \
--cc=jackmanb@google.com \
--cc=jpoimboe@kernel.org \
--cc=kvm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=pawan.kumar.gupta@linux.intel.com \
--cc=pbonzini@redhat.com \
--cc=peterz@infradead.org \
--cc=tglx@linutronix.de \
/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