From: Krish Sadhukhan <krish.sadhukhan@oracle.com>
To: kvm@vger.kernel.org
Cc: pbonzini@redhat.com, vkuznets@redhat.com, qemu-devel@nongnu.org,
sean.j.christopherson@intel.com, jmattson@google.com
Subject: [PATCH 0/5 v4] KVM: x86: Fill in conforming {vmx|svm}_x86_ops and {vmx|svm}_nested_ops via macros
Date: Tue, 10 Nov 2020 01:23:07 +0000 [thread overview]
Message-ID: <20201110012312.20820-1-krish.sadhukhan@oracle.com> (raw)
v3 -> v4:
1. v3 did not include a few x86_ops and x86_nested_ops in the macro
expansion process of function names. This set has covered all those
left-out ops.
2. Patch# 6 from v3 has been dropped as those changes already exist in
QEMU source.
[PATCH 1/5 v4] KVM: x86: Change names of some of the kvm_x86_ops
[PATCH 2/5 v4] KVM: SVM: Fill in conforming svm_x86_ops via macro
[PATCH 3/5 v4] KVM: nSVM: Fill in conforming svm_nested_ops via macro
[PATCH 4/5 v4] KVM: VMX: Fill in conforming vmx_x86_ops via macro
[PATCH 5/5 v4] KVM: nVMX: Fill in conforming vmx_nested_ops via macro
arch/arm64/include/asm/kvm_host.h | 2 +-
arch/mips/include/asm/kvm_host.h | 2 +-
arch/powerpc/include/asm/kvm_host.h | 2 +-
arch/s390/kvm/kvm-s390.c | 2 +-
arch/x86/include/asm/kvm_host.h | 16 +-
arch/x86/kvm/lapic.c | 2 +-
arch/x86/kvm/pmu.h | 4 +-
arch/x86/kvm/svm/avic.c | 11 +-
arch/x86/kvm/svm/nested.c | 20 +--
arch/x86/kvm/svm/pmu.c | 2 +-
arch/x86/kvm/svm/sev.c | 4 +-
arch/x86/kvm/svm/svm.c | 296 ++++++++++++++++++++----------------
arch/x86/kvm/svm/svm.h | 15 +-
arch/x86/kvm/vmx/evmcs.c | 6 +-
arch/x86/kvm/vmx/evmcs.h | 4 +-
arch/x86/kvm/vmx/nested.c | 39 +++--
arch/x86/kvm/vmx/pmu_intel.c | 2 +-
arch/x86/kvm/vmx/posted_intr.c | 6 +-
arch/x86/kvm/vmx/posted_intr.h | 4 +-
arch/x86/kvm/vmx/vmx.c | 262 +++++++++++++++----------------
arch/x86/kvm/vmx/vmx.h | 4 +-
arch/x86/kvm/x86.c | 41 ++---
include/linux/kvm_host.h | 2 +-
include/uapi/linux/kvm.h | 6 +-
tools/include/uapi/linux/kvm.h | 6 +-
virt/kvm/kvm_main.c | 4 +-
26 files changed, 405 insertions(+), 359 deletions(-)
Krish Sadhukhan (5):
KVM: x86: Change names of some of the kvm_x86_ops functions to make them more semantical and readable
KVM: SVM: Fill in conforming svm_x86_ops via macro
KVM: nSVM: Fill in conforming svm_nested_ops via macro
KVM: VMX: Fill in conforming vmx_x86_ops via macro
KVM: nVMX: Fill in conforming vmx_nested_ops via macro
next reply other threads:[~2020-11-10 1:25 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-11-10 1:23 Krish Sadhukhan [this message]
2020-11-10 1:23 ` [PATCH 1/5 v4] KVM: x86: Change names of some of the kvm_x86_ops functions to make them more semantical and readable Krish Sadhukhan
2020-11-10 1:23 ` [PATCH 2/5 v4] KVM: SVM: Fill in conforming svm_x86_ops via macro Krish Sadhukhan
2020-11-10 3:56 ` kernel test robot
2020-11-10 1:23 ` [PATCH 3/5 v4] KVM: nSVM: Fill in conforming svm_nested_ops " Krish Sadhukhan
2020-11-10 1:23 ` [PATCH 4/5 v4] KVM: VMX: Fill in conforming vmx_x86_ops " Krish Sadhukhan
2020-11-10 1:49 ` Like Xu
2020-11-10 19:02 ` Krish Sadhukhan
2020-11-11 1:54 ` Xu, Like
2020-11-10 1:23 ` [PATCH 5/5 v4] KVM: nVMX: Fill in conforming vmx_nested_ops " Krish Sadhukhan
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=20201110012312.20820-1-krish.sadhukhan@oracle.com \
--to=krish.sadhukhan@oracle.com \
--cc=jmattson@google.com \
--cc=kvm@vger.kernel.org \
--cc=pbonzini@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=sean.j.christopherson@intel.com \
--cc=vkuznets@redhat.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).