From: Sean Christopherson <seanjc@google.com>
To: Vitaly Kuznetsov <vkuznets@redhat.com>,
Sean Christopherson <seanjc@google.com>,
Paolo Bonzini <pbonzini@redhat.com>,
Nathan Chancellor <nathan@kernel.org>,
Nick Desaulniers <ndesaulniers@google.com>
Cc: Tom Rix <trix@redhat.com>,
kvm@vger.kernel.org, llvm@lists.linux.dev,
linux-kernel@vger.kernel.org
Subject: [PATCH 0/2] KVM: VMX: Stub out enable_evmcs static key
Date: Wed, 8 Feb 2023 20:54:28 +0000 [thread overview]
Message-ID: <20230208205430.1424667-1-seanjc@google.com> (raw)
Stub out the enable_evmcs static key for CONFIG_HYPERV=n. gcc (as of
gcc-12) isn't clever enough to elide the nop placeholder when there's no
code guarded by a static branch. With gcc-12, because of the vast number
of VMCS accesses, eliminating the nops reduces the size of kvm-intel.ko by
~7.5% (200KiB).
Patch 1 is tangentially related cleanup.
Applies on `git@github.com:kvm-x86/linux.git vmx`.
Sean Christopherson (2):
KVM: nVMX: Move EVMCS1_SUPPORT_* macros to hyperv.c
KVM: VMX: Stub out enable_evmcs static key for CONFIG_HYPERV=n
arch/x86/kvm/vmx/hyperv.c | 107 +++++++++++++++++++++++++++++++++-
arch/x86/kvm/vmx/hyperv.h | 115 +++----------------------------------
arch/x86/kvm/vmx/vmx.c | 15 +++--
arch/x86/kvm/vmx/vmx_ops.h | 22 +++----
4 files changed, 132 insertions(+), 127 deletions(-)
base-commit: 93827a0a36396f2fd6368a54a020f420c8916e9b
--
2.39.1.519.gcb327c4b5f-goog
next reply other threads:[~2023-02-08 20:54 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-02-08 20:54 Sean Christopherson [this message]
2023-02-08 20:54 ` [PATCH 1/2] KVM: nVMX: Move EVMCS1_SUPPORT_* macros to hyperv.c Sean Christopherson
2023-02-09 13:08 ` Vitaly Kuznetsov
2023-02-08 20:54 ` [PATCH 2/2] KVM: VMX: Stub out enable_evmcs static key for CONFIG_HYPERV=n Sean Christopherson
2023-02-09 13:13 ` Vitaly Kuznetsov
2023-02-09 13:56 ` Paolo Bonzini
2023-02-10 1:13 ` Sean Christopherson
2023-02-10 9:55 ` Vitaly Kuznetsov
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=20230208205430.1424667-1-seanjc@google.com \
--to=seanjc@google.com \
--cc=kvm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=llvm@lists.linux.dev \
--cc=nathan@kernel.org \
--cc=ndesaulniers@google.com \
--cc=pbonzini@redhat.com \
--cc=trix@redhat.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
all inboxes | Powered by JetHome®