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, pbonzini@redhat.com,
shuah@kernel.org, dbarboza@ventanamicro.com,
paul.walmsley@sifive.com, palmer@dabbelt.com,
aou@eecs.berkeley.edu, duchao713@qq.com
Subject: Re: [PATCH v1 1/3] RISC-V: KVM: Implement kvm_arch_vcpu_ioctl_set_guest_debug()
Date: Tue, 20 Feb 2024 10:58:25 +0800 (GMT+08:00) [thread overview]
Message-ID: <4a5a30cd.18c.18dc4734699.Coremail.duchao@eswincomputing.com> (raw)
In-Reply-To: <CAK9=C2VZ1t3ctTWKiqeKOALjLh0kJgzVEsZvM=xfc2j7yQOEcQ@mail.gmail.com>
On 2024-02-14 21:19, Anup Patel <apatel@ventanamicro.com> wrote:
>
> On Tue, Feb 6, 2024 at 1:22 PM Chao Du <duchao@eswincomputing.com> wrote:
> >
> > kvm_vm_ioctl_check_extension(): Return 1 if KVM_CAP_SET_GUEST_DEBUG is
> > being checked.
> >
> > kvm_arch_vcpu_ioctl_set_guest_debug(): Update the guest_debug flags
> > from userspace accordingly. Route the breakpoint exceptions to HS mode
> > if the VM is being debugged by userspace, by clearing the corresponding
> > bit in hedeleg CSR.
> >
> > Signed-off-by: Chao Du <duchao@eswincomputing.com>
> > ---
> > arch/riscv/include/uapi/asm/kvm.h | 1 +
> > arch/riscv/kvm/vcpu.c | 15 +++++++++++++--
> > arch/riscv/kvm/vm.c | 1 +
> > 3 files changed, 15 insertions(+), 2 deletions(-)
> >
> > diff --git a/arch/riscv/include/uapi/asm/kvm.h b/arch/riscv/include/uapi/asm/kvm.h
> > index d6b7a5b95874..8890977836f0 100644
> > --- a/arch/riscv/include/uapi/asm/kvm.h
> > +++ b/arch/riscv/include/uapi/asm/kvm.h
> > @@ -17,6 +17,7 @@
> >
> > #define __KVM_HAVE_IRQ_LINE
> > #define __KVM_HAVE_READONLY_MEM
> > +#define __KVM_HAVE_GUEST_DEBUG
> >
> > #define KVM_COALESCED_MMIO_PAGE_OFFSET 1
> >
> > diff --git a/arch/riscv/kvm/vcpu.c b/arch/riscv/kvm/vcpu.c
> > index b5ca9f2e98ac..6cee974592ac 100644
> > --- a/arch/riscv/kvm/vcpu.c
> > +++ b/arch/riscv/kvm/vcpu.c
> > @@ -475,8 +475,19 @@ int kvm_arch_vcpu_ioctl_set_mpstate(struct kvm_vcpu *vcpu,
> > int kvm_arch_vcpu_ioctl_set_guest_debug(struct kvm_vcpu *vcpu,
> > struct kvm_guest_debug *dbg)
> > {
> > - /* TODO; To be implemented later. */
> > - return -EINVAL;
> > + if (dbg->control & KVM_GUESTDBG_ENABLE) {
> > + if (vcpu->guest_debug != dbg->control) {
> > + vcpu->guest_debug = dbg->control;
> > + csr_clear(CSR_HEDELEG, BIT(EXC_BREAKPOINT));
> > + }
> > + } else {
> > + if (vcpu->guest_debug != 0) {
> > + vcpu->guest_debug = 0;
> > + csr_set(CSR_HEDELEG, BIT(EXC_BREAKPOINT));
> > + }
> > + }
>
> This is broken because directly setting breakpoint exception delegation
> in CSR also affects other VCPUs running on the same host CPU.
>
> To address the above, we should do the following:
> 1) Add "unsigned long hedeleg" in "struct kvm_vcpu_config" which
> is pre-initialized in kvm_riscv_vcpu_setup_config() without setting
> EXC_BREAKPOINT bit.
> 2) The kvm_arch_vcpu_ioctl_set_guest_debug() should only set/clear
> EXC_BREAKPOINT bit in "hedeleg" of "struct kvm_vcpu_config".
> 3) The kvm_riscv_vcpu_swap_in_guest_state() must write the
> HEDELEG csr before entering the Guest/VM.
>
> Regards,
> Anup
>
Thanks for the review and detailed suggestion.
Maybe we could make it a bit easier:
1) The kvm_arch_vcpu_ioctl_set_guest_debug() only update vcpu->guest_debug
accordingly.
2) The kvm_riscv_vcpu_swap_in_guest_state() check vcpu->guest_debug and
set/clear the HEDELEG csr accordingly.
Could you confirm if this is OK?
If yes, I will post another revision.
Regards,
Chao
> > +
> > + return 0;
> > }
> >
> > static void kvm_riscv_vcpu_setup_config(struct kvm_vcpu *vcpu)
> > diff --git a/arch/riscv/kvm/vm.c b/arch/riscv/kvm/vm.c
> > index ce58bc48e5b8..7396b8654f45 100644
> > --- a/arch/riscv/kvm/vm.c
> > +++ b/arch/riscv/kvm/vm.c
> > @@ -186,6 +186,7 @@ int kvm_vm_ioctl_check_extension(struct kvm *kvm, long ext)
> > case KVM_CAP_READONLY_MEM:
> > case KVM_CAP_MP_STATE:
> > case KVM_CAP_IMMEDIATE_EXIT:
> > + case KVM_CAP_SET_GUEST_DEBUG:
> > r = 1;
> > break;
> > case KVM_CAP_NR_VCPUS:
> > --
> > 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:[~2024-02-20 3:01 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-02-06 7:49 [PATCH v1 0/3] RISC-V: KVM: Guest Debug Support - Software Breakpoint Part Chao Du
2024-02-06 7:49 ` [PATCH v1 1/3] RISC-V: KVM: Implement kvm_arch_vcpu_ioctl_set_guest_debug() Chao Du
2024-02-14 12:49 ` Anup Patel
2024-02-20 2:58 ` Chao Du [this message]
2024-02-20 4:24 ` Anup Patel
2024-02-21 1:54 ` Chao Du
2024-02-21 3:49 ` Anup Patel
2024-02-21 5:49 ` Chao Du
2024-02-06 7:49 ` [PATCH v1 2/3] RISC-V: KVM: Handle breakpoint exits for VCPU Chao Du
2024-02-14 12:51 ` Anup Patel
2024-02-06 7:49 ` [PATCH v1 3/3] RISC-V: KVM: selftests: Add breakpoints test support 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=4a5a30cd.18c.18dc4734699.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=duchao713@qq.com \
--cc=kvm-riscv@lists.infradead.org \
--cc=kvm@vger.kernel.org \
--cc=palmer@dabbelt.com \
--cc=paul.walmsley@sifive.com \
--cc=pbonzini@redhat.com \
--cc=shuah@kernel.org \
/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