From: Andrew Jones <ajones@ventanamicro.com>
To: Chao Du <duchao@eswincomputing.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, haibo1.xu@intel.com, duchao713@qq.com
Subject: Re: [PATCH v4 3/3] RISC-V: KVM: selftests: Add ebreak test support
Date: Tue, 2 Apr 2024 17:36:06 +0200 [thread overview]
Message-ID: <20240402-d3a3ebd7da7998f4928f47ba@orel> (raw)
In-Reply-To: <20240402062628.5425-4-duchao@eswincomputing.com>
On Tue, Apr 02, 2024 at 06:26:28AM +0000, Chao Du wrote:
> Initial support for RISC-V KVM ebreak test. Check the exit reason and
> the PC when guest debug is enabled. Also to make sure the guest could
> handle the ebreak exception without exiting to the VMM when guest debug
> is not enabled.
>
> Signed-off-by: Chao Du <duchao@eswincomputing.com>
> ---
> tools/testing/selftests/kvm/Makefile | 1 +
> .../testing/selftests/kvm/riscv/ebreak_test.c | 82 +++++++++++++++++++
> 2 files changed, 83 insertions(+)
> create mode 100644 tools/testing/selftests/kvm/riscv/ebreak_test.c
>
> diff --git a/tools/testing/selftests/kvm/Makefile b/tools/testing/selftests/kvm/Makefile
> index 741c7dc16afc..7f4430242c9e 100644
> --- a/tools/testing/selftests/kvm/Makefile
> +++ b/tools/testing/selftests/kvm/Makefile
> @@ -189,6 +189,7 @@ TEST_GEN_PROGS_s390x += rseq_test
> TEST_GEN_PROGS_s390x += set_memory_region_test
> TEST_GEN_PROGS_s390x += kvm_binary_stats_test
>
> +TEST_GEN_PROGS_riscv += riscv/ebreak_test
> TEST_GEN_PROGS_riscv += arch_timer
> TEST_GEN_PROGS_riscv += demand_paging_test
> TEST_GEN_PROGS_riscv += dirty_log_test
> diff --git a/tools/testing/selftests/kvm/riscv/ebreak_test.c b/tools/testing/selftests/kvm/riscv/ebreak_test.c
> new file mode 100644
> index 000000000000..823c132069b4
> --- /dev/null
> +++ b/tools/testing/selftests/kvm/riscv/ebreak_test.c
> @@ -0,0 +1,82 @@
> +// SPDX-License-Identifier: GPL-2.0
> +/*
> + * RISC-V KVM ebreak test.
> + *
> + * Copyright 2024 Beijing ESWIN Computing Technology Co., Ltd.
> + *
> + */
> +#include "kvm_util.h"
> +
> +#define LABEL_ADDRESS(v) ((uint64_t)&(v))
> +
> +extern unsigned char sw_bp_1, sw_bp_2;
> +static uint64_t sw_bp_addr;
> +
> +static void guest_code(void)
> +{
> + asm volatile(
> + ".option push\n"
> + ".option norvc\n"
> + "sw_bp_1: ebreak\n"
> + "sw_bp_2: ebreak\n"
> + ".option pop\n"
> + );
> + GUEST_ASSERT_EQ(READ_ONCE(sw_bp_addr), LABEL_ADDRESS(sw_bp_2));
> +
> + GUEST_DONE();
> +}
> +
> +static void guest_breakpoint_handler(struct ex_regs *regs)
> +{
> + WRITE_ONCE(sw_bp_addr, regs->epc);
> + regs->epc += 4;
> +}
> +
> +int main(void)
> +{
> + struct kvm_vm *vm;
> + struct kvm_vcpu *vcpu;
> + uint64_t pc;
> + struct kvm_guest_debug debug = {
> + .control = KVM_GUESTDBG_ENABLE,
> + };
> +
> + TEST_REQUIRE(kvm_has_cap(KVM_CAP_SET_GUEST_DEBUG));
> +
> + vm = vm_create_with_one_vcpu(&vcpu, guest_code);
> +
> + vm_init_vector_tables(vm);
> + vcpu_init_vector_tables(vcpu);
> + vm_install_exception_handler(vm, EXC_BREAKPOINT,
> + guest_breakpoint_handler);
> +
> + /*
> + * Enable the guest debug.
> + * ebreak should exit to the VMM with KVM_EXIT_DEBUG reason.
> + */
> + vcpu_guest_debug_set(vcpu, &debug);
> + vcpu_run(vcpu);
> +
> + TEST_ASSERT_KVM_EXIT_REASON(vcpu, KVM_EXIT_DEBUG);
> +
> + vcpu_get_reg(vcpu, RISCV_CORE_REG(regs.pc), &pc);
> + TEST_ASSERT_EQ(pc, LABEL_ADDRESS(sw_bp_1));
> +
> + /* skip sw_bp_1 */
> + vcpu_set_reg(vcpu, RISCV_CORE_REG(regs.pc), pc + 4);
> +
> + /*
> + * Disable all debug controls.
> + * Guest should handle the ebreak without exiting to the VMM.
> + */
> + memset(&debug, 0, sizeof(debug));
> + vcpu_guest_debug_set(vcpu, &debug);
> +
> + vcpu_run(vcpu);
> +
> + TEST_ASSERT_EQ(get_ucall(vcpu, NULL), UCALL_DONE);
> +
> + kvm_vm_free(vm);
> +
> + return 0;
> +}
> --
> 2.17.1
>
Reviewed-by: Andrew Jones <ajones@ventanamicro.com>
next prev parent reply other threads:[~2024-04-02 15:36 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-04-02 6:26 [PATCH v4 0/3] RISC-V: KVM: Guest Debug Support - Software Breakpoint Part Chao Du
2024-04-02 6:26 ` [PATCH v4 1/3] RISC-V: KVM: Implement kvm_arch_vcpu_ioctl_set_guest_debug() Chao Du
2024-04-02 6:26 ` [PATCH v4 2/3] RISC-V: KVM: Handle breakpoint exits for VCPU Chao Du
2024-04-02 6:26 ` [PATCH v4 3/3] RISC-V: KVM: selftests: Add ebreak test support Chao Du
2024-04-02 15:36 ` Andrew Jones [this message]
2024-04-08 11:51 ` [PATCH v4 0/3] RISC-V: KVM: Guest Debug Support - Software Breakpoint Part Anup Patel
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=20240402-d3a3ebd7da7998f4928f47ba@orel \
--to=ajones@ventanamicro.com \
--cc=anup@brainfault.org \
--cc=aou@eecs.berkeley.edu \
--cc=atishp@atishpatra.org \
--cc=dbarboza@ventanamicro.com \
--cc=duchao713@qq.com \
--cc=duchao@eswincomputing.com \
--cc=haibo1.xu@intel.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