Changes in irq_test.c

67f8bc848ee31831336bd478e57d2f993551902e - Merge drm/drm-fixes into drm-misc-fixes

Tue, 01 Sep 2026 09:38:51 +0200

Merge drm/drm-fixes into drm-misc-fixesLet's start the 7.3 drm-misc-fixes cycle.Signed-off-by: Maxime Ripard List of files: /linux/tools/testing/selftests/kvm/irq_test.c

7bb6284aa7b3c369b41e7f33fcbe193161f008e7 - Merge tag 'for-linus' of git://git.kernel.org/pub/scm/virt/kvm/kvm

Tue, 25 Aug 2026 20:48:04 +0200

Merge tag 'for-linus' of git://git.kernel.org/pub/scm/virt/kvm/kvmPull kvm updates from Paolo Bonzini: "ARM64: - Add support for 'slot' based PMU events, paired with new UAPI that compels the user to select a specific PMU implementation - Lazy save/restore of vCPU state for pKVM, along with various fixes and cleanups to the management of vCPU state between the untrusted host and pKVM hypervisor - Disable traps of EL1 registers for nested hypervisors when FEAT_NV2p1 is present, guaranteeing that EL2-specific register bits are stateful in the EL1 counterpart - Leverage FEAT_NV3 to avoid unnecessary ERET/TLBI traps when the scope of those instructions remains 'in host' (i.e. L1 kernel/userspace) - Pile of fixes for the management of the VNCR pseudo-TLB, such as under-invalidations and races with concurrent TLBIs on other vCPUs - Consolidate the non-protected and pKVM view of ICH_VTR_EL2 to a runtime-patched constant, allowing the same data to be shared with pKVM prior to dropping host privileges - Considerable pile of LLM-assisted fixes around the shop but mostly in the VGIC, our in-kernel generator of bugs (and sometimes interrupts) LoongArch: - Advertise already-supported capabilities - Some bug fixes about timer and MMIO - Some hardening about interrupt injection - Replace kvm_err() with kvm_pr_unimpl() - Add FPU/LSX/LASX test cases for selftests RISC-V: - Svadu/Zicfiss/Zicfilp FWFT support for Guest - Use try_cmpxchg for IMSIC MRIF RMW - More arch-specific tracepoints in KVM RISC-V - Eager page splitting when enabling dirty logging - Optimize hfence request handling for SMP Guests - Improve dirty log clearing by skipping zero bits in mask - Guard HFENCE range loops against overflow - CPU PM notifiers in KVM RISC-V for non-retentive idle states - Fix kernel-mode vector context save/restore for Guest s390: - Fixes for vfio-ap - Fixes for the gmap rework - Fixes for vsie - AI triggered fixes all over - diag9c tracing - code move preparation for the additional arm64 support - enable CONTEXT_ANALYSIS x86: - Perform spring cleaning on x86.{c,h} and asm/kvm_host.h, by adding regs.c (the kvm_cache_regs.h => regs.h is already applied) and msrs.{c,h}, and moving relevant code out of x86.c - Split kvm_mmu in three parts, respectively to describe the format of page tables, walking the guest page tables and building the page tables. Always use the same page table walker kvm->arch.gva_walk as the entry point to convert a guest's virtual address, where the previous code used two different kvm_mmu structs depending on whether the walk included nested EPT/NPT or not. Make page fault vmexits reuse the permission checking machinery that is used for guest page faults. This is both a cleanup and a baby step towards supporting XS/XU memory permissions - Document some of the "fun" gotchas with the APIC base when creating IRQCHIPs on x86 - Remove a defunct masterclock update from kvm_xen_shared_info_init(). It could result in incorrect kvmclock due to triggering an unnecessary switch to/from masterclock mode - Skip Xen runstate time updates if time has effectively gone backwards, so that the guest doesn't report 100% steal time for a very, very long time - Drop KVM's runtime updates of the Xen PV timing CPUID leaf, as KVM was updating the wrong sub-leaf, and upstream KVM will soon provide all the information needed by userspace to populate the CPUID field itself - Fix a bug where KVM would walk a newly created rmap without holding the rmap lock (or mmu_lock) during aging - Fix a bug where aging TDP MMU SPTEs could clobber FROZEN SPTEs - Fix a variety of #DB priority bugs - Fix a class of races related to enabling Hyper-V emulation on a vCPU after the vCPU is visible to the rest of KVM - Use static calls for nested virtualization ops - Move more KVM-internal code out of x86's kvm_host.h - Enumerate support for a variety of Zhaoxin instructions that don't require explicit virtualization - Fix missing EFER validation bugs, including in the KVM_SET_SREGS* path - Harden kvm_vcpu_map() against double-mapping and thus leaking references - Misc fixes and cleanups, e.g. for largely benign syzkaller splats x86 (Intel): - Zero a vCPU's entry in VMX's Posted Interrupt Descriptor table used for IPI virtualization when the vCPU is freed, to fix a use-after-free where hardware will write to a freed vCPU's PID - Service local TLB flushes on a failed nested VM-Enter to fix a bug where KVM could miss a TLB on a future, successful VM-Enter with the same L2 VPID - Cap the maximum value shoved into the VMX Preemption Timer to workaround an erratum that affects all existing Intel CPUs that support CPUID 0x15 - Fix VPID virtualization bugs where KVM would fail to flush hardware TLBs - Harden the TDX "populate" ioctls against bad input, and to prepare for supporting in-place private<=>shared conversion x86 (AMD): - Forcefully invalidate SNP VMSA pages if their backing guest_memfd page is zapped/invalidated, e.g. due to a PUNCH_HOLE in response to a Page-State Change request - Remove a dying VM from the GA Log notifier list before the VM is actually destroyed, to fix a potential use-after-free - While FOLL_WRITE was needed in the past to trigger CoW unsharing, nowadays FOLL_LONGTERM does that already even without FOLL_WRITE, and in fact, get_user_pages() actually disallows FOLL_WRITE together with FOLL_LONGTERM. So don't pass FOLL_WRITE when registering encrypted memory regions, i.e. when pinning SEV/SEV-ES guest memory, to fix a regression with file-backed memory introduced by KVM's (correct) usage of long-term pins (This was reviewed by mm maintainers; for more information, see commit ee1a586dd1fa "KVM: SEV: Drop FOLL_WRITE for encrypted region registration") - Allocate full pages for SEV/SEV-ES {DE,EN}CRYPT ops on SNP-enabled hosts to fix a data corruption issue due to the PSP driver assigning to-be-written pages to firmware (as required by the SNP specs) - Unconditionally intercept ICBEP so that KVM generates the correct guest RIP when handling an ICEBP-induced TASK_SWITCH #VMEXIT - Harden the SNP "populate" ioctls against bad input, and to prepare for supporting in-place private<=>shared conversion Generic: - Remove kvm_debugfs_dir if kvm_init() fails after creating KVM's debugfs - Add a per-VM bitmap to track which vCPU IDs have been "claimed" but for which the vCPU isn't yet online, and use the bitmap to reject duplicate IDs before calling into arch code. This allows arch code to consume vcpu_id without having to worry about cross-vCPU clobbering (at least s390 and x86 have had related bugs) - Rework the so called "prepare" and "invalidate" guest_memfd hooks to prepare for in-place private<=>shared conversion, and clean up a few warts along the way Selftests: - Automatically allocate a full page for L2 guest stacks on x86 instead of requiring test-specific L1 guest code to carve out a portion of the L1 stack for L2 usage, and to ensure the L2 stack also adheres to the x86-64 calling convention ABI - Add a selftest to verify {Guest,Host}-Only behavior in x86's mediated PMU - Clean up nested SVM's handling of GPRs on L2<=>L1 transitions, reuse the functionality for nested VMX, and drop the ucall hack that was fudging around the lack of GPR switching on nVMX - Add a stress test to verify KVM doesn't clobber/drop #PF state, e.g. CR2, across save/restore, including when L2 is active - Add a test to verify KVM_CREATE_VM accepts exactly what is reported by KVM_CAP_VM_TYPES - Misc selftests fixes and cleanups - Fix several issues with seeding the pRNG, and rework the pRNG APIs to that the pRNG can be sanely used in host code, not just guest code - Add an IRQ test to validate virtual IRQ deliverty for IRQs wired up via KVM_IRQFD + KVM_SET_GSI_ROUTING, with optional support for triggering IRQs via writes to an assigned VFIO device - Add syscall wrappers to assert success on a variety of pthreads and CPU affinity APIs - Set vCPU pthread affinity as early as possible to reduce contention issues that were surfaced by PREEMPT_LAZY, which result in runtimes of over a minute on large hosts, versus the expected ~5 seconds - Rework the PMU counters test to run each testcase using a single VM with many vCPUs for each sub-testcase, instead of using a unique VM for each sub-testcase. This cuts the runtime by ~20x Miscellaneous: - MAINTAINERS updates for vfio-ap, guest_memfd, kvm-x86. Mostly representing the status quo more accurately, but also... welcome David Hildenbrand as guest_memfd reviewer!"* tag 'for-linus' of git://git.kernel.org/pub/scm/virt/kvm/kvm: (413 commits) KVM: arm64: Validate GICv5 timer PPIs before claiming ownership KVM: arm64: vgic: Reject out-of-range GICv5 PPI IDs KVM: arm64: vgic: Prevent speculative SPI array underflow KVM: arm64: vgic: Free gic_kvm_info on initialization failure KVM: arm64: Avoid mismatched accesses to 'struct kvm_nvhe_init_params' s390/vfio-ap: Fix NULL deref in status_show() during queue probe s390/vfio-ap: Fix hot-unplug skipped when last AP adapter or domain removed s390/vfio-ap: fix potential use of uninitialized apm_filtered bitmap s390/vfio-ap: Fix control domain removal in vfio_ap_mdev_cfg_remove s390/vfio-ap: Fix required lock not held during update of ap_matrix_mdev object s390/vfio-ap: Fix missing lock required to access list of ap_matrix_mdev objects s390/vfio-ap: Fix dereference matrix_mdev->kvm without checking for NULL s390/vfio-ap: Fix stale do_remove flag across iterations in vfio_ap_mdev_cfg_remove RISC-V: KVM: fix vcpu vector context handling for kernel-mode vector riscv: vector: allow non-preemptible kernel-mode vector with IRQs off riscv: vector: refactor riscv_v_start_kernel_context KVM: s390: gmap: Make prefix handling optional KVM: s390: gmap: Make CMMA optional KVM: s390: gmap: Make storage keys optional KVM: s390: Prepare gmap for a second KVM implementation ... List of files: /linux/tools/testing/selftests/kvm/irq_test.c

15a9a2ba0c546fb576085f36c6d39fbae6a32dd4 - Merge tag 'kvm-x86-selftests2-7.3' of https://github.com/kvm-x86/linux into HEAD

Tue, 18 Aug 2026 13:19:01 +0200

Merge tag 'kvm-x86-selftests2-7.3' of https://github.com/kvm-x86/linux into HEADKVM selftests changes for 7.3, part 2 - Fix several issues with seeding KVM's pRNG, and rework the pRNG APIs to that the pRNG can be sanely used in host code, not just guest code. - Add an IRQ test to validate virtual IRQ deliverty for IRQs wired up via KVM_IRQFD + KVM_SET_GSI_ROUTING, with optional support for triggering IRQs via writes to an assigned VFIO device. - Add syscall wrappers to assert success on a variety of pthreads and CPU affinity APIs. - Set vCPU pthread affinity as early as possible to reduce contention issues that were surfaced by PREEMPT_LAZY, which result in runtimes of over a minute on large hosts, versus the expected ~5 seconds. - Rework the PMU counters test to run each testcase using a single VM with many vCPUs for each sub-testcase, instead of using a unique VM for each sub-testcase. This cuts the runtime by ~20x. List of files: /linux/tools/testing/selftests/kvm/irq_test.c

bc9143135bf328a61456c7eb60e97b5ffb15e96e - KVM: selftests: Add KVM syscall wrappers for pthread_{cancel,join}()

Fri, 31 Jul 2026 21:56:09 +0200

KVM: selftests: Add KVM syscall wrappers for pthread_{cancel,join}()Add and use KVM wrappers for pthread_{cancel,join}() so that selftestsdon't need to manually assert that the syscalls succeeded.Note, the vast majority tests don't actually assert success, but they allobviously rely on the syscall to succeed.Other than explicitly failing if a syscall fails, no functional changeintended.Link: https://patch.msgid.link/20260731195612.2697986-10-seanjc@google.comSigned-off-by: Sean Christopherson List of files: /linux/tools/testing/selftests/kvm/irq_test.c

5171573ce7cbaaaa3a02879a369f5884e3906710 - KVM: selftests: Add KVM syscall wrapper for pthread_create()

Fri, 31 Jul 2026 21:56:08 +0200

KVM: selftests: Add KVM syscall wrapper for pthread_create()Add and use a KVM wrapper for pthread_create() syscall so that selftestsdon't need to manually assert that the syscall succeeded.Note, most tests don't actually assert success, but they all obviouslyrely on the syscall to succeed.Other than explicitly failing if pthread_create() fails, no functionalchange intended.Link: https://patch.msgid.link/20260731195612.2697986-9-seanjc@google.comSigned-off-by: Sean Christopherson List of files: /linux/tools/testing/selftests/kvm/irq_test.c

2708ecca4dbdb51e40e0f6ada9154d7162b09623 - KVM: selftests: Add xAPIC support in eventfd IRQ test

Fri, 26 Jun 2026 23:35:33 +0200

KVM: selftests: Add xAPIC support in eventfd IRQ testExtend the eventfd IRQ test with a '-x' flag to let the user run the testin xAPIC mode instead of the default x2APIC mode. When using xAPIC mode,sanity check user input to ensure the test is being run with at most 255vCPUs, as xAPIC can only address IDs 0-254 (255, i.e. 0xff, broadcasts toall CPUs).Signed-off-by: David Matlack Co-developed-by: Josh Hilke Signed-off-by: Josh Hilke [sean: add sanity check on number of vCPUs]Link: https://patch.msgid.link/20260626213534.3866178-21-seanjc@google.comSigned-off-by: Sean Christopherson List of files: /linux/tools/testing/selftests/kvm/irq_test.c

0315713a19388010b6c9f904cd6544ef6ef3a802 - KVM: selftests: Make number of vCPUs configurable in IRQ test

Fri, 26 Jun 2026 23:35:32 +0200

KVM: selftests: Make number of vCPUs configurable in IRQ testExtend the eventfd IRQ test with a '-v' flag to allow the user toconfigure the number of vCPUs to create and run (versus only ever using asingle vCPU).Update the routing logic to play nice with 32 bit IDs, enable x2APIC formatin KVM (to enable 32-bit ID routing), and disable KVM's x2APIC broadcastquirk so that targeting vCPU 255 doesn't blast the interrupt to all vCPUswhen in x2APIC mode.Signed-off-by: David Matlack Co-developed-by: Josh Hilke Signed-off-by: Josh Hilke Co-developed-by: Sean Christopherson Link: https://patch.msgid.link/20260626213534.3866178-20-seanjc@google.comSigned-off-by: Sean Christopherson List of files: /linux/tools/testing/selftests/kvm/irq_test.c

6b9470baea6c4c61e501cdf00a3b2b2113d554f8 - KVM: selftests: Verify vCPU migration during IRQ delivery in IRQ test

Fri, 26 Jun 2026 23:35:31 +0200

KVM: selftests: Verify vCPU migration during IRQ delivery in IRQ testExtend the eventfd IRQ test with a '-m' flag to have the test migrate thetarget vCPU to a random physical CPU before triggering its interrupt, e.g.to validate KVM's ability to update device posted IRQ routing.Signed-off-by: David Matlack Co-developed-by: Josh Hilke Signed-off-by: Josh Hilke [sean: pin one vCPU at a time to simplify things, use main()'s affinity]Link: https://patch.msgid.link/20260626213534.3866178-19-seanjc@google.comSigned-off-by: Sean Christopherson List of files: /linux/tools/testing/selftests/kvm/irq_test.c

25e268b76e771525fa2fca3205ad0a708d55792a - KVM: selftests: Verify non-postable IRQ remapping in IRQ test

Fri, 26 Jun 2026 23:35:27 +0200

KVM: selftests: Verify non-postable IRQ remapping in IRQ testExtend the eventfd IRQ test with an '-n' flag to route a subset of deviceinterrupts as NMIs (Non-Maskable Interrupts) into the guest using analternating pattern of 4 NMIs followed by 4 regular interrupts.While this adds coverage for NMI injection, the primary goal is tovalidate KVM's handling of non-postable interrupt delivery (AMD and IntelIOMMUs only support posting fixed IRQs targeting a single vCPU). KVMhas historically bungled handling transitions between posted and remappedmodes. Use NMIs to stress the transitions, because they are a reliable,architectural way to force these code paths.Signed-off-by: David Matlack Co-developed-by: Josh Hilke Signed-off-by: Josh Hilke [sean: add GUEST_RECEIVED_INTERRUPT(), massage changelog]Link: https://patch.msgid.link/20260626213534.3866178-15-seanjc@google.comSigned-off-by: Sean Christopherson List of files: /linux/tools/testing/selftests/kvm/irq_test.c

38950af64a1ca9dc6a0279b6d0881e54ed3a5921 - KVM: selftests: Make number of IRQs configurable in IRQ test

Fri, 26 Jun 2026 23:35:26 +0200

KVM: selftests: Make number of IRQs configurable in IRQ testExtend the eventfd IRQ test with a '-i' flag to let the user specify thethe number of IRQs to generate (instead of hardcoding the test to alwaysgenerate 1000 interrupts).Signed-off-by: David Matlack Co-developed-by: Josh Hilke Signed-off-by: Josh Hilke [sean: massage changelog]Link: https://patch.msgid.link/20260626213534.3866178-14-seanjc@google.comSigned-off-by: Sean Christopherson List of files: /linux/tools/testing/selftests/kvm/irq_test.c

ec333e3ace258dde8eddbdded2a8be81b3501cf2 - KVM: selftests: Add option to set empty routing between IRQs in eventfd IRQ test

Fri, 26 Jun 2026 23:35:25 +0200

KVM: selftests: Add option to set empty routing between IRQs in eventfd IRQ testExtend the eventfd IRQ test with an '-e' flag to set empty GSI routingbetween interrupts. Clobbering the GSI routing table verifies that KVMcorrectly handles CPUx => NULL => CPUy transitions, not just CPUx => CPUytransitions, and verifies that KVM can "rebuild" an entire routing setup.Signed-off-by: David Matlack Co-developed-by: Josh Hilke Signed-off-by: Josh Hilke [sean: '-e' for "empty" instead of '-c' for "clear", massage changelog]Link: https://patch.msgid.link/20260626213534.3866178-13-seanjc@google.comSigned-off-by: Sean Christopherson List of files: /linux/tools/testing/selftests/kvm/irq_test.c

197b0cd9ac66bf28f575f2723499f6516bb56f3e - KVM: selftests: Verify interrupts are received when IRQ affinity changes in IRQ test

Fri, 26 Jun 2026 23:35:24 +0200

KVM: selftests: Verify interrupts are received when IRQ affinity changes in IRQ testExtent the eventfd IRQ test with a '-a' flag to randomly affinitize thedevice's host IRQ to different physical CPUs throughout the test. Thisstresses the kernel's ability to maintain correct interrupt routing anddelivery even as the underlying hardware IRQ affinity is changeddynamically via /proc//smp_affinity{,_list}.Signed-off-by: David Matlack Co-developed-by: Josh Hilke Signed-off-by: Josh Hilke [sean: massage changelog]Link: https://patch.msgid.link/20260626213534.3866178-12-seanjc@google.comSigned-off-by: Sean Christopherson List of files: /linux/tools/testing/selftests/kvm/irq_test.c

3902e8b02dce7878b65f10ada5d62def3e2d3a65 - KVM: selftests: Add VFIO device support to eventfd IRQ test

Fri, 26 Jun 2026 23:35:22 +0200

KVM: selftests: Add VFIO device support to eventfd IRQ testExtend the eventfd IRQ test with a '-d' argument that takes a BDF (in theformat segment:bus:device.function) of an interrupt-capable PCI(e) devicebound to VFIO, and use said device to trigger interrupts instead of alwayssynthesizing interrupts via direct writes to the eventfd.Using a VFIO device to trigger interrupts validates the end-to-end deliveryof IRQs for "real" devices, and when supported by hardware (and KVM), alsovalidates interrupt delivery via IRQ bypass, i.e. via device posted IRQs.Now that IOMMUFD is a thing, auto-probe IOMMUFD vs. "legacy" VFIO bytemporarily opening /dev/iommufd, and skip the test if neither IOMMUFD norlegacy VFIO is available. Add a '-t' option to the user override the probelogic, e.g. in case IOMMUFD is available but the system is configured forlegacy usage.Note, the device must have a VFIO selftest driver in order to work withthe test. A helper script to list supported devices will hopefully beavailable in the near future attools/testing/selftests/vfio/scripts/list_supported_devices.sh[1].Example:$ ./tools/testing/selftests/kvm/irq_test -d 0000:06:0a.1Link: https://lore.kernel.org/all/20260602222941.3133236-1-jrhilke%40google.com [1]Signed-off-by: David Matlack Co-developed-by: Josh Hilke Signed-off-by: Josh Hilke Co-developed-by: Sean Christopherson Link: https://patch.msgid.link/20260626213534.3866178-10-seanjc@google.comSigned-off-by: Sean Christopherson List of files: /linux/tools/testing/selftests/kvm/irq_test.c

3ceab37ac973a27a15e72af88d30d7a820b380f4 - KVM: selftests: Add an irqfd send+receive (and later IRQ bypass) test

Fri, 26 Jun 2026 23:35:20 +0200

KVM: selftests: Add an irqfd send+receive (and later IRQ bypass) testAdd a new test, irq_test to verify that KVM correctly delivers interruptsto a running vCPU, when triggered via an eventfd bound to a KVM GSI usingKVM's irqfd mechanism.This test is intentionally simple, for now. Support for sending interruptsvia VFIO devices, for IRQ bypass, and for other features will be added inthe near future.Add the test in common code, even though it currently will only build andrun on x86, as the concept and the bulk of the host-side code isn'tspecific to x86.Suggested-by: Sean Christopherson Link: https://lore.kernel.org/kvm/20250404193923.1413163-68-seanjc@google.comSigned-off-by: David Matlack Co-developed-by: Josh Hilke Signed-off-by: Josh Hilke [sean: use while() and TEST_ASSERT() instead of if-statement => TEST_FAIL()]Link: https://patch.msgid.link/20260626213534.3866178-8-seanjc@google.comSigned-off-by: Sean Christopherson List of files: /linux/tools/testing/selftests/kvm/irq_test.c