From: Paolo Bonzini <pbonzini@redhat.com>
To: Wanpeng Li <kernellwp@gmail.com>,
linux-kernel@vger.kernel.org, kvm@vger.kernel.org
Cc: "Radim Krčmář" <rkrcmar@redhat.com>,
"Sean Christopherson" <sean.j.christopherson@intel.com>,
"Vitaly Kuznetsov" <vkuznets@redhat.com>,
"Wanpeng Li" <wanpengli@tencent.com>,
"Jim Mattson" <jmattson@google.com>,
"Joerg Roedel" <joro@8bytes.org>
Subject: Re: [PATCH 1/2] KVM: X86: Single target IPI fastpath
Date: Thu, 14 Nov 2019 12:58:56 +0100 [thread overview]
Message-ID: <6c2c7bbb-39f4-2a77-632e-7730e9887fc5@redhat.com> (raw)
In-Reply-To: <1573283135-5502-1-git-send-email-wanpengli@tencent.com>
Ok, it's not _so_ ugly after all.
> ---
> arch/x86/kvm/vmx/vmx.c | 39 +++++++++++++++++++++++++++++++++++++--
> include/linux/kvm_host.h | 1 +
> 2 files changed, 38 insertions(+), 2 deletions(-)
>
> diff --git a/arch/x86/kvm/vmx/vmx.c b/arch/x86/kvm/vmx/vmx.c
> index 5d21a4a..5c67061 100644
> --- a/arch/x86/kvm/vmx/vmx.c
> +++ b/arch/x86/kvm/vmx/vmx.c
> @@ -5924,7 +5924,9 @@ static int vmx_handle_exit(struct kvm_vcpu *vcpu)
> }
> }
>
> - if (exit_reason < kvm_vmx_max_exit_handlers
> + if (vcpu->fast_vmexit)
> + return 1;
> + else if (exit_reason < kvm_vmx_max_exit_handlers
Instead of a separate vcpu->fast_vmexit, perhaps you can set exit_reason
to vmx->exit_reason to -1 if the fast path succeeds.
> + if (ret == 0)
> + ret = kvm_skip_emulated_instruction(vcpu);
Please move the "kvm_skip_emulated_instruction(vcpu)" to
vmx_handle_exit, so that this basically is
#define EXIT_REASON_NEED_SKIP_EMULATED_INSN -1
if (ret == 0)
vcpu->exit_reason = EXIT_REASON_NEED_SKIP_EMULATED_INSN;
and handle_ipi_fastpath can return void.
Thanks,
Paolo
> + };
> + };
> +
> + return ret;
> +}
> +
> static void vmx_vcpu_run(struct kvm_vcpu *vcpu)
> {
> struct vcpu_vmx *vmx = to_vmx(vcpu);
> @@ -6615,6 +6645,12 @@ static void vmx_vcpu_run(struct kvm_vcpu *vcpu)
> | (1 << VCPU_EXREG_CR3));
> vcpu->arch.regs_dirty = 0;
>
> + vmx->exit_reason = vmx->fail ? 0xdead : vmcs_read32(VM_EXIT_REASON);
> + vcpu->fast_vmexit = false;
> + if (!is_guest_mode(vcpu) &&
> + vmx->exit_reason == EXIT_REASON_MSR_WRITE)
> + vcpu->fast_vmexit = handle_ipi_fastpath(vcpu);
This should be done later, at least after kvm_put_guest_xcr0, because
running with partially-loaded guest state is harder to audit. The best
place to put it actually is right after the existing vmx->exit_reason
assignment, where we already handle EXIT_REASON_MCE_DURING_VMENTRY.
> pt_guest_exit(vmx);
>
> /*
> @@ -6634,7 +6670,6 @@ static void vmx_vcpu_run(struct kvm_vcpu *vcpu)
> vmx->nested.nested_run_pending = 0;
> vmx->idt_vectoring_info = 0;
>
> - vmx->exit_reason = vmx->fail ? 0xdead : vmcs_read32(VM_EXIT_REASON);
> if ((u16)vmx->exit_reason == EXIT_REASON_MCE_DURING_VMENTRY)
> kvm_machine_check();
>
> diff --git a/include/linux/kvm_host.h b/include/linux/kvm_host.h
> index 719fc3e..7a7358b 100644
> --- a/include/linux/kvm_host.h
> +++ b/include/linux/kvm_host.h
> @@ -319,6 +319,7 @@ struct kvm_vcpu {
> #endif
> bool preempted;
> bool ready;
> + bool fast_vmexit;
> struct kvm_vcpu_arch arch;
> struct dentry *debugfs_dentry;
> };
>
next prev parent reply other threads:[~2019-11-14 11:59 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-11-09 7:05 Wanpeng Li
2019-11-09 7:05 ` [PATCH 2/2] KVM: LAPIC: micro-optimize fixed mode ipi delivery Wanpeng Li
2019-11-11 21:59 ` Paolo Bonzini
2019-11-12 1:34 ` Wanpeng Li
2019-11-10 1:59 ` [PATCH 1/2] KVM: X86: Single target IPI fastpath kbuild test robot
2019-11-10 1:59 ` [PATCH] KVM: X86: fix semicolon.cocci warnings kbuild test robot
2019-11-11 13:06 ` [PATCH 1/2] KVM: X86: Single target IPI fastpath Vitaly Kuznetsov
2019-11-12 1:18 ` Wanpeng Li
2019-11-11 21:59 ` Paolo Bonzini
2019-11-12 1:33 ` Wanpeng Li
2019-11-13 6:05 ` Wanpeng Li
2019-11-14 3:12 ` Wanpeng Li
2019-11-14 11:58 ` Paolo Bonzini [this message]
2019-11-14 15:22 ` Sean Christopherson
2019-11-14 15:44 ` Paolo Bonzini
2019-11-14 16:34 ` Sean Christopherson
2019-11-15 5:56 ` Wanpeng Li
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=6c2c7bbb-39f4-2a77-632e-7730e9887fc5@redhat.com \
--to=pbonzini@redhat.com \
--cc=jmattson@google.com \
--cc=joro@8bytes.org \
--cc=kernellwp@gmail.com \
--cc=kvm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=rkrcmar@redhat.com \
--cc=sean.j.christopherson@intel.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
all inboxes | Powered by JetHome®