Re: [PATCH] RISC-V: KVM: Fix timer state restore
| Newsgroups | org.infradead.lists.kvm-riscv,org.infradead.lists.linux-riscv,org.kernel.vger.kvm,org.kernel.vger.linux-kernel |
|---|---|
| Message-ID | <178246208225.3816447.7133626201153668356.git-patchwork-notify@kernel.org> |
Hello: This patch was applied to riscv/linux.git (fixes) by Anup Patel <[email protected]>: On Tue, 26 May 2026 15:55:44 +0800 you wrote: > The KVM_REG_RISCV_TIMER_REG(state) one-reg write passes the value > written by userspace to kvm_riscv_vcpu_timer_next_event() when > re-enabling the timer. > > That value is the timer state, KVM_RISCV_TIMER_STATE_ON, not the > timer compare value. During migration or state restore, userspace > restores the compare register separately, which stores the target > cycle in t->next_cycles. Re-arming the timer with the state value > schedules the next event at cycle 1 instead of the restored compare > value, causing the virtual timer to fire too early. > > [...] Here is the summary with links: - RISC-V: KVM: Fix timer state restore https://git.kernel.org/riscv/c/6d4c17ed5620 You are awesome, thank you! -- Deet-doot-dot, I am a bot. https://korg.docs.kernel.org/patchwork/pwbot.html -- kvm-riscv mailing list [email protected] http://lists.infradead.org/mailman/listinfo/kvm-riscv