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: VMX changes for 6.6
Date: Tue, 29 Aug 2023 17:06:33 -0700 [thread overview]
Message-ID: <20230830000633.3158416-8-seanjc@google.com> (raw)
In-Reply-To: <20230830000633.3158416-1-seanjc@google.com>
VMX changes for 6.6. Nothing mindblowing, by far the most interesting change
is the super late fix for NMI VM-Exits that you've already looked at.
The following changes since commit fdf0eaf11452d72945af31804e2a1048ee1b574c:
Linux 6.5-rc2 (2023-07-16 15:10:37 -0700)
are available in the Git repository at:
https://github.com/kvm-x86/linux.git tags/kvm-x86-vmx-6.6
for you to fetch changes up to 50011c2a245792993f2756e5b5b571512bfa409e:
KVM: VMX: Refresh available regs and IDT vectoring info before NMI handling (2023-08-28 20:07:43 -0700)
----------------------------------------------------------------
KVM: x86: VMX changes for 6.6:
- Misc cleanups
- Fix a bug where KVM reads a stale vmcs.IDT_VECTORING_INFO_FIELD when trying
to handle NMI VM-Exits
----------------------------------------------------------------
Sean Christopherson (3):
KVM: VMX: Drop manual TLB flush when migrating vmcs.APIC_ACCESS_ADDR
KVM: VMX: Delete ancient pr_warn() about KVM_SET_TSS_ADDR not being set
KVM: VMX: Refresh available regs and IDT vectoring info before NMI handling
Shiyuan Gao (1):
KVM: VMX: Rename vmx_get_max_tdp_level() to vmx_get_max_ept_level()
arch/x86/kvm/vmx/vmx.c | 38 +++++++++++++++++---------------------
1 file changed, 17 insertions(+), 21 deletions(-)
next prev parent reply other threads:[~2023-08-30 0:07 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-08-30 0:06 [GIT PULL] KVM: x86 pull requests " Sean Christopherson
2023-08-30 0:06 ` [GIT PULL] KVM: Non-x86 changes " Sean Christopherson
2023-08-31 17:20 ` Paolo Bonzini
2023-08-30 0:06 ` [GIT PULL] KVM: x86: Misc " Sean Christopherson
2023-08-31 17:39 ` Paolo Bonzini
2023-08-31 18:27 ` Sean Christopherson
2023-08-30 0:06 ` [GIT PULL] KVM: x86: MMU " Sean Christopherson
2023-08-31 17:27 ` Sean Christopherson
2023-08-31 17:43 ` Paolo Bonzini
2023-09-01 18:43 ` Sean Christopherson
2023-09-01 21:07 ` Paolo Bonzini
2023-09-01 21:49 ` Sean Christopherson
2023-08-30 0:06 ` [GIT PULL] KVM: x86: PMU " Sean Christopherson
2023-08-31 17:31 ` Paolo Bonzini
2023-08-30 0:06 ` [GIT PULL] KVM: x86: Selftests " Sean Christopherson
2023-08-31 17:21 ` Paolo Bonzini
2023-08-30 0:06 ` [GIT PULL] KVM: x86: SVM " Sean Christopherson
2023-08-30 0:06 ` Sean Christopherson [this message]
2023-08-31 17:32 ` [GIT PULL] KVM: x86: VMX " Paolo Bonzini
2023-08-31 17:30 ` [GIT PULL] KVM: x86 pull requests " 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=20230830000633.3158416-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®