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,
Kai Huang <kai.huang@intel.com>,
xuyun <xuyun_xy.xy@linux.alibaba.com>,
weizijie <zijie.wei@linux.alibaba.com>
Subject: [PATCH v5 0/3] KVM: x86: Optimize "stale" EOI bitmap exiting
Date: Mon, 3 Mar 2025 17:33:32 -0800 [thread overview]
Message-ID: <20250304013335.4155703-1-seanjc@google.com> (raw)
Slightly modified version of the patch (now mini-series) to optimize EOI
bitmap exiting for "stale" routes, i.e. for the case where a vCPU has an
in-flight IRQ when the routing changes, and needs one final EOI exit to
deassert the IRQ.
Kai, I dropped your Reviewed-by as the change was non-trivial.
v5:
- Intercept EOI if and only if the IRQ is level-triggered.
- Add helper to consolidate logic.
- Tweak field name.
- "Reset" field to -1, immediately before scanning routes.
v4: https://lore.kernel.org/all/20250303052227.523411-1-zijie.wei@linux.alibaba.com
Sean Christopherson (2):
KVM: x86: Isolate edge vs. level check in userspace I/O APIC route
scanning
KVM: x86: Add a helper to deduplicate I/O APIC EOI interception logic
weizijie (1):
KVM: x86: Rescan I/O APIC routes after EOI interception for old
routing
arch/x86/include/asm/kvm_host.h | 1 +
arch/x86/kvm/ioapic.c | 7 ++-----
arch/x86/kvm/ioapic.h | 2 ++
arch/x86/kvm/irq_comm.c | 37 ++++++++++++++++++++++++++++-----
arch/x86/kvm/lapic.c | 8 +++++++
arch/x86/kvm/x86.c | 1 +
6 files changed, 46 insertions(+), 10 deletions(-)
base-commit: ead22377189e55ba0e9b637a8f48578cf84f5b9c
--
2.48.1.711.g2feabab25a-goog
next reply other threads:[~2025-03-04 1:33 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-03-04 1:33 Sean Christopherson [this message]
2025-03-04 1:33 ` [PATCH v5 1/3] KVM: x86: Isolate edge vs. level check in userspace I/O APIC route scanning Sean Christopherson
2025-03-04 9:42 ` Huang, Kai
2025-04-10 22:46 ` Sean Christopherson
2025-04-10 22:55 ` Kai Huang
2025-03-04 1:33 ` [PATCH v5 2/3] KVM: x86: Add a helper to deduplicate I/O APIC EOI interception logic Sean Christopherson
2025-03-04 9:45 ` Huang, Kai
2025-03-04 1:33 ` [PATCH v5 3/3] KVM: x86: Rescan I/O APIC routes after EOI interception for old routing Sean Christopherson
2025-03-04 9:54 ` Huang, Kai
2025-04-25 22:09 ` [PATCH v5 0/3] KVM: x86: Optimize "stale" EOI bitmap exiting 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=20250304013335.4155703-1-seanjc@google.com \
--to=seanjc@google.com \
--cc=kai.huang@intel.com \
--cc=kvm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=pbonzini@redhat.com \
--cc=xuyun_xy.xy@linux.alibaba.com \
--cc=zijie.wei@linux.alibaba.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