From: "Philippe Mathieu-Daudé" <philmd@linaro.org>
To: Alistair Francis <alistair23@gmail.com>,
qemu-devel@nongnu.org, alex.bennee@linaro.org,
peter.maydell@linaro.org
Cc: "Bin Meng" <bmeng.cn@gmail.com>,
palmer@dabbelt.com, liwei1518@gmail.com,
zhiwei_liu@linux.alibaba.com, qemu-riscv@nongnu.org,
"Alistair Francis" <Alistair.Francis@wdc.com>,
"Paolo Bonzini" <pbonzini@redhat.com>,
"Marc-André Lureau" <marcandre.lureau@redhat.com>,
atishp@rivosinc.com, dbarboza@ventanamicro.com,
"Thomas Huth" <thuth@redhat.com>
Subject: Re: [PATCH v4 2/2] hw/char: sifive_uart: Print uart characters async
Date: Tue, 10 Sep 2024 09:16:19 +0200 [thread overview]
Message-ID: <998e3864-f091-41a7-8616-3f2e5357d059@linaro.org> (raw)
In-Reply-To: <20240910045419.1252277-3-alistair.francis@wdc.com>
On 10/9/24 06:54, Alistair Francis wrote:
> The current approach of using qemu_chr_fe_write() and ignoring the
> return values results in dropped characters [1].
>
> Let's update the SiFive UART to use a async sifive_uart_xmit() function
> to transmit the characters and apply back pressure to the guest with
> the SIFIVE_UART_TXFIFO_FULL status.
>
> This should avoid dropped characters and more realisticly model the
> hardware.
>
> 1: https://gitlab.com/qemu-project/qemu/-/issues/2114
>
> Signed-off-by: Alistair Francis <alistair.francis@wdc.com>
> Reviewed-by: Daniel Henrique Barboza <dbarboza@ventanamicro.com>
> Tested-by: Thomas Huth <thuth@redhat.com>
> ---
> include/hw/char/sifive_uart.h | 16 +++++-
> hw/char/sifive_uart.c | 94 ++++++++++++++++++++++++++++++++---
> 2 files changed, 102 insertions(+), 8 deletions(-)
> +static void sifive_uart_write_tx_fifo(SiFiveUARTState *s, const uint8_t *buf,
> + int size)
> +{
> + uint64_t current_time = qemu_clock_get_ns(QEMU_CLOCK_VIRTUAL);
> +
> + if (size > fifo8_num_free(&s->tx_fifo)) {
> + size = fifo8_num_free(&s->tx_fifo);
> + qemu_log_mask(LOG_GUEST_ERROR, "sifive_uart: TX FIFO overflow");
> + }
> +
> + fifo8_push_all(&s->tx_fifo, buf, size);
> +
> + if (fifo8_is_full(&s->tx_fifo)) {
> + s->txfifo |= SIFIVE_UART_TXFIFO_FULL;
> + }
> +
> + timer_mod(s->fifo_trigger_handle, current_time + 100);
Preferably using a #define instead of this magic '100' value (no
need to repost):
Reviewed-by: Philippe Mathieu-Daudé <philmd@linaro.org>
> +}
next prev parent reply other threads:[~2024-09-10 7:16 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-09-10 4:54 [PATCH v4 0/2] riscv: char: Avoid dropped charecters Alistair Francis
2024-09-10 4:54 ` [PATCH v4 1/2] hw/char: riscv_htif: Use blocking qemu_chr_fe_write_all Alistair Francis
2024-09-10 7:16 ` Philippe Mathieu-Daudé
2024-09-10 4:54 ` [PATCH v4 2/2] hw/char: sifive_uart: Print uart characters async Alistair Francis
2024-09-10 7:16 ` Philippe Mathieu-Daudé [this message]
2024-09-10 20:34 ` Mark Cave-Ayland
2024-09-11 1:53 ` Alistair Francis
2024-10-17 13:22 ` [PATCH v4 0/2] riscv: char: Avoid dropped charecters Thomas Huth
2024-10-21 3:44 ` Alistair Francis
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=998e3864-f091-41a7-8616-3f2e5357d059@linaro.org \
--to=philmd@linaro.org \
--cc=Alistair.Francis@wdc.com \
--cc=alex.bennee@linaro.org \
--cc=alistair23@gmail.com \
--cc=atishp@rivosinc.com \
--cc=bmeng.cn@gmail.com \
--cc=dbarboza@ventanamicro.com \
--cc=liwei1518@gmail.com \
--cc=marcandre.lureau@redhat.com \
--cc=palmer@dabbelt.com \
--cc=pbonzini@redhat.com \
--cc=peter.maydell@linaro.org \
--cc=qemu-devel@nongnu.org \
--cc=qemu-riscv@nongnu.org \
--cc=thuth@redhat.com \
--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).