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.7
Date: Fri, 27 Oct 2023 13:49:30 -0700 [thread overview]
Message-ID: <20231027204933.3651381-7-seanjc@google.com> (raw)
In-Reply-To: <20231027204933.3651381-1-seanjc@google.com>
An enhancement to help userspace deal with SEV-ES guest crashes, and cleanups
related to not being able to do "skip" emulation for SEV guests.
The following changes since commit 5804c19b80bf625c6a9925317f845e497434d6d3:
Merge tag 'kvm-riscv-fixes-6.6-1' of https://github.com/kvm-riscv/linux into HEAD (2023-09-23 05:35:55 -0400)
are available in the Git repository at:
https://github.com/kvm-x86/linux.git tags/kvm-x86-svm-6.7
for you to fetch changes up to 00682995409696866fe43984c74c8688bdf8f0a5:
KVM: SVM: Treat all "skip" emulation for SEV guests as outright failures (2023-10-04 15:08:53 -0700)
----------------------------------------------------------------
KVM SVM changes for 6.7:
- Report KVM_EXIT_SHUTDOWN instead of EINVAL if KVM intercepts SHUTDOWN while
running an SEV-ES guest.
- Clean up handling "failures" when KVM detects it can't emulate the "skip"
action for an instruction that has already been partially emulated. Drop a
hack in the SVM code that was fudging around the emulator code not giving
SVM enough information to do the right thing.
----------------------------------------------------------------
Peter Gonda (1):
KVM: SVM: Update SEV-ES shutdown intercepts with more metadata
Sean Christopherson (2):
KVM: x86: Refactor can_emulate_instruction() return to be more expressive
KVM: SVM: Treat all "skip" emulation for SEV guests as outright failures
arch/x86/include/asm/kvm-x86-ops.h | 2 +-
arch/x86/include/asm/kvm_host.h | 4 +--
arch/x86/kvm/svm/svm.c | 50 ++++++++++++++++----------------------
arch/x86/kvm/vmx/vmx.c | 12 ++++-----
arch/x86/kvm/x86.c | 22 +++++++++++------
5 files changed, 45 insertions(+), 45 deletions(-)
next prev parent reply other threads:[~2023-10-27 20:50 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-10-27 20:49 [GIT PULL] KVM: x86 pull requests " Sean Christopherson
2023-10-27 20:49 ` [GIT PULL] KVM: x86: APIC changes " Sean Christopherson
2023-10-31 14:15 ` Paolo Bonzini
2023-10-27 20:49 ` [GIT PULL] KVM: x86: Documentation updates " Sean Christopherson
2023-10-31 14:14 ` Paolo Bonzini
2023-10-27 20:49 ` [GIT PULL] KVM: x86: Misc changes " Sean Christopherson
2023-10-31 14:21 ` Paolo Bonzini
2023-10-27 20:49 ` [GIT PULL] KVM: x86: MMU " Sean Christopherson
2023-10-31 14:20 ` Paolo Bonzini
2023-10-27 20:49 ` [GIT PULL] KVM: x86: PMU change " Sean Christopherson
2023-10-27 20:49 ` Sean Christopherson [this message]
2023-10-31 14:55 ` [GIT PULL] KVM: x86: SVM changes " Paolo Bonzini
2023-10-27 20:49 ` [GIT PULL] KVM: x86: Xen " Sean Christopherson
2023-10-31 14:22 ` 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=20231027204933.3651381-7-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®