[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20231027204933.3651381-6-seanjc@google.com>
Date: Fri, 27 Oct 2023 13:49:29 -0700
From: Sean Christopherson <seanjc@...gle.com>
To: Paolo Bonzini <pbonzini@...hat.com>
Cc: kvm@...r.kernel.org, linux-kernel@...r.kernel.org,
Sean Christopherson <seanjc@...gle.com>
Subject: [GIT PULL] KVM: x86: PMU change for 6.7
A single PMU change for 6.7. Note, this _just_ got rebased because I had a
brain fart and used kvm-x86/next as the base when recreating the "pmu" branch
after the fixes for 6.6 were merged. The commit has been in -next since October
16th as 4b09cc132a59. This is not at all urgent and can definitely be deferred
to 6.8 if the late rebase is an issue.
The following changes since commit 2b3f2325e71f09098723727d665e2e8003d455dc:
Merge tag 'kvm-x86-selftests-6.6-fixes' of https://github.com/kvm-x86/linux into HEAD (2023-10-15 08:25:18 -0400)
are available in the Git repository at:
https://github.com/kvm-x86/linux.git tags/kvm-x86-pmu-6.7
for you to fetch changes up to fad505b2cb838fb52cb72fa22830824c80330f2f:
KVM: x86: Service NMI requests after PMI requests in VM-Enter path (2023-10-27 13:20:29 -0700)
----------------------------------------------------------------
KVM PMU change for 6.7:
- Handle NMI/SMI requests after PMU/PMI requests so that a PMI=>NMI doesn't
require redoing the entire run loop due to the NMI not being detected until
the final kvm_vcpu_exit_request() check before entering the guest.
----------------------------------------------------------------
Mingwei Zhang (1):
KVM: x86: Service NMI requests after PMI requests in VM-Enter path
arch/x86/kvm/x86.c | 12 ++++++------
1 file changed, 6 insertions(+), 6 deletions(-)
Powered by blists - more mailing lists