diff options
author | Daniel Henrique Barboza <dbarboza@ventanamicro.com> | 2025-06-05 06:44:56 -0300 |
---|---|---|
committer | Alistair Francis <alistair.francis@wdc.com> | 2025-07-04 21:09:48 +1000 |
commit | 7ec39d0cc945dd81108e08ca37afcfb3c9e5e012 (patch) | |
tree | 21d7c093f80ddd3ffc485d637321468865b9230f /scripts/qapi/source.py | |
parent | 5000ba0cb1c513283f0a2f2f9742cfe8053dab8d (diff) | |
download | qemu-7ec39d0cc945dd81108e08ca37afcfb3c9e5e012.zip qemu-7ec39d0cc945dd81108e08ca37afcfb3c9e5e012.tar.gz qemu-7ec39d0cc945dd81108e08ca37afcfb3c9e5e012.tar.bz2 |
target/riscv: use qemu_chr_fe_write_all() in DBCN_CONSOLE_WRITE_BYTE
The SBI spec states, for console write byte:
"This is a blocking SBI call and it will only return after writing the
specified byte to the debug console. It will also return, with
SBI_ERR_FAILED, if there are I/O errors."
Being a blocker call will either succeed writing the byte or error out,
it's feasible to use the blocking qemu_chr_fe_write_all() instead of
qemu_chr_fe_write().
Last but not the least, we will duck possible changes in
qemu_chr_fe_write() where ret = 0 will have a 'zero byte written'
semantic [1] - something that we're not ready to deal in this current
state.
[1] https://lore.kernel.org/qemu-devel/CAFEAcA_kEndvNtw4EHySXWwQPoGs029yAzZGGBcV=zGHaj7KUQ@mail.gmail.com/
Signed-off-by: Daniel Henrique Barboza <dbarboza@ventanamicro.com>
Reviewed-by: Philippe Mathieu-Daudé <philmd@linaro.org>
Message-ID: <20250605094456.1385105-2-dbarboza@ventanamicro.com>
Signed-off-by: Alistair Francis <alistair.francis@wdc.com>
Diffstat (limited to 'scripts/qapi/source.py')
0 files changed, 0 insertions, 0 deletions