From: Josh Poimboeuf <jpoimboe@redhat.com>
To: Sean Christopherson <sean.j.christopherson@intel.com>
Cc: Paolo Bonzini <pbonzini@redhat.com>,
Vitaly Kuznetsov <vkuznets@redhat.com>,
Wanpeng Li <wanpengli@tencent.com>,
Jim Mattson <jmattson@google.com>, Joerg Roedel <joro@8bytes.org>,
kvm@vger.kernel.org, linux-kernel@vger.kernel.org,
Uros Bizjak <ubizjak@gmail.com>, Andi Kleen <ak@linux.intel.com>
Subject: Re: [PATCH 1/2] KVM: VMX: Move IRQ invocation to assembly subroutine
Date: Mon, 14 Sep 2020 15:40:24 -0500 [thread overview]
Message-ID: <20200914204024.w3rpjon64d3fesys@treble> (raw)
In-Reply-To: <20200914195634.12881-2-sean.j.christopherson@intel.com>
On Mon, Sep 14, 2020 at 12:56:33PM -0700, Sean Christopherson wrote:
> Move the asm blob that invokes the appropriate IRQ handler after VM-Exit
> into a proper subroutine. Slightly rework the blob so that it plays
> nice with objtool without any additional hints (existing hints aren't
> able to handle returning with a seemingly modified stack size).
>
> Suggested-by: Josh Poimboeuf <jpoimboe@redhat.com>
> Cc: Uros Bizjak <ubizjak@gmail.com>
> Signed-off-by: Sean Christopherson <sean.j.christopherson@intel.com>
> ---
> arch/x86/kvm/vmx/vmenter.S | 28 ++++++++++++++++++++++++++++
> arch/x86/kvm/vmx/vmx.c | 33 +++------------------------------
> 2 files changed, 31 insertions(+), 30 deletions(-)
>
> diff --git a/arch/x86/kvm/vmx/vmenter.S b/arch/x86/kvm/vmx/vmenter.S
> index 799db084a336..baec1e0fefc5 100644
> --- a/arch/x86/kvm/vmx/vmenter.S
> +++ b/arch/x86/kvm/vmx/vmenter.S
> @@ -4,6 +4,7 @@
> #include <asm/bitsperlong.h>
> #include <asm/kvm_vcpu_regs.h>
> #include <asm/nospec-branch.h>
> +#include <asm/segment.h>
>
> #define WORD_SIZE (BITS_PER_LONG / 8)
>
> @@ -294,3 +295,30 @@ SYM_FUNC_START(vmread_error_trampoline)
>
> ret
> SYM_FUNC_END(vmread_error_trampoline)
> +
> +SYM_FUNC_START(vmx_do_interrupt_nmi_irqoff)
> + /*
> + * Unconditionally create a stack frame. RSP needs to be aligned for
> + * x86-64, getting the correct RSP on the stack (for x86-64) would take
> + * two instructions anyways, and it helps make objtool happy (see below).
> + */
> + push %_ASM_BP
> + mov %rsp, %_ASM_BP
RSP needs to be aligned to what? How would this align the stack, other
than by accident?
> +
> +#ifdef CONFIG_X86_64
> + push $__KERNEL_DS
> + push %_ASM_BP
> +#endif
> + pushf
> + push $__KERNEL_CS
> + CALL_NOSPEC _ASM_ARG1
> +
> + /*
> + * "Restore" RSP from RBP, even though IRET has already unwound RSP to
> + * the correct value. objtool doesn't know the target will IRET and so
> + * thinks the stack is getting walloped (without the explicit restore).
> + */
> + mov %_ASM_BP, %rsp
> + pop %_ASM_BP
> + ret
BTW, there *is* actually an unwind hint for this situation:
UNWIND_HINT_RET_OFFSET.
So you might be able to do something like the following (depending on
what your alignment requirements actually are):
SYM_FUNC_START(vmx_do_interrupt_nmi_irqoff)
#ifdef CONFIG_X86_64
push $__KERNEL_DS
push %_ASM_BP
#endif
pushf
push $__KERNEL_CS
CALL_NOSPEC _ASM_ARG1
/* The call popped the pushes */
UNWIND_HINT_RET_OFFSET sp_offset=32
ret
SYM_FUNC_END(vmx_do_interrupt_nmi_irqoff)
--
Josh
next prev parent reply other threads:[~2020-09-14 20:40 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-09-14 19:56 [PATCH 0/2] KVM: VMX: Clean up IRQ/NMI handling Sean Christopherson
2020-09-14 19:56 ` [PATCH 2/2] KVM: VMX: Invoke NMI handler via indirect call instead of INTn Sean Christopherson
[not found] ` <20200914195634.12881-2-sean.j.christopherson@intel.com>
2020-09-14 20:37 ` [PATCH 1/2] KVM: VMX: Move IRQ invocation to assembly subroutine Uros Bizjak
2020-09-14 21:08 ` Sean Christopherson
2020-09-14 20:40 ` Josh Poimboeuf [this message]
[not found] ` <20200914210719.GB7084@sjchrist-ice>
2020-09-14 21:21 ` Uros Bizjak
2020-09-14 21:31 ` Uros Bizjak
2020-09-14 21:55 ` Sean Christopherson
2020-09-14 21:38 ` Josh Poimboeuf
2020-09-14 21:54 ` Sean Christopherson
2020-09-15 2:42 ` Andi Kleen
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=20200914204024.w3rpjon64d3fesys@treble \
--to=jpoimboe@redhat.com \
--cc=ak@linux.intel.com \
--cc=jmattson@google.com \
--cc=joro@8bytes.org \
--cc=kvm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=pbonzini@redhat.com \
--cc=sean.j.christopherson@intel.com \
--cc=ubizjak@gmail.com \
--cc=vkuznets@redhat.com \
--cc=wanpengli@tencent.com \
/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