From: "Chao Du" <duchao@eswincomputing.com>
To: "Daniel Henrique Barboza" <dbarboza@ventanamicro.com>
Cc: qemu-devel@nongnu.org, qemu-riscv@nongnu.org,
pbonzini@redhat.com, alistair23@gmail.com,
bin.meng@windriver.com, liweiwei@iscas.ac.cn,
zhiwei_liu@linux.alibaba.com, palmer@dabbelt.com,
anup@brainfault.org, atishp@atishpatra.org
Subject: Re: [RFC PATCH 0/4] target/riscv/kvm: QEMU support for KVM Guest Debug on RISC-V
Date: Tue, 9 Apr 2024 17:43:15 +0800 (GMT+08:00) [thread overview]
Message-ID: <48d413a8.25e8.18ec23d85b9.Coremail.duchao@eswincomputing.com> (raw)
In-Reply-To: <846ec319-6026-4b14-b156-9e1f42c6dba1@ventanamicro.com>
Hi Daniel and all,
The KVM patches have been reviewd and are in the queue.
https://lore.kernel.org/all/20240402062628.5425-1-duchao@eswincomputing.com/
Could you please review in the QEMU side ?
Then I will rebase this series with your comments.
Some Notes:
1. As the first stage, only the software breakpoints is implemented.
2. A 'corner case' in which the debug exception is not inserted by the
debugger, need to be re-injected to the guest. This is not handled yet
in this series.
Thanks,
Chao
On 2023-12-22 22:16, Daniel Henrique Barboza <dbarboza@ventanamicro.com> wrote:
>
> Hi,
>
> It seems that we still need the kernel KVM side to be sorted out first [1],
> so I believe we should wait a bit until we can review this RFC. Otherwise we
> might risk reviewing something that has to be changed later.
>
>
> [1] https://lore.kernel.org/kvm/20231221095002.7404-1-duchao@eswincomputing.com/
>
>
> Thanks,
>
> Daniel
>
> On 12/21/23 06:49, Chao Du wrote:
> > This series implements QEMU 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 QEMU 8.2.0-rc4 and is also available at:
> > https://github.com/Du-Chao/qemu/tree/riscv_gd_sw
> >
> > This is dependent on KVM side changes:
> > https://github.com/Du-Chao/linux/tree/riscv_gd_sw
> >
> > Chao Du (4):
> > target/riscv/kvm: add software breakpoints support
> > target/riscv/kvm: implement kvm_arch_update_guest_debug()
> > target/riscv/kvm: handle the exit with debug reason
> > linux-headers: enable KVM GUEST DEBUG for RISC-V
> >
> > accel/kvm/kvm-all.c | 8 +--
> > include/sysemu/kvm.h | 6 +-
> > linux-headers/asm-riscv/kvm.h | 1 +
> > target/arm/kvm64.c | 6 +-
> > target/i386/kvm/kvm.c | 6 +-
> > target/mips/kvm.c | 6 +-
> > target/ppc/kvm.c | 6 +-
> > target/riscv/kvm/kvm-cpu.c | 101 ++++++++++++++++++++++++++++++++++
> > target/s390x/kvm/kvm.c | 6 +-
> > 9 files changed, 130 insertions(+), 16 deletions(-)
> >
> > --
> > 2.17.1
> >
next prev parent reply other threads:[~2024-04-09 9:45 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-12-21 9:49 [RFC PATCH 0/4] target/riscv/kvm: QEMU support for KVM Guest Debug on RISC-V Chao Du
2023-12-21 9:49 ` [RFC PATCH 1/4] target/riscv/kvm: add software breakpoints support Chao Du
2024-04-16 9:23 ` Daniel Henrique Barboza
2024-04-18 9:46 ` Chao Du
2024-05-24 16:11 ` Paolo Bonzini
2024-05-27 2:12 ` Chao Du
2023-12-21 9:49 ` [RFC PATCH 2/4] target/riscv/kvm: implement kvm_arch_update_guest_debug() Chao Du
2023-12-21 9:49 ` [RFC PATCH 3/4] target/riscv/kvm: handle the exit with debug reason Chao Du
2023-12-21 9:49 ` [RFC PATCH 4/4] linux-headers: enable KVM GUEST DEBUG for RISC-V Chao Du
2023-12-22 14:16 ` [RFC PATCH 0/4] target/riscv/kvm: QEMU support for KVM Guest Debug on RISC-V Daniel Henrique Barboza
2024-04-09 9:43 ` Chao Du [this message]
2024-04-15 1:47 ` Chao Du
2024-04-16 9:25 ` Daniel Henrique Barboza
2024-05-20 10:22 ` 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=48d413a8.25e8.18ec23d85b9.Coremail.duchao@eswincomputing.com \
--to=duchao@eswincomputing.com \
--cc=alistair23@gmail.com \
--cc=anup@brainfault.org \
--cc=atishp@atishpatra.org \
--cc=bin.meng@windriver.com \
--cc=dbarboza@ventanamicro.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.