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, ajones@ventanamicro.com, atishp@rivosinc.com,
atish.patra@linux.dev, kvm-riscv@lists.infradead.org,
kvm@vger.kernel.org
Subject: Re: [GIT PULL v2] KVM/riscv changes for 6.17
Date: Sun, 10 Aug 2025 21:12:20 +0000 [thread overview]
Message-ID: <175486034099.1221929.4746664358148231967.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <CAAhSdy1084USuM+k9T-AP7X_=s7x+WFv++U0PkjVojbPbjRCrw@mail.gmail.com>
Hello:
This pull request was applied to riscv/linux.git (fixes)
by Paolo Bonzini <pbonzini@redhat.com>:
On Tue, 29 Jul 2025 17:04:22 +0530 you wrote:
> Hi Paolo,
>
> We have the following KVM RISC-V changes for 6.17:
> 1) Enabled ring-based dirty memory tracking
> 2) Improved "perf kvm stat" to report interrupt events
> 3) Delegate illegal instruction trap to VS-mode
> 4) MMU related improvements for KVM RISC-V for the
> upcoming nested virtualization support
>
> [...]
Here is the summary with links:
- [GIT,PULL,v2] KVM/riscv changes for 6.17
https://git.kernel.org/riscv/c/65164fd0f6b5
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
next prev parent reply other threads:[~2025-08-10 21:14 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-07-29 11:34 [GIT PULL v2] KVM/riscv changes for 6.17 Anup Patel
2025-08-10 21:12 ` patchwork-bot+linux-riscv [this message]
2025-08-10 21:40 ` patchwork-bot+linux-riscv
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=175486034099.1221929.4746664358148231967.git-patchwork-notify@kernel.org \
--to=patchwork-bot+linux-riscv@kernel.org \
--cc=ajones@ventanamicro.com \
--cc=anup@brainfault.org \
--cc=atish.patra@linux.dev \
--cc=atishp@rivosinc.com \
--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 \
/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