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: APIC changes for 6.7
Date: Fri, 27 Oct 2023 13:49:25 -0700 [thread overview]
Message-ID: <20231027204933.3651381-2-seanjc@google.com> (raw)
In-Reply-To: <20231027204933.3651381-1-seanjc@google.com>
Two small APIC changes for 6.7, both specific to Intel's APICv.
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-apic-6.7
for you to fetch changes up to 629d3698f6958ee6f8131ea324af794f973b12ac:
KVM: x86: Clear bit12 of ICR after APIC-write VM-exit (2023-09-28 10:42:16 -0700)
----------------------------------------------------------------
KVM x86 APIC changes for 6.7:
- Purge VMX's posted interrupt descriptor *before* loading APIC state when
handling KVM_SET_LAPIC. Purging the PID after loading APIC state results in
lost APIC timer IRQs as the APIC timer can be armed as part of loading APIC
state, i.e. can immediately pend an IRQ if the expiry is in the past.
- Clear the ICR.BUSY bit when handling trap-like x2APIC writes to suppress a
WARN due to KVM expecting the BUSY bit to be cleared when sending IPIs.
----------------------------------------------------------------
Haitao Shan (1):
KVM: x86: Fix lapic timer interrupt lost after loading a snapshot.
Tao Su (1):
KVM: x86: Clear bit12 of ICR after APIC-write VM-exit
arch/x86/include/asm/kvm-x86-ops.h | 1 +
arch/x86/include/asm/kvm_host.h | 1 +
arch/x86/kvm/lapic.c | 30 +++++++++++++++++-------------
arch/x86/kvm/vmx/vmx.c | 4 ++--
4 files changed, 21 insertions(+), 15 deletions(-)
next prev parent reply other threads:[~2023-10-27 20:49 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 ` Sean Christopherson [this message]
2023-10-31 14:15 ` [GIT PULL] KVM: x86: APIC changes " 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 ` [GIT PULL] KVM: x86: SVM changes " Sean Christopherson
2023-10-31 14:55 ` 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-2-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®