From: Sean Christopherson <seanjc@google.com>
To: Sean Christopherson <seanjc@google.com>,
Paolo Bonzini <pbonzini@redhat.com>
Cc: kvm@vger.kernel.org, linux-kernel@vger.kernel.org,
Sashiko Bot <sashiko-bot@kernel.org>,
Amirmohammad Eftekhar <amirmohammad.eftekhar@cispa.de>
Subject: [PATCH v3 0/3] KVM: x86: Drop deferred updates of EOI bitmaps
Date: Tue, 27 Oct 2026 15:30:35 -0700 [thread overview]
Message-ID: <20261027223038.1566931-1-seanjc@google.com> (raw)
Stop deferring EOI bitmap updates. As pointed out by Amirmohammad, I missed
this one when removing all the other cases where KVM defers an update until
vmcs01 is active.
Patch 1 fixes a pre-existing bug Sashiko pointed out where KVM doesn't update
the EOI bitmaps if APICv is temporarily inhibited.
v3: Add the aforementioned patch 1. [Sashiko]
v2: https://lore.kernel.org/all/20261022022813.303978-1-seanjc@google.com
v1: https://lore.kernel.org/all/20261017093016.32348-2-amirmohammad.eftekhar@cispa.de
Sean Christopherson (3):
KVM: VMX: Update EOI bitmaps even if APICv is (temporarily) inhibited
KVM: x86: Switch to vmcs01 to update EOI exiting bitmap on-demand if
L2 is active
KVM: x86: Consolidate invocations of kvm_x86_ops.load_eoi_exitmap()
arch/x86/include/asm/kvm_host.h | 3 +--
arch/x86/kvm/regs.h | 6 ------
arch/x86/kvm/vmx/vmx.c | 4 +++-
arch/x86/kvm/x86.c | 27 +++++++--------------------
4 files changed, 11 insertions(+), 29 deletions(-)
base-commit: 7e60162b16f9da0d2fa83da5c1723b6853a0ac1d
--
2.56.0.307.g5fe7bd680c-goog
next reply other threads:[~2026-10-27 22:30 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-27 22:30 Sean Christopherson [this message]
2026-10-27 22:30 ` [PATCH v3 1/3] KVM: VMX: Update EOI bitmaps even if APICv is (temporarily) inhibited Sean Christopherson
2026-10-27 22:30 ` [PATCH v3 2/3] KVM: x86: Switch to vmcs01 to update EOI exiting bitmap on-demand if L2 is active Sean Christopherson
2026-10-27 22:30 ` [PATCH v3 3/3] KVM: x86: Consolidate invocations of kvm_x86_ops.load_eoi_exitmap() Sean Christopherson
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=20261027223038.1566931-1-seanjc@google.com \
--to=seanjc@google.com \
--cc=amirmohammad.eftekhar@cispa.de \
--cc=kvm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=pbonzini@redhat.com \
--cc=sashiko-bot@kernel.org \
/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®