From: Sean Christopherson <seanjc@google.com>
To: Sean Christopherson <seanjc@google.com>,
Paolo Bonzini <pbonzini@redhat.com>,
Vitaly Kuznetsov <vkuznets@redhat.com>,
David Woodhouse <dwmw2@infradead.org>,
Paul Durrant <paul@xen.org>
Cc: kvm@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 0/9] KVM: x86: APIC and I/O APIC cleanups
Date: Mon, 12 Jan 2026 09:38:32 -0800 [thread overview]
Message-ID: <176823891558.1370546.10438547249061271576.b4-ty@google.com> (raw)
In-Reply-To: <20251206004311.479939-1-seanjc@google.com>
On Fri, 05 Dec 2025 16:43:02 -0800, Sean Christopherson wrote:
> Drop a bunch of _really_ old dead code (ASSERT() buried behind a DEBUG
> macro that probably hasn't been enabled in 15+ years), clean up the bizarre
> and confusing "dest_map" pointer that gets passed all of the place but is
> only actually used for in-kernel RTC emulation, and the bury almost all of
> ioapic.h behind CONFIG_KVM_IOAPIC=y.
>
> I'm not entirely sure why I started poking at this. I think I got mad at
> the dest_map code, and then things snowballed...
>
> [...]
Applied to kvm-x86 apic, thanks!
[1/9] KVM: x86: Drop ASSERT()s on APIC/vCPU being non-NULL
https://github.com/kvm-x86/linux/commit/a4978324e4bd
[2/9] KVM: x86: Drop guest/user-triggerable asserts on IRR/ISR vectors
https://github.com/kvm-x86/linux/commit/37187992dd82
[3/9] KVM: x86: Drop ASSERT() on I/O APIC EOIs being only for LEVEL_to WARN_ON_ONCE
https://github.com/kvm-x86/linux/commit/ca909f9ea8cb
[4/9] KVM: x86: Drop guest-triggerable ASSERT()s on I/O APIC access alignment
https://github.com/kvm-x86/linux/commit/9eabb2a5e499
[5/9] KVM: x86: Drop MAX_NR_RESERVED_IOAPIC_PINS, use KVM_MAX_IRQ_ROUTES directly
https://github.com/kvm-x86/linux/commit/4d846f183897
[6/9] KVM: x86: Add a wrapper to handle common case of IRQ delivery without dest_map
https://github.com/kvm-x86/linux/commit/1a5d7f9540af
[7/9] KVM: x86: Fold "struct dest_map" into "struct rtc_status"
https://github.com/kvm-x86/linux/commit/5cd6b1a6eebd
[8/9] KVM: x86: Bury ioapic.h definitions behind CONFIG_KVM_IOAPIC
https://github.com/kvm-x86/linux/commit/59c3e0603d86
[9/9] KVM: x86: Hide KVM_IRQCHIP_KERNEL behind CONFIG_KVM_IOAPIC=y
https://github.com/kvm-x86/linux/commit/fd09d259c161
--
https://github.com/kvm-x86/linux/tree/next
prev parent reply other threads:[~2026-01-12 17:39 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-12-06 0:43 Sean Christopherson
2025-12-06 0:43 ` [PATCH 1/9] KVM: x86: Drop ASSERT()s on APIC/vCPU being non-NULL Sean Christopherson
2025-12-06 0:43 ` [PATCH 2/9] KVM: x86: Drop guest/user-triggerable asserts on IRR/ISR vectors Sean Christopherson
2025-12-06 0:43 ` [PATCH 3/9] KVM: x86: Drop ASSERT() on I/O APIC EOIs being only for LEVEL_to WARN_ON_ONCE Sean Christopherson
2025-12-06 0:43 ` [PATCH 4/9] KVM: x86: Drop guest-triggerable ASSERT()s on I/O APIC access alignment Sean Christopherson
2025-12-06 0:43 ` [PATCH 5/9] KVM: x86: Drop MAX_NR_RESERVED_IOAPIC_PINS, use KVM_MAX_IRQ_ROUTES directly Sean Christopherson
2025-12-06 0:43 ` [PATCH 6/9] KVM: x86: Add a wrapper to handle common case of IRQ delivery without dest_map Sean Christopherson
2025-12-06 0:43 ` [PATCH 7/9] KVM: x86: Fold "struct dest_map" into "struct rtc_status" Sean Christopherson
2025-12-06 0:43 ` [PATCH 8/9] KVM: x86: Bury ioapic.h definitions behind CONFIG_KVM_IOAPIC Sean Christopherson
2025-12-06 0:43 ` [PATCH 9/9] KVM: x86: Hide KVM_IRQCHIP_KERNEL behind CONFIG_KVM_IOAPIC=y Sean Christopherson
2026-01-12 17:38 ` Sean Christopherson [this message]
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=176823891558.1370546.10438547249061271576.b4-ty@google.com \
--to=seanjc@google.com \
--cc=dwmw2@infradead.org \
--cc=kvm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=paul@xen.org \
--cc=pbonzini@redhat.com \
--cc=vkuznets@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®