From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on aws-us-west-2-korg-lkml-1.web.codeaurora.org Received: from bombadil.infradead.org (bombadil.infradead.org [198.137.202.133]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by smtp.lore.kernel.org (Postfix) with ESMTPS id 420DFCDE008 for ; Fri, 26 Jun 2026 08:22:16 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=lists.infradead.org; s=bombadil.20210309; h=Sender: Content-Transfer-Encoding:Content-Type:List-Subscribe:List-Help:List-Post: List-Archive:List-Unsubscribe:List-Id:Cc:To:In-Reply-To:References:Date: Message-Id:From:Subject:MIME-Version:Reply-To:Content-ID:Content-Description: Resent-Date:Resent-From:Resent-Sender:Resent-To:Resent-Cc:Resent-Message-ID: List-Owner; bh=zCaWLONIb9hX6F8OLA38fhKfZamI3OMU7EsCF8TPEvg=; b=RuVUcKxz4nVOll QeEEoNK4McXXlPwjFmBvMHRx0ed+Fe31OnXuqPAkNwQKvUPC59mmRY6VUNoYj3ejtJKI+5AEPJYmX q2CRLtmTyZFs0HEqWdV9s9AbzUU2KKQzptZ0rMJYNpioGxufE5MKJbd8S5Zo2kjUJCOEj+eCIc0cl BTBmTr+lFTbZE+4cyVUtNIoLJfo1Tsrwa5BPDs09E1kKC5zEOl9ZBe/Xen3R8ZIZ9V3ODWjmtbFwA gcvHTWWrSjLH4ihfhafqU3Jz96znV7NgrnO7lD+J6ipHcS48AdtG9TXCItesM90wBdoZm74uIvZND JvIhngRGvNX/8QnmQhxg==; Received: from localhost ([::1] helo=bombadil.infradead.org) by bombadil.infradead.org with esmtp (Exim 4.99.1 #2 (Red Hat Linux)) id 1wd1p7-0000000AolZ-0x8E; Fri, 26 Jun 2026 08:22:05 +0000 Received: from tor.source.kernel.org ([2600:3c04:e001:324:0:1991:8:25]) by bombadil.infradead.org with esmtps (Exim 4.99.1 #2 (Red Hat Linux)) id 1wd1of-0000000AnhS-0cVb; Fri, 26 Jun 2026 08:21:38 +0000 Received: from smtp.kernel.org (quasi.space.kernel.org [100.103.45.18]) by tor.source.kernel.org (Postfix) with ESMTP id A074160220; Fri, 26 Jun 2026 08:21:35 +0000 (UTC) Received: by smtp.kernel.org (Postfix) with ESMTPSA id 564071F000E9; Fri, 26 Jun 2026 08:21:35 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=kernel.org; s=k20260515; t=1782462095; bh=9ng+K5LtfItZozFyW5DaKLk3vg89jUk5p+Jo40h/pz0=; h=Subject:From:Date:References:In-Reply-To:To:Cc; b=gy9obNaagDLrQoDnAOJ9mWpvqgzIicpqyoeod0wvdXDDe+Li3tUihiHwItm8IN9PR j2CMjq8Hhphd8FC9VSV+2cEQEMVhXUS1Stp59UV8bNTu+pBxueYh2S45iDWfZ/qaym DLBjQnHS26sbvZAkitK+HeZo4FtglhDXlWF3+RxBNfJ+mdam37U4E+OReRc7HZWT3M iwShpsnaYenuj21+AJcPCuUzrqfHiWRN02laL9IdavxX9tiqUmmKEJ36cwNsgvzHXa GXdaMOleHY3lHrkOmx7h9DsqT++WIHzHTWg/2JsQBpXWJ07Zjy2d2WGlhbVTQv9GSy FUppLP2bY7jPw== Received: from [10.30.226.235] (localhost [IPv6:::1]) by aws-us-west-2-korg-oddjob-rhel9-1.codeaurora.org (Postfix) with ESMTP id 93AC539389E8; Fri, 26 Jun 2026 08:21:23 +0000 (UTC) MIME-Version: 1.0 Subject: Re: [PATCH] RISC-V: KVM: Fix timer state restore From: patchwork-bot+linux-riscv@kernel.org Message-Id: <178246208225.3816447.7133626201153668356.git-patchwork-notify@kernel.org> Date: Fri, 26 Jun 2026 08:21:22 +0000 References: <20260526075544.796396-1-maqianga@uniontech.com> In-Reply-To: <20260526075544.796396-1-maqianga@uniontech.com> To: Qiang Ma Cc: linux-riscv@lists.infradead.org, anup@brainfault.org, atish.patra@linux.dev, pjw@kernel.org, palmer@dabbelt.com, aou@eecs.berkeley.edu, alex@ghiti.fr, kvm@vger.kernel.org, kvm-riscv@lists.infradead.org, linux-kernel@vger.kernel.org X-BeenThere: linux-riscv@lists.infradead.org X-Mailman-Version: 2.1.34 Precedence: list List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: "linux-riscv" Errors-To: linux-riscv-bounces+linux-riscv=archiver.kernel.org@lists.infradead.org Hello: This patch was applied to riscv/linux.git (fixes) by Anup Patel : 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 _______________________________________________ linux-riscv mailing list linux-riscv@lists.infradead.org http://lists.infradead.org/mailman/listinfo/linux-riscv