From: "Chao Du" <duchao@eswincomputing.com>
To: "Anup Patel" <apatel@ventanamicro.com>
Cc: kvm@vger.kernel.org, kvm-riscv@lists.infradead.org,
anup@brainfault.org, atishp@atishpatra.org,
dbarboza@ventanamicro.com, paul.walmsley@sifive.com,
palmer@dabbelt.com, aou@eecs.berkeley.edu
Subject: Re: Re: [RFC PATCH 0/3] RISC-V: KVM: Guest Debug Support
Date: Mon, 25 Dec 2023 10:52:50 +0800 (GMT+08:00) [thread overview]
Message-ID: <51c6e871.1f32.18c9ee3ae12.Coremail.duchao@eswincomputing.com> (raw)
In-Reply-To: <19434eff.1deb.18c90a3a375.Coremail.duchao@eswincomputing.com>
On 2023-12-22 16:28, Chao Du <duchao@eswincomputing.com> wrote:
>
> On 2023-12-21 21:01, Anup Patel <apatel@ventanamicro.com> wrote:
> >
> > On Thu, Dec 21, 2023 at 3:21 PM Chao Du <duchao@eswincomputing.com> wrote:
> > >
> > > This series implements KVM Guest Debug on RISC-V. Currently, we can
> > > debug RISC-V KVM guest from the host side, with software breakpoints.
> > >
> > > A brief test was done on QEMU RISC-V hypervisor emulator.
> > >
> > > A TODO list which will be added later:
> > > 1. HW breakpoints support
> > > 2. Test cases
> >
> > Himanshu has already done the complete HW breakpoint implementation
> > in OpenSBI, Linux RISC-V, and KVM RISC-V. This is based on the upcoming
> > SBI debug trigger extension draft proposal.
> > (Refer, https://lists.riscv.org/g/tech-debug/message/1261)
> >
> > There are also RISE projects to track these efforts:
> > https://wiki.riseproject.dev/pages/viewpage.action?pageId=394541
> > https://wiki.riseproject.dev/pages/viewpage.action?pageId=394545
> >
> > Currently, we are in the process of upstreaming the OpenSBI support
> > for SBI debug trigger extension. The Linux RISC-V and KVM RISC-V
> > patches require SBI debug trigger extension and Sdtrig extension to
> > be frozen which will happen next year 2024.
> >
> > Regards,
> > Anup
> >
>
> Hi Anup,
>
> Thank you for the information and your great work on the SBI
> Debug Trigger Extension proposal.
>
> So I think that 'HW breakpoints support' in the above TODO list
> will be taken care of by Himanshu following the extension proposal.
>
> On the other hand, if I understand correctly, the software
> breakpoint part of KVM Guest Debug has no dependency on the new
> extension since it does not use the trigger module. Just an
> ebreak substitution is made.
>
> So may I know your suggestion about this RFC? Both in KVM and QEMU.
>
> Regards,
> Chao
>
Hi Anup and all,
I'm still waiting for your comment and suggestion for the next step.
:)
Thanks
> > >
> > > This series is based on Linux 6.7-rc6 and is also available at:
> > > https://github.com/Du-Chao/linux/tree/riscv_gd_sw
> > >
> > > The matched QEMU is available at:
> > > https://github.com/Du-Chao/qemu/tree/riscv_gd_sw
> > >
> > > Chao Du (3):
> > > RISC-V: KVM: Enable the KVM_CAP_SET_GUEST_DEBUG capability
> > > RISC-V: KVM: Implement kvm_arch_vcpu_ioctl_set_guest_debug()
> > > RISC-V: KVM: Handle breakpoint exits for VCPU
> > >
> > > arch/riscv/include/uapi/asm/kvm.h | 1 +
> > > arch/riscv/kvm/vcpu.c | 15 +++++++++++++--
> > > arch/riscv/kvm/vcpu_exit.c | 4 ++++
> > > arch/riscv/kvm/vm.c | 1 +
> > > 4 files changed, 19 insertions(+), 2 deletions(-)
> > >
> > > --
> > > 2.17.1
> > >
> > >
> > > --
> > > kvm-riscv mailing list
> > > kvm-riscv@lists.infradead.org
> > > http://lists.infradead.org/mailman/listinfo/kvm-riscv
next prev parent reply other threads:[~2023-12-25 2:54 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-12-21 9:49 [RFC PATCH 0/3] RISC-V: KVM: Guest Debug Support Chao Du
2023-12-21 9:50 ` [RFC PATCH 1/3] RISC-V: KVM: Enable the KVM_CAP_SET_GUEST_DEBUG capability Chao Du
2023-12-21 9:50 ` [RFC PATCH 2/3] RISC-V: KVM: Implement kvm_arch_vcpu_ioctl_set_guest_debug() Chao Du
2023-12-21 9:50 ` [RFC PATCH 3/3] RISC-V: KVM: Handle breakpoint exits for VCPU Chao Du
2023-12-21 12:31 ` [RFC PATCH 0/3] RISC-V: KVM: Guest Debug Support Anup Patel
2023-12-22 8:28 ` Chao Du
2023-12-25 2:52 ` Chao Du [this message]
2024-01-04 10:22 ` Chao Du
2024-01-04 11:29 ` Anup Patel
2024-01-05 9:42 ` Chao Du
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=51c6e871.1f32.18c9ee3ae12.Coremail.duchao@eswincomputing.com \
--to=duchao@eswincomputing.com \
--cc=anup@brainfault.org \
--cc=aou@eecs.berkeley.edu \
--cc=apatel@ventanamicro.com \
--cc=atishp@atishpatra.org \
--cc=dbarboza@ventanamicro.com \
--cc=kvm-riscv@lists.infradead.org \
--cc=kvm@vger.kernel.org \
--cc=palmer@dabbelt.com \
--cc=paul.walmsley@sifive.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