From: Sean Christopherson <seanjc@google.com>
To: Sean Christopherson <seanjc@google.com>,
Paolo Bonzini <pbonzini@redhat.com>
Cc: kvm@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: [PATCH 0/3] KVM: Mark vendor module param read-only after init
Date: Thu, 10 Nov 2022 01:30:00 +0000 [thread overview]
Message-ID: <20221110013003.1421895-1-seanjc@google.com> (raw)
Mark the read-only VMX and SVM module params, and a few other global
variables, read-only after init. In many cases, KVM is royally hosed if
a configuration knob changes while VMs are running, e.g. toggling the TDP
knob would result in spectacular fireworks.
This series is probably best queued very early in a cycle, as the result
of mis-labeled variable is an unexpected kernel #PF.
Sean Christopherson (3):
KVM: VMX: Make module params and other variables read-only after init
KVM: SVM: Make MSR permission bitmap offsets read-only after init
KVM: SVM: Make module params and other variables read-only after init
arch/x86/kvm/svm/svm.c | 38 ++++++++++++++++-----------------
arch/x86/kvm/svm/svm.h | 2 +-
arch/x86/kvm/vmx/capabilities.h | 16 +++++++-------
arch/x86/kvm/vmx/nested.c | 4 ++--
arch/x86/kvm/vmx/sgx.c | 2 +-
arch/x86/kvm/vmx/sgx.h | 2 +-
arch/x86/kvm/vmx/vmx.c | 36 +++++++++++++++----------------
7 files changed, 50 insertions(+), 50 deletions(-)
base-commit: d663b8a285986072428a6a145e5994bc275df994
--
2.38.1.431.g37b22c650d-goog
next reply other threads:[~2022-11-10 1:30 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-10 1:30 Sean Christopherson [this message]
2022-11-10 1:30 ` [PATCH 1/3] KVM: VMX: Make module params and other variables " Sean Christopherson
2022-11-10 1:30 ` [PATCH 2/3] KVM: SVM: Make MSR permission bitmap offsets " Sean Christopherson
2022-11-10 1:30 ` [PATCH 3/3] KVM: SVM: Make module params and other variables " Sean Christopherson
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=20221110013003.1421895-1-seanjc@google.com \
--to=seanjc@google.com \
--cc=kvm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=pbonzini@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®