[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-Id:
<175450054049.2863135.4614852920454002653.git-patchwork-notify@kernel.org>
Date: Wed, 06 Aug 2025 17:15:40 +0000
From: patchwork-bot+linux-riscv@...nel.org
To: Anup Patel <apatel@...tanamicro.com>
Cc: linux-riscv@...ts.infradead.org, atish.patra@...ux.dev,
palmer@...belt.com, paul.walmsley@...ive.com, alex@...ti.fr,
ajones@...tanamicro.com, anup@...infault.org, kvm@...r.kernel.org,
kvm-riscv@...ts.infradead.org, linux-kernel@...r.kernel.org
Subject: Re: [PATCH v2 0/2] Few timer and AIA fixes for KVM RISC-V
Hello:
This series was applied to riscv/linux.git (for-next)
by Anup Patel <anup@...infault.org>:
On Mon, 7 Jul 2025 09:23:42 +0530 you wrote:
> The RISC-V Privileged specificaiton says the following: "WFI is also
> required to resume execution for locally enabled interrupts pending
> at any privilege level, regardless of the global interrupt enable at
> each privilege level."
>
> Based on the above, if there is pending VS-timer interrupt when the
> host (aka HS-mode) executes WFI then such a WFI will simply become NOP
> and not do anything. This result in QEMU RISC-V consuming a lot of CPU
> time on the x86 machine where it is running. The PATCH1 solves this
> issue by adding appropriate cleanup in KVM RISC-V timer virtualization.
>
> [...]
Here is the summary with links:
- [v2,1/2] RISC-V: KVM: Disable vstimecmp before exiting to user-space
https://git.kernel.org/riscv/c/57f576e860d3
- [v2,2/2] RISC-V: KVM: Move HGEI[E|P] CSR access to IMSIC virtualization
(no matching commit)
You are awesome, thank you!
--
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html
Powered by blists - more mailing lists