From: Marcelo Tosatti <mtosatti@redhat.com> To: kvm@vger.kernel.org Cc: Paolo Bonzini <pbonzini@redhat.com>, Alex Williamson <alex.williamson@redhat.com>, Sean Christopherson <seanjc@google.com>, Marcelo Tosatti <mtosatti@redhat.com> Subject: [patch 2/4] KVM: add arch specific vcpu_check_block callback Date: Fri, 07 May 2021 10:06:11 -0300 [thread overview] Message-ID: <20210507130923.468254904@redhat.com> (raw) In-Reply-To: <20210507130609.269153197@redhat.com> Add callback in kvm_vcpu_check_block, so that architectures can direct a vcpu to exit the vcpu block loop without requiring events that would unhalt it. Signed-off-by: Marcelo Tosatti <mtosatti@redhat.com> Index: kvm/include/linux/kvm_host.h =================================================================== --- kvm.orig/include/linux/kvm_host.h +++ kvm/include/linux/kvm_host.h @@ -971,6 +971,13 @@ static inline int kvm_arch_flush_remote_ } #endif +#ifndef __KVM_HAVE_ARCH_VCPU_CHECK_BLOCK +static inline int kvm_arch_vcpu_check_block(struct kvm_vcpu *vcpu) +{ + return 0; +} +#endif + #ifdef __KVM_HAVE_ARCH_NONCOHERENT_DMA void kvm_arch_register_noncoherent_dma(struct kvm *kvm); void kvm_arch_unregister_noncoherent_dma(struct kvm *kvm); Index: kvm/virt/kvm/kvm_main.c =================================================================== --- kvm.orig/virt/kvm/kvm_main.c +++ kvm/virt/kvm/kvm_main.c @@ -2794,6 +2794,8 @@ static int kvm_vcpu_check_block(struct k goto out; if (signal_pending(current)) goto out; + if (kvm_arch_vcpu_check_block(vcpu)) + goto out; ret = 0; out:
next prev parent reply other threads:[~2021-05-07 13:10 UTC|newest] Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top 2021-05-07 13:06 [patch 0/4] VMX: configure posted interrupt descriptor when assigning device Marcelo Tosatti 2021-05-07 13:06 ` [patch 1/4] KVM: x86: add start_assignment hook to kvm_x86_ops Marcelo Tosatti 2021-05-07 19:16 ` Peter Xu 2021-05-10 17:53 ` Marcelo Tosatti 2021-05-07 13:06 ` Marcelo Tosatti [this message] 2021-05-07 13:06 ` [patch 3/4] KVM: x86: implement kvm_arch_vcpu_check_block callback Marcelo Tosatti 2021-05-07 13:06 ` [patch 4/4] KVM: VMX: update vcpu posted-interrupt descriptor when assigning device Marcelo Tosatti 2021-05-07 17:22 ` Sean Christopherson 2021-05-07 19:29 ` Peter Xu 2021-05-07 22:08 ` Marcelo Tosatti 2021-05-11 14:39 ` Peter Xu 2021-05-11 14:51 ` Marcelo Tosatti 2021-05-11 16:19 ` Peter Xu 2021-05-11 17:18 ` Marcelo Tosatti 2021-05-11 21:35 ` Peter Xu 2021-05-11 23:51 ` Marcelo Tosatti 2021-05-12 0:02 ` Marcelo Tosatti 2021-05-12 0:38 ` Peter Xu 2021-05-12 11:10 ` Marcelo Tosatti 2021-05-12 14:41 ` Sean Christopherson 2021-05-12 15:34 ` Peter Xu 2021-05-10 17:26 [patch 0/4] VMX: configure posted interrupt descriptor when assigning device (v3) Marcelo Tosatti 2021-05-10 17:26 ` [patch 2/4] KVM: add arch specific vcpu_check_block callback Marcelo Tosatti 2021-05-11 23:57 [patch 0/4] VMX: configure posted interrupt descriptor when assigning device (v4) Marcelo Tosatti 2021-05-11 23:57 ` [patch 2/4] KVM: add arch specific vcpu_check_block callback Marcelo Tosatti
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=20210507130923.468254904@redhat.com \ --to=mtosatti@redhat.com \ --cc=alex.williamson@redhat.com \ --cc=kvm@vger.kernel.org \ --cc=pbonzini@redhat.com \ --cc=seanjc@google.com \ --subject='Re: [patch 2/4] KVM: add arch specific vcpu_check_block callback' \ /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
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).