From: Alistair Francis <alistair23@gmail.com>
To: Ajeet Singh <itachis6234@gmail.com>
Cc: qemu-devel@nongnu.org, Mark Corbin <mark@dibsco.co.uk>,
Warner Losh <imp@bsdimp.com>, Ajeet Singh <itachis@freebsd.org>,
Jessica Clarke <jrtc27@jrtc27.com>,
Kyle Evans <kevans@freebsd.org>,
Richard Henderson <richard.henderson@linaro.org>
Subject: Re: [PATCH v4 02/17] bsd-user: Add RISC-V CPU execution loop and syscall handling
Date: Fri, 6 Sep 2024 10:25:57 +1000 [thread overview]
Message-ID: <CAKmqyKMVmF1cXpwca+P2DgYSQ7-Vrny3LO6++2wgKPTrmFeNVQ@mail.gmail.com> (raw)
In-Reply-To: <20240828095243.90491-3-itachis@FreeBSD.org>
On Wed, Aug 28, 2024 at 7:53 PM Ajeet Singh <itachis6234@gmail.com> wrote:
>
> From: Mark Corbin <mark@dibsco.co.uk>
>
> Implemented the RISC-V CPU execution loop, including handling various
> exceptions and system calls. The loop continuously executes CPU
> instructions,processes exceptions, and handles system calls by invoking
> FreeBSD syscall handlers.
>
> Signed-off-by: Mark Corbin <mark@dibsco.co.uk>
> Signed-off-by: Ajeet Singh <itachis@FreeBSD.org>
> Co-authored-by: Jessica Clarke <jrtc27@jrtc27.com>
> Co-authored-by: Kyle Evans <kevans@FreeBSD.org>
> Reviewed-by: Richard Henderson <richard.henderson@linaro.org>
> ---
> bsd-user/riscv/target_arch_cpu.h | 94 ++++++++++++++++++++++++++++++++
> 1 file changed, 94 insertions(+)
>
> diff --git a/bsd-user/riscv/target_arch_cpu.h b/bsd-user/riscv/target_arch_cpu.h
> index e17c910ae9..ba589909e2 100644
> --- a/bsd-user/riscv/target_arch_cpu.h
> +++ b/bsd-user/riscv/target_arch_cpu.h
> @@ -36,4 +36,98 @@ static inline void target_cpu_init(CPURISCVState *env,
> env->pc = regs->sepc;
> }
>
> +static inline void target_cpu_loop(CPURISCVState *env)
> +{
> + CPUState *cs = env_cpu(env);
> + int trapnr;
> + abi_long ret;
> + unsigned int syscall_num;
> + int32_t signo, code;
> +
> + for (;;) {
> + cpu_exec_start(cs);
> + trapnr = cpu_exec(cs);
> + cpu_exec_end(cs);
> + process_queued_cpu_work(cs);
> +
> + signo = 0;
> +
> + switch (trapnr) {
> + case EXCP_INTERRUPT:
> + /* just indicate that signals should be handled asap */
> + break;
> + case EXCP_ATOMIC:
> + cpu_exec_step_atomic(cs);
> + break;
> + case RISCV_EXCP_U_ECALL:
> + syscall_num = env->gpr[xT0];
> + env->pc += TARGET_INSN_SIZE;
> + /* Compare to cpu_fetch_syscall_args() in riscv/riscv/trap.c */
> + if (TARGET_FREEBSD_NR___syscall == syscall_num ||
> + TARGET_FREEBSD_NR_syscall == syscall_num) {
> + ret = do_freebsd_syscall(env,
> + env->gpr[xA0],
> + env->gpr[xA1],
> + env->gpr[xA2],
> + env->gpr[xA3],
> + env->gpr[xA4],
> + env->gpr[xA5],
> + env->gpr[xA6],
> + env->gpr[xA7],
> + 0);
> + } else {
> + ret = do_freebsd_syscall(env,
> + syscall_num,
> + env->gpr[xA0],
> + env->gpr[xA1],
> + env->gpr[xA2],
> + env->gpr[xA3],
> + env->gpr[xA4],
> + env->gpr[xA5],
> + env->gpr[xA6],
> + env->gpr[xA7]
There is trailing white space on these lines and in a few other
patches in this series.
Can you run ./scripts/checkpatch.pl against the changes and then send
a v5 with the issues addressed
Alistair
> + );
> + }
> +
> + /*
> + * Compare to cpu_set_syscall_retval() in
> + * riscv/riscv/vm_machdep.c
> + */
> + if (ret >= 0) {
> + env->gpr[xA0] = ret;
> + env->gpr[xT0] = 0;
> + } else if (ret == -TARGET_ERESTART) {
> + env->pc -= TARGET_INSN_SIZE;
> + } else if (ret != -TARGET_EJUSTRETURN) {
> + env->gpr[xA0] = -ret;
> + env->gpr[xT0] = 1;
> + }
> + break;
> + case RISCV_EXCP_ILLEGAL_INST:
> + signo = TARGET_SIGILL;
> + code = TARGET_ILL_ILLOPC;
> + break;
> + case RISCV_EXCP_BREAKPOINT:
> + signo = TARGET_SIGTRAP;
> + code = TARGET_TRAP_BRKPT;
> + break;
> + case EXCP_DEBUG:
> + signo = TARGET_SIGTRAP;
> + code = TARGET_TRAP_BRKPT;
> + break;
> + default:
> + fprintf(stderr, "qemu: unhandled CPU exception "
> + "0x%x - aborting\n", trapnr);
> + cpu_dump_state(cs, stderr, 0);
> + abort();
> + }
> +
> + if (signo) {
> + force_sig_fault(signo, code, env->pc);
> + }
> +
> + process_pending_signals(env);
> + }
> +}
> +
> #endif /* TARGET_ARCH_CPU_H */
> --
> 2.34.1
>
>
next prev parent reply other threads:[~2024-09-06 0:27 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-08-28 9:52 [PATCH v4 00/17] bsd-user: Comprehensive RISCV Support Ajeet Singh
2024-08-28 9:52 ` [PATCH v4 01/17] bsd-user: Implement RISC-V CPU initialization and main loop Ajeet Singh
2024-08-28 9:52 ` [PATCH v4 02/17] bsd-user: Add RISC-V CPU execution loop and syscall handling Ajeet Singh
2024-09-06 0:25 ` Alistair Francis [this message]
2024-08-28 9:52 ` [PATCH v4 03/17] bsd-user: Implement RISC-V CPU register cloning and reset functions Ajeet Singh
2024-08-28 9:52 ` [PATCH v4 04/17] bsd-user: Implement RISC-V TLS register setup Ajeet Singh
2024-08-28 9:52 ` [PATCH v4 05/17] bsd-user: Add RISC-V ELF definitions and hardware capability detection Ajeet Singh
2024-08-28 9:52 ` [PATCH v4 06/17] bsd-user: Define RISC-V register structures and register copying Ajeet Singh
2024-08-28 9:52 ` [PATCH v4 07/17] bsd-user: Add RISC-V signal trampoline setup function Ajeet Singh
2024-08-28 9:52 ` [PATCH v4 08/17] bsd-user: Implement RISC-V sysarch system call emulation Ajeet Singh
2024-08-28 9:52 ` [PATCH v4 09/17] bsd-user: Add RISC-V thread setup and initialization support Ajeet Singh
2024-08-28 9:52 ` [PATCH v4 10/17] bsd-user: Define RISC-V VM parameters and helper functions Ajeet Singh
2024-08-28 9:52 ` [PATCH v4 11/17] bsd-user: Define RISC-V system call structures and constants Ajeet Singh
2024-08-28 9:52 ` [PATCH v4 12/17] bsd-user: Add generic RISC-V64 target definitions Ajeet Singh
2024-08-28 9:52 ` [PATCH v4 13/17] bsd-user: Define RISC-V signal handling structures and constants Ajeet Singh
2024-08-28 9:52 ` [PATCH v4 14/17] bsd-user: Implement RISC-V signal trampoline setup functions Ajeet Singh
2024-08-28 9:52 ` [PATCH v4 15/17] bsd-user: Implement 'get_mcontext' for RISC-V Ajeet Singh
2024-08-28 9:52 ` [PATCH v4 16/17] bsd-user: Implement set_mcontext and get_ucontext_sigreturn for RISCV Ajeet Singh
2024-08-28 9:52 ` [PATCH v4 17/17] bsd-user: Add RISC-V 64-bit Target Configuration and Debug XML Files Ajeet Singh
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=CAKmqyKMVmF1cXpwca+P2DgYSQ7-Vrny3LO6++2wgKPTrmFeNVQ@mail.gmail.com \
--to=alistair23@gmail.com \
--cc=imp@bsdimp.com \
--cc=itachis6234@gmail.com \
--cc=itachis@freebsd.org \
--cc=jrtc27@jrtc27.com \
--cc=kevans@freebsd.org \
--cc=mark@dibsco.co.uk \
--cc=qemu-devel@nongnu.org \
--cc=richard.henderson@linaro.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;
as well as URLs for NNTP newsgroup(s).