Re: [PATCH] RISC-V: KVM: Add arch-specific tracepoints
Anup Patel <[email protected]> Tue, 28 Jul 2026 21:05:39 +0530
| Newsgroups | org.infradead.lists.linux-riscv,org.infradead.lists.kvm-riscv,org.kernel.vger.kvm,org.kernel.vger.linux-kernel |
|---|---|
| Message-ID | <CAAhSdy2Qa2DGFzb27MgmoH5Pf1BOrgwaZBqP__U9eejs5-5Bsw@mail.gmail.com> |
On Fri, Jun 26, 2026 at 4:07 PM Yuhang.chen <[email protected]> wrote: > > Add RISC-V KVM tracepoints for events that are useful when debugging > guest exits and in-kernel emulation paths. The existing kvm_entry and > kvm_exit tracepoints are kept, with the kvm_entry PC format fixed to use > zero-padded hexadecimal output. > > The newly added tracepoints cover: > > * kvm_guest_fault for G-stage page faults > * kvm_irq_line for userspace IRQ injection > * kvm_mmio_emulate for MMIO load/store emulation > * kvm_timer_update_irq for VS timer interrupt updates > * kvm_wait_riscv for trapped WFI/WRS instructions > * kvm_sbi_ecall for SBI ecalls > * kvm_csr_access for CSR emulation Drop kvm_guest_fault, kvm_sbi_ecall, kvm_wait_riscv, and kvm_csr_access tracepoints. Instead add common kvm_vcpu_exit tracepoint for all vcpu exits just before the switch case in kvm_riscv_vcpu_exit() function. Drop the kvm_irq_line and kvm_timer_update_irq tracepoints. Instead add common kvm_vcpu_irq tracepoint called from kvm_riscv_vcpu_set/unset_interrupt() function. The kvm_mmio_emulate tracepoint is fine. Regards, Anup _______________________________________________ linux-riscv mailing list [email protected] http://lists.infradead.org/mailman/listinfo/linux-riscv