From: patchwork-bot+linux-riscv@kernel.org
To: Anup Patel <anup@brainfault.org>
Cc: linux-riscv@lists.infradead.org, pbonzini@redhat.com,
palmer@dabbelt.com, pjw@kernel.org,
andrew.jones@oss.qualcomm.com, atish.patra@linux.dev,
kvm-riscv@lists.infradead.org, kvm@vger.kernel.org
Subject: Re: [GIT PULL] KVM/riscv changes for 7.1
Date: Thu, 30 Apr 2026 04:08:37 +0000 [thread overview]
Message-ID: <177752211779.2274119.18444543512578889035.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <CAAhSdy0sU997x67zZe00ZVPVrOT-=X8zOUk3OxWXeDcn-rHeXA@mail.gmail.com>
Hello:
This pull request was applied to riscv/linux.git (for-next)
by Paolo Bonzini <pbonzini@redhat.com>:
On Sun, 12 Apr 2026 18:44:24 +0530 you wrote:
> Hi Paolo,
>
> We have the following KVM RISC-V changes for 7.1:
> 1) Fixes for issues in steal time accounting, vector and
> PMU which were discovered by KVM API fuzzing
> 2) Split huge pages during fault handling for dirty logging
> so that write permission is restored for smaller pages
> 3) Improve kvm_arch_vcpu_load() performance by skipping
> CSR restore if VCPU is reloaded on the same core
> 4) Implement kvm_arch_has_default_irqchip() for KVM selftests
> 5) Support configuration of per-VM HGATP mode from KVM
> user space
> 6) Some more preparatory changes for nested virtualization
> such as:
> 6.1) Factored-out ISA checks into separate sources
> 6.2) Added hideleg to struct kvm_vcpu_config
> 6.3) Factored-out VCPU config into separate sources
>
> [...]
Here is the summary with links:
- [GIT,PULL] KVM/riscv changes for 7.1
https://git.kernel.org/riscv/c/d880d2a9c694
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
prev parent reply other threads:[~2026-04-30 4:09 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-04-12 13:14 [GIT PULL] KVM/riscv changes for 7.1 Anup Patel
2026-04-13 9:43 ` Paolo Bonzini
2026-04-30 3:25 ` patchwork-bot+linux-riscv
2026-04-30 4:08 ` patchwork-bot+linux-riscv [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=177752211779.2274119.18444543512578889035.git-patchwork-notify@kernel.org \
--to=patchwork-bot+linux-riscv@kernel.org \
--cc=andrew.jones@oss.qualcomm.com \
--cc=anup@brainfault.org \
--cc=atish.patra@linux.dev \
--cc=kvm-riscv@lists.infradead.org \
--cc=kvm@vger.kernel.org \
--cc=linux-riscv@lists.infradead.org \
--cc=palmer@dabbelt.com \
--cc=pbonzini@redhat.com \
--cc=pjw@kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox