From: Chao Du <duchao@eswincomputing.com>
To: 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: [RFC PATCH 0/3] RISC-V: KVM: Guest Debug Support
Date: Thu, 21 Dec 2023 09:49:59 +0000 [thread overview]
Message-ID: <20231221095002.7404-1-duchao@eswincomputing.com> (raw)
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
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
next reply other threads:[~2023-12-21 9:51 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-12-21 9:49 Chao Du [this message]
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
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=20231221095002.7404-1-duchao@eswincomputing.com \
--to=duchao@eswincomputing.com \
--cc=anup@brainfault.org \
--cc=aou@eecs.berkeley.edu \
--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;
as well as URLs for NNTP newsgroup(s).