Re: [PATCH v2 0/2] Few timer and AIA fixes for KVM RISC-V - patchwork-bot+linux-riscv

From: patchwork-bot+linux-riscv@kernel.org
To: Anup Patel <apatel@ventanamicro.com>
Cc: linux-riscv@lists.infradead.org, atish.patra@linux.dev,
	palmer@dabbelt.com, paul.walmsley@sifive.com, alex@ghiti.fr,
	ajones@ventanamicro.com, anup@brainfault.org,
	kvm@vger.kernel.org, kvm-riscv@lists.infradead.org,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2 0/2] Few timer and AIA fixes for KVM RISC-V
Date: Wed, 06 Aug 2025 17:15:40 +0000	[thread overview]
Message-ID: <175450054049.2863135.4614852920454002653.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20250707035345.17494-1-apatel@ventanamicro.com>

Hello:

This series was applied to riscv/linux.git (for-next)
by Anup Patel <anup@brainfault.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

-- 
kvm-riscv mailing list
kvm-riscv@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/kvm-riscv