From: Chao Du <duchao@eswincomputing.com>
To: qemu-devel@nongnu.org, qemu-riscv@nongnu.org,
pbonzini@redhat.com, ajones@ventanamicro.com,
alistair23@gmail.com, bin.meng@windriver.com,
liweiwei@iscas.ac.cn, dbarboza@ventanamicro.com,
zhiwei_liu@linux.alibaba.com, palmer@dabbelt.com,
anup@brainfault.org, duchao713@qq.com
Subject: [PATCH v2 0/3] target/riscv/kvm: QEMU support for KVM Guest Debug on RISC-V
Date: Tue, 28 May 2024 07:20:45 +0000 [thread overview]
Message-ID: <20240528072048.25529-1-duchao@eswincomputing.com> (raw)
This series implements QEMU KVM Guest Debug on RISC-V, with which we
could debug RISC-V KVM guest from the host side, using software
breakpoints.
This series is based on riscv-to-apply.next branch (v9.0.0) and is also
available at:
https://github.com/Du-Chao/alistair23-qemu/tree/riscv-to-apply.next.0528
The corresponding KVM side patches have been merged already:
https://lore.kernel.org/kvm/20240402062628.5425-1-duchao@eswincomputing.com/
A TODO list which will be added later:
1. HW breakpoints support
2. A 'corner case' in which the debug exception is not inserted by the
debugger, need to be re-injected to the guest.
v1->v2:
- squash patch #2 into #1
- check the instruction length from the tail two bits, instead of passing the
length information by parameters.
RFC->v1:
- Rebased on riscv-to-apply.next
- use configs/ definition to conditionalize debug support
v1 link:
https://lore.kernel.org/qemu-riscv/20240527021916.12953-1-duchao@eswincomputing.com/
RFC link:
https://lore.kernel.org/qemu-riscv/20231221094923.7349-1-duchao@eswincomputing.com/
Chao Du (3):
target/riscv/kvm: add software breakpoints support
target/riscv/kvm: handle the exit with debug reason
target/riscv/kvm: define TARGET_KVM_HAVE_GUEST_DEBUG
configs/targets/riscv64-softmmu.mak | 1 +
target/riscv/kvm/kvm-cpu.c | 89 +++++++++++++++++++++++++++++
2 files changed, 90 insertions(+)
--
2.17.1
next reply other threads:[~2024-05-28 7:27 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-05-28 7:20 Chao Du [this message]
2024-05-28 7:20 ` [PATCH v2 1/3] target/riscv/kvm: add software breakpoints support Chao Du
2024-05-28 7:20 ` [PATCH v2 2/3] target/riscv/kvm: handle the exit with debug reason Chao Du
2024-05-28 7:20 ` [PATCH v2 3/3] target/riscv/kvm: define TARGET_KVM_HAVE_GUEST_DEBUG 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=20240528072048.25529-1-duchao@eswincomputing.com \
--to=duchao@eswincomputing.com \
--cc=ajones@ventanamicro.com \
--cc=alistair23@gmail.com \
--cc=anup@brainfault.org \
--cc=bin.meng@windriver.com \
--cc=dbarboza@ventanamicro.com \
--cc=duchao713@qq.com \
--cc=liweiwei@iscas.ac.cn \
--cc=palmer@dabbelt.com \
--cc=pbonzini@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=qemu-riscv@nongnu.org \
--cc=zhiwei_liu@linux.alibaba.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.