From: Paolo Bonzini <pbonzini@redhat.com>
To: linux-kernel@vger.kernel.org, kvm@vger.kernel.org
Cc: seanjc@google.com
Subject: [PATCH v3 0/6] kvm: x86: better handling of optional kvm_x86_ops
Date: Thu, 17 Feb 2022 13:08:25 -0500 [thread overview]
Message-ID: <20220217180831.288210-1-pbonzini@redhat.com> (raw)
This series is really two changes:
- patch 1 remove a kvm_x86_ops callback.
- patch 2 to 5 clean up optional kvm_x86_ops so that they are marked
in kvm-x86-ops.h and the non-optional ones WARN if used incorrectly.
As an additional outcome of the review, a few more uses of
static_call_cond are introduced.
- patch 6 allows to NULL a few kvm_x86_ops that return a value, by
using __static_call_ret0.
v1->v2:
- use KVM_X86_OP_OPTIONAL and KVM_X86_OP_OPTIONAL_RET0
- mark load_eoi_exitmap and set_virtual_apic_mode as optional
- fix module compilation of KVM
v2->v3:
- new patch 1 to remove .has_accelerated_tpr
- do not expand KVM_X86_OP_OPTIONAL in KVM_X86_OP
- cosmetic changes to comments
Paolo Bonzini (6):
KVM: x86: return 1 unconditionally for availability of KVM_CAP_VAPIC
KVM: x86: use static_call_cond for optional callbacks
KVM: x86: remove KVM_X86_OP_NULL and mark optional kvm_x86_ops
KVM: x86: warn on incorrectly NULL members of kvm_x86_ops
KVM: x86: make several AVIC callbacks optional
KVM: x86: allow defining return-0 static calls
arch/x86/include/asm/kvm-x86-ops.h | 104 +++++++++++++++--------------
arch/x86/include/asm/kvm_host.h | 14 ++--
arch/x86/kvm/lapic.c | 24 +++----
arch/x86/kvm/svm/avic.c | 23 -------
arch/x86/kvm/svm/svm.c | 30 ---------
arch/x86/kvm/svm/svm.h | 1 -
arch/x86/kvm/vmx/vmx.c | 6 --
arch/x86/kvm/x86.c | 20 ++----
kernel/static_call.c | 1 +
9 files changed, 81 insertions(+), 142 deletions(-)
--
2.31.1
next reply other threads:[~2022-02-17 18:08 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-02-17 18:08 Paolo Bonzini [this message]
2022-02-17 18:08 ` [PATCH v3 1/6] KVM: x86: return 1 unconditionally for availability of KVM_CAP_VAPIC Paolo Bonzini
2022-02-18 15:44 ` Sean Christopherson
2022-02-23 13:21 ` Maxim Levitsky
2022-02-17 18:08 ` [PATCH v3 2/6] KVM: x86: use static_call_cond for optional callbacks Paolo Bonzini
2022-02-18 15:46 ` Sean Christopherson
2022-02-17 18:08 ` [PATCH v3 3/6] KVM: x86: remove KVM_X86_OP_NULL and mark optional kvm_x86_ops Paolo Bonzini
2022-02-18 15:52 ` Sean Christopherson
2022-02-17 18:08 ` [PATCH v3 4/6] KVM: x86: warn on incorrectly NULL members of kvm_x86_ops Paolo Bonzini
2022-02-18 16:18 ` Sean Christopherson
2022-02-17 18:08 ` [PATCH v3 5/6] KVM: x86: make several AVIC callbacks optional Paolo Bonzini
2022-02-18 16:23 ` Sean Christopherson
2022-02-18 17:17 ` Paolo Bonzini
2022-02-18 17:37 ` Sean Christopherson
2022-02-18 17:41 ` Paolo Bonzini
2022-02-17 18:08 ` [PATCH v3 6/6] KVM: x86: allow defining return-0 static calls Paolo Bonzini
2022-02-18 16:29 ` Sean Christopherson
2022-02-18 17:20 ` Paolo Bonzini
2022-02-18 17:33 ` Sean Christopherson
2022-03-17 17:43 ` Maxim Levitsky
2022-03-17 22:30 ` David Laight
2022-03-18 16:29 ` Paolo Bonzini
2022-03-18 17:28 ` Peter Zijlstra
2022-03-18 17:47 ` Peter Zijlstra
2022-03-18 18:02 ` Peter Zijlstra
2022-03-18 23:03 ` David Laight
2022-03-20 13:58 ` Maxim Levitsky
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=20220217180831.288210-1-pbonzini@redhat.com \
--to=pbonzini@redhat.com \
--cc=kvm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=seanjc@google.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;
as well as URLs for NNTP newsgroup(s).