From: Sean Christopherson <seanjc@google.com>
To: Paolo Bonzini <pbonzini@redhat.com>
Cc: kvm@vger.kernel.org, linux-kernel@vger.kernel.org,
Sean Christopherson <seanjc@google.com>
Subject: [GIT PULL] KVM: x86: SVM changes for 6.8
Date: Thu, 4 Jan 2024 11:33:02 -0800 [thread overview]
Message-ID: <20240104193303.3175844-8-seanjc@google.com> (raw)
In-Reply-To: <20240104193303.3175844-1-seanjc@google.com>
A few minor fixes and cleanups, along with feature "enabling" for flush-by-ASID
to play nice with newer versions of VMware Workstation that require it.
The following changes since commit e9e60c82fe391d04db55a91c733df4a017c28b2f:
selftests/kvm: fix compilation on non-x86_64 platforms (2023-11-21 11:58:25 -0500)
are available in the Git repository at:
https://github.com/kvm-x86/linux.git tags/kvm-x86-svm-6.8
for you to fetch changes up to 72046d0a077a8f70d4d1e5bdeed324c1a310da8c:
KVM: SVM: Don't intercept IRET when injecting NMI and vNMI is enabled (2023-11-30 12:51:22 -0800)
----------------------------------------------------------------
KVM SVM changes for 6.8:
- Revert a bogus, made-up nested SVM consistency check for TLB_CONTROL.
- Advertise flush-by-ASID support for nSVM unconditionally, as KVM always
flushes on nested transitions, i.e. always satisfies flush requests. This
allows running bleeding edge versions of VMware Workstation on top of KVM.
- Sanity check that the CPU supports flush-by-ASID when enabling SEV support.
- Fix a benign NMI virtualization bug where KVM would unnecessarily intercept
IRET when manually injecting an NMI, e.g. when KVM pends an NMI and injects
a second, "simultaneous" NMI.
----------------------------------------------------------------
Sean Christopherson (4):
Revert "nSVM: Check for reserved encodings of TLB_CONTROL in nested VMCB"
KVM: nSVM: Advertise support for flush-by-ASID
KVM: SVM: Explicitly require FLUSHBYASID to enable SEV support
KVM: SVM: Don't intercept IRET when injecting NMI and vNMI is enabled
arch/x86/kvm/svm/nested.c | 15 ---------------
arch/x86/kvm/svm/sev.c | 7 +++++--
arch/x86/kvm/svm/svm.c | 18 ++++++++++++++++--
3 files changed, 21 insertions(+), 19 deletions(-)
next prev parent reply other threads:[~2024-01-04 19:33 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-01-04 19:32 [GIT PULL] KVM: x86 pull requests " Sean Christopherson
2024-01-04 19:32 ` [GIT PULL] KVM: non-x86 changes " Sean Christopherson
2024-01-08 12:54 ` Paolo Bonzini
2024-01-04 19:32 ` [GIT PULL] KVM: x86: Hyper-V " Sean Christopherson
2024-01-08 12:56 ` Paolo Bonzini
2024-01-04 19:32 ` [GIT PULL] KVM: x86: LAM support " Sean Christopherson
2024-01-08 13:04 ` Paolo Bonzini
2024-01-22 7:57 ` Binbin Wu
2024-01-04 19:32 ` [GIT PULL] KVM: x86: Misc changes " Sean Christopherson
2024-01-08 12:58 ` Paolo Bonzini
2024-01-04 19:33 ` [GIT PULL] KVM: x86: MMU " Sean Christopherson
2024-01-04 19:33 ` [GIT PULL] KVM: x86: PMU " Sean Christopherson
2024-01-08 12:57 ` Paolo Bonzini
2024-01-04 19:33 ` Sean Christopherson [this message]
2024-01-08 13:05 ` [GIT PULL] KVM: x86: SVM " Paolo Bonzini
2024-01-04 19:33 ` [GIT PULL] KVM: x86: Xen change " Sean Christopherson
2024-01-08 13:06 ` Paolo Bonzini
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=20240104193303.3175844-8-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®