diff options
| author | Sean Christopherson <seanjc@google.com> | 2025-12-05 16:43:05 -0800 |
|---|---|---|
| committer | Sean Christopherson <seanjc@google.com> | 2026-01-12 09:31:38 -0800 |
| commit | ca909f9ea8cb19032c9d9d7841a8e2395b6a9e8b (patch) | |
| tree | cbc7d818e7377f68187304da8ad79c43f879d7a7 /tools/perf/scripts/python | |
| parent | 37187992dd821e0283da3f7664ef3d6ab4220ef8 (diff) | |
| download | linux-ca909f9ea8cb19032c9d9d7841a8e2395b6a9e8b.tar.gz linux-ca909f9ea8cb19032c9d9d7841a8e2395b6a9e8b.zip | |
KVM: x86: Drop ASSERT() on I/O APIC EOIs being only for LEVEL_to WARN_ON_ONCE
Remove kvm_ioapic_update_eoi_one()'s ASSERT() that the vector's entry is
configured to be level-triggered, as KVM intercepts and forward EOIs to
the I/O APIC even for edge-triggered IRQs (see kvm_ioapic_scan_entry()),
and nothing guarantees the local APIC's TMR register is synchronized with
the I/O APIC redirection table, i.e. the @trigger_mode check just out of
sight doesn't provide any meaningful protection.
Given that roughly half of the historic ASSERT()s are/were guest- and/or
user-triggerable, it's safe to assume no one has run meaningful workloads
with DEBUG=1, i.e. that the ASSERT() has been dead code since it was
added 18+ years ago.
Opportunistically drop the unnecessary forward declaration of
kvm_ioapic_update_eoi_one().
For all intents and purposes, no functional change intended.
Link: https://patch.msgid.link/20251206004311.479939-4-seanjc@google.com
Signed-off-by: Sean Christopherson <seanjc@google.com>
Diffstat (limited to 'tools/perf/scripts/python')
0 files changed, 0 insertions, 0 deletions
