From: Thomas Huth <thuth@redhat.com>
To: Alistair Francis <alistair23@gmail.com>,
peter.maydell@linaro.org, qemu-devel@nongnu.org,
alex.bennee@linaro.org
Cc: liwei1518@gmail.com, atishp@rivosinc.com, palmer@dabbelt.com,
"Bin Meng" <bmeng.cn@gmail.com>,
zhiwei_liu@linux.alibaba.com,
"Paolo Bonzini" <pbonzini@redhat.com>,
dbarboza@ventanamicro.com, qemu-riscv@nongnu.org,
"Alistair Francis" <Alistair.Francis@wdc.com>,
"Marc-André Lureau" <marcandre.lureau@redhat.com>
Subject: Re: [PATCH v2 2/2] hw/char: sifive_uart: Print uart charecters async
Date: Tue, 3 Sep 2024 07:53:59 +0200 [thread overview]
Message-ID: <585e9a05-2ef8-4abf-be7d-a64948e28851@redhat.com> (raw)
In-Reply-To: <20240819113148.3007047-3-alistair.francis@wdc.com>
On 19/08/2024 13.31, Alistair Francis wrote:
> The current approach of using qemu_chr_fe_write() and ignoring the
> return values results in dropped charecters [1].
s/charecters/characters/g
(also in the subject of the patch)
> Let's update the SiFive UART to use a async sifive_uart_xmit() function
> to transmit the charecters and apply back preassure to the guest with
s/preassure/pressure/
> the SIFIVE_UART_TXFIFO_FULL status.
>
> This should avoid dropped charecters and more realisiticly model the
s/realisiticly/realisticly/
> hardware.
>
> 1: https://gitlab.com/qemu-project/qemu/-/issues/2114
>
> Signed-off-by: Alistair Francis <alistair.francis@wdc.com>
> ---
> include/hw/char/sifive_uart.h | 17 ++++++-
> hw/char/sifive_uart.c | 88 +++++++++++++++++++++++++++++++++--
> 2 files changed, 99 insertions(+), 6 deletions(-)
>
> diff --git a/include/hw/char/sifive_uart.h b/include/hw/char/sifive_uart.h
> index 7f6c79f8bd..b43109bb8b 100644
> --- a/include/hw/char/sifive_uart.h
> +++ b/include/hw/char/sifive_uart.h
> @@ -24,6 +24,7 @@
> #include "hw/qdev-properties.h"
> #include "hw/sysbus.h"
> #include "qom/object.h"
> +#include "qemu/fifo8.h"
>
> enum {
> SIFIVE_UART_TXFIFO = 0,
> @@ -48,9 +49,13 @@ enum {
> SIFIVE_UART_IP_RXWM = 2 /* Receive watermark interrupt pending */
> };
>
> +#define SIFIVE_UART_TXFIFO_FULL 0x80000000
> +
> #define SIFIVE_UART_GET_TXCNT(txctrl) ((txctrl >> 16) & 0x7)
> #define SIFIVE_UART_GET_RXCNT(rxctrl) ((rxctrl >> 16) & 0x7)
> +
> #define SIFIVE_UART_RX_FIFO_SIZE 8
> +#define SIFIVE_UART_TX_FIFO_SIZE 8
>
> #define TYPE_SIFIVE_UART "riscv.sifive.uart"
> OBJECT_DECLARE_SIMPLE_TYPE(SiFiveUARTState, SIFIVE_UART)
> @@ -63,13 +68,21 @@ struct SiFiveUARTState {
> qemu_irq irq;
> MemoryRegion mmio;
> CharBackend chr;
> - uint8_t rx_fifo[SIFIVE_UART_RX_FIFO_SIZE];
> - uint8_t rx_fifo_len;
> +
> + uint32_t txfifo;
> uint32_t ie;
> uint32_t ip;
> uint32_t txctrl;
> uint32_t rxctrl;
> uint32_t div;
> +
> + uint8_t rx_fifo[SIFIVE_UART_RX_FIFO_SIZE];
> + uint8_t rx_fifo_len;
> +
> + Fifo8 tx_fifo;
> +
> + QEMUTimer *fifo_trigger_handle;
> + uint64_t char_tx_time;
> };
>
> SiFiveUARTState *sifive_uart_create(MemoryRegion *address_space, hwaddr base,
> diff --git a/hw/char/sifive_uart.c b/hw/char/sifive_uart.c
> index 7fc6787f69..07730e241c 100644
> --- a/hw/char/sifive_uart.c
> +++ b/hw/char/sifive_uart.c
> @@ -64,6 +64,72 @@ static void sifive_uart_update_irq(SiFiveUARTState *s)
> }
> }
>
> +static gboolean sifive_uart_xmit(void *do_not_use, GIOCondition cond,
> + void *opaque)
> +{
> + SiFiveUARTState *s = opaque;
> + int ret;
> + const uint8_t *charecters;
> + uint32_t numptr = 0;
> +
> + /* instant drain the fifo when there's no back-end */
> + if (!qemu_chr_fe_backend_connected(&s->chr)) {
> + fifo8_reset(&s->tx_fifo);
> + return G_SOURCE_REMOVE;
> + }
> +
> + if (fifo8_is_empty(&s->tx_fifo)) {
> + return G_SOURCE_REMOVE;
> + }
> +
> + /* Don't pop the FIFO incase the write fails */
s/incase/in case/
> + charecters = fifo8_peek_bufptr(&s->tx_fifo,
> + fifo8_num_used(&s->tx_fifo), &numptr);
> + ret = qemu_chr_fe_write(&s->chr, charecters, numptr);
> +
> + if (ret >= 0) {
> + /* We wrote the data, actuallly pop the fifo */
s/actuallly/actually/
I recommend running checkpatch.pl with the --codespell flag ;-)
Anyway, this indeed seems to fix the problem with the avocado test, thank
you very much for tackling this!
Tested-by: Thomas Huth <thuth@redhat.com>
prev parent reply other threads:[~2024-09-03 5:54 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-08-19 11:31 [PATCH v2 0/2] riscv: char: Avoid dropped charecters Alistair Francis
2024-08-19 11:31 ` [PATCH v2 1/2] hw/char: riscv_htif: Use blocking qemu_chr_fe_write_all Alistair Francis
2024-09-03 5:42 ` Thomas Huth
2024-08-19 11:31 ` [PATCH v2 2/2] hw/char: sifive_uart: Print uart charecters async Alistair Francis
2024-09-03 5:53 ` Thomas Huth [this message]
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=585e9a05-2ef8-4abf-be7d-a64948e28851@redhat.com \
--to=thuth@redhat.com \
--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=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).