From: "Philippe Mathieu-Daudé" <philmd@linaro.org>
To: Daniel Henrique Barboza <dbarboza@ventanamicro.com>,
qemu-devel@nongnu.org
Cc: qemu-riscv@nongnu.org, alistair.francis@wdc.com,
bmeng@tinylab.org, liwei1518@gmail.com,
zhiwei_liu@linux.alibaba.com, palmer@rivosinc.com
Subject: Re: [PATCH] target/riscv/kvm: implement SBI debug console (DBCN) calls
Date: Tue, 3 Jun 2025 15:19:35 +0200 [thread overview]
Message-ID: <eb6bd3d7-c66b-4300-9573-c29830a3aff4@linaro.org> (raw)
In-Reply-To: <20240425155012.581366-1-dbarboza@ventanamicro.com>
Hi Daniel,
(now merged as commit a6b53378f537)
On 25/4/24 17:50, Daniel Henrique Barboza wrote:
> SBI defines a Debug Console extension "DBCN" that will, in time, replace
> the legacy console putchar and getchar SBI extensions.
>
> The appeal of the DBCN extension is that it allows multiple bytes to be
> read/written in the SBI console in a single SBI call.
>
> As far as KVM goes, the DBCN calls are forwarded by an in-kernel KVM
> module to userspace. But this will only happens if the KVM module
> actually supports this SBI extension and we activate it.
>
> We'll check for DBCN support during init time, checking if get-reg-list
> is advertising KVM_RISCV_SBI_EXT_DBCN. In that case, we'll enable it via
> kvm_set_one_reg() during kvm_arch_init_vcpu().
>
> Finally, change kvm_riscv_handle_sbi() to handle the incoming calls for
> SBI_EXT_DBCN, reading and writing as required.
>
> A simple KVM guest with 'earlycon=sbi', running in an emulated RISC-V
> host, takes around 20 seconds to boot without using DBCN. With this
> patch we're taking around 14 seconds to boot due to the speed-up in the
> terminal output. There's no change in boot time if the guest isn't
> using earlycon.
>
> Signed-off-by: Daniel Henrique Barboza <dbarboza@ventanamicro.com>
> ---
> target/riscv/kvm/kvm-cpu.c | 111 +++++++++++++++++++++++++++++
> target/riscv/sbi_ecall_interface.h | 17 +++++
> 2 files changed, 128 insertions(+)
> +static void kvm_riscv_handle_sbi_dbcn(CPUState *cs, struct kvm_run *run)
> +{
> + g_autofree uint8_t *buf = NULL;
> + RISCVCPU *cpu = RISCV_CPU(cs);
> + target_ulong num_bytes;
> + uint64_t addr;
> + unsigned char ch;
> + int ret;
> +
> + switch (run->riscv_sbi.function_id) {
> + case SBI_EXT_DBCN_CONSOLE_READ:
> + case SBI_EXT_DBCN_CONSOLE_WRITE:
> + num_bytes = run->riscv_sbi.args[0];
> +
> + if (num_bytes == 0) {
> + run->riscv_sbi.ret[0] = SBI_SUCCESS;
> + run->riscv_sbi.ret[1] = 0;
> + break;
> + }
> +
> + addr = run->riscv_sbi.args[1];
> +
> + /*
> + * Handle the case where a 32 bit CPU is running in a
> + * 64 bit addressing env.
> + */
> + if (riscv_cpu_mxl(&cpu->env) == MXL_RV32) {
> + addr |= (uint64_t)run->riscv_sbi.args[2] << 32;
> + }
> +
> + buf = g_malloc0(num_bytes);
> +
> + if (run->riscv_sbi.function_id == SBI_EXT_DBCN_CONSOLE_READ) {
> + ret = qemu_chr_fe_read_all(serial_hd(0)->be, buf, num_bytes);
> + if (ret < 0) {
> + error_report("SBI_EXT_DBCN_CONSOLE_READ: error when "
> + "reading chardev");
> + exit(1);
> + }
> +
> + cpu_physical_memory_write(addr, buf, ret);
> + } else {
> + cpu_physical_memory_read(addr, buf, num_bytes);
> +
> + ret = qemu_chr_fe_write_all(serial_hd(0)->be, buf, num_bytes);
> + if (ret < 0) {
> + error_report("SBI_EXT_DBCN_CONSOLE_WRITE: error when "
> + "writing chardev");
> + exit(1);
> + }
> + }
> +
> + run->riscv_sbi.ret[0] = SBI_SUCCESS;
> + run->riscv_sbi.ret[1] = ret;
> + break;
> + case SBI_EXT_DBCN_CONSOLE_WRITE_BYTE:
> + ch = run->riscv_sbi.args[0];
> + ret = qemu_chr_fe_write(serial_hd(0)->be, &ch, sizeof(ch));
> +
> + if (ret < 0) {
> + error_report("SBI_EXT_DBCN_CONSOLE_WRITE_BYTE: error when "
> + "writing chardev");
> + exit(1);
> + }
We are ignoring partial writes (non-blocking call returning 0 byte
written), is that expected? If so, is it OK to add a comment we can
safely discard not-yet-written DBCN_CONSOLE_WRITE_BYTE?
> +
> + run->riscv_sbi.ret[0] = SBI_SUCCESS;
> + run->riscv_sbi.ret[1] = 0;
> + break;
> + default:
> + run->riscv_sbi.ret[0] = SBI_ERR_NOT_SUPPORTED;
> + }
> +}
next prev parent reply other threads:[~2025-06-03 13:21 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-04-25 15:50 [PATCH] target/riscv/kvm: implement SBI debug console (DBCN) calls Daniel Henrique Barboza
2024-04-25 16:04 ` Andrew Jones
2024-04-29 2:23 ` Alistair Francis
2025-06-03 13:19 ` Philippe Mathieu-Daudé [this message]
2025-06-03 18:04 ` Daniel Henrique Barboza
2025-06-04 7:32 ` Philippe Mathieu-Daudé
2025-06-04 9:17 ` Daniel Henrique Barboza
2025-06-04 9:38 ` Philippe Mathieu-Daudé
2025-06-04 10:54 ` Daniel Henrique Barboza
2025-06-04 9:50 ` Daniel P. Berrangé
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=eb6bd3d7-c66b-4300-9573-c29830a3aff4@linaro.org \
--to=philmd@linaro.org \
--cc=alistair.francis@wdc.com \
--cc=bmeng@tinylab.org \
--cc=dbarboza@ventanamicro.com \
--cc=liwei1518@gmail.com \
--cc=palmer@rivosinc.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 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).