From: Sean Christopherson <seanjc@google.com>
To: Paolo Bonzini <pbonzini@redhat.com>
Cc: Sean Christopherson <seanjc@google.com>,
Vitaly Kuznetsov <vkuznets@redhat.com>,
Wanpeng Li <wanpengli@tencent.com>,
Jim Mattson <jmattson@google.com>, Joerg Roedel <joro@8bytes.org>,
kvm@vger.kernel.org, linux-kernel@vger.kernel.org,
Chenyi Qiang <chenyi.qiang@intel.com>
Subject: [PATCH 0/3] KVM: x86: Nested fixes (mostly #DF/#TF)
Date: Thu, 7 Apr 2022 00:23:12 +0000 [thread overview]
Message-ID: <20220407002315.78092-1-seanjc@google.com> (raw)
Patch 1 removes an assertion that is going to fail miserably once KVM
allows save/restore of pending triple faults.
Patches 2 and 3 are fixes for edge cases for nVMX related to saving exit
info on failed VM-Entry, #DF and triple fault, that in all likelihood no
one cares about.
Sean Christopherson (3):
KVM: x86: Drop WARNs that assert a triple fault never "escapes" from
L2
KVM: nVMX: Leave most VM-Exit info fields unmodified on failed
VM-Entry
KVM: nVMX: Clear IDT vectoring on nested VM-Exit for double/triple
fault
arch/x86/kvm/svm/nested.c | 3 ---
arch/x86/kvm/vmx/nested.c | 48 ++++++++++++++++++++++++++++++---------
arch/x86/kvm/vmx/vmcs.h | 5 ++++
3 files changed, 42 insertions(+), 14 deletions(-)
base-commit: 7d4cda14f55ae6998220aaecd2ab00e20d0e8f57
--
2.35.1.1094.g7c7d902a7c-goog
next reply other threads:[~2022-04-07 0:23 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-04-07 0:23 Sean Christopherson [this message]
2022-04-07 0:23 ` [PATCH 1/3] KVM: x86: Drop WARNs that assert a triple fault never "escapes" from L2 Sean Christopherson
2022-04-07 0:23 ` [PATCH 2/3] KVM: nVMX: Leave most VM-Exit info fields unmodified on failed VM-Entry Sean Christopherson
2022-04-07 0:23 ` [PATCH 3/3] KVM: nVMX: Clear IDT vectoring on nested VM-Exit for double/triple fault Sean Christopherson
2022-04-07 8:02 ` Xiaoyao Li
2022-04-07 8:42 ` Xiaoyao Li
2022-04-08 16:50 ` [PATCH 0/3] KVM: x86: Nested fixes (mostly #DF/#TF) 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=20220407002315.78092-1-seanjc@google.com \
--to=seanjc@google.com \
--cc=chenyi.qiang@intel.com \
--cc=jmattson@google.com \
--cc=joro@8bytes.org \
--cc=kvm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=pbonzini@redhat.com \
--cc=vkuznets@redhat.com \
--cc=wanpengli@tencent.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®