From: Paolo Bonzini <pbonzini@redhat.com>
To: Anup Patel <anup@brainfault.org>
Cc: Palmer Dabbelt <palmer@dabbelt.com>,
Andrew Jones <ajones@ventanamicro.com>,
Atish Patra <atishp@rivosinc.com>,
Atish Patra <atish.patra@linux.dev>,
"open list:KERNEL VIRTUAL MACHINE FOR RISC-V (KVM/riscv)"
<kvm-riscv@lists.infradead.org>,
KVM General <kvm@vger.kernel.org>,
linux-riscv <linux-riscv@lists.infradead.org>
Subject: Re: [GIT PULL] KVM/riscv changes for 6.17
Date: Mon, 28 Jul 2025 18:12:59 +0200 [thread overview]
Message-ID: <CABgObfaDkfUa+=Dthqx_ZFy418KLFkqy2+tKLaGEZmbZ6SbhBA@mail.gmail.com> (raw)
In-Reply-To: <CAAhSdy3Jr1-8TVcEhiCUrc-DHQSTPE1RjF--marQPtcV6FPjJA@mail.gmail.com>
On Mon, Jul 28, 2025 at 5:55 PM Anup Patel <anup@brainfault.org> wrote:
>
> On Mon, Jul 28, 2025 at 9:22 PM Paolo Bonzini <pbonzini@redhat.com> wrote:
> >
> > On Fri, Jul 25, 2025 at 2:06 PM Anup Patel <anup@brainfault.org> wrote:
> > > RISC-V: perf/kvm: Add reporting of interrupt events
> >
> > Something here ate Quan Zhou's Signed-off-by line, which is present at
> > https://lore.kernel.org/r/9693132df4d0f857b8be3a75750c36b40213fcc0.1726211632.git.zhouquan@iscas.ac.cn
> > but not in your branch.
>
> There were couple of "---" lines in patch description which
> created problems for me so I tried fixing manually and
> accidentally ate Signed-off-by.
>
> Sorry about that.
No problem. Another (and more important) question, for SBI FWFT I
don't see any way for userspace to 1) pick which features are
available 2) retrieve the state and put it back into KVM. Am I missing
something?
Paolo
--
kvm-riscv mailing list
kvm-riscv@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/kvm-riscv
next prev parent reply other threads:[~2025-07-28 17:14 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-07-25 12:06 [GIT PULL] KVM/riscv changes for 6.17 Anup Patel
2025-07-28 15:02 ` Paolo Bonzini
2025-07-28 15:52 ` Paolo Bonzini
2025-07-28 15:55 ` Anup Patel
2025-07-28 16:12 ` Paolo Bonzini [this message]
2025-07-28 16:20 ` Anup Patel
2025-07-28 16:50 ` Paolo Bonzini
2025-07-28 16:53 ` Anup Patel
2025-07-29 11:37 ` Radim Krčmář
2025-07-29 11:58 ` Paolo Bonzini
2025-07-29 12:52 ` Anup Patel
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='CABgObfaDkfUa+=Dthqx_ZFy418KLFkqy2+tKLaGEZmbZ6SbhBA@mail.gmail.com' \
--to=pbonzini@redhat.com \
--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 \
/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;
as well as URLs for NNTP newsgroup(s).