From: Thomas Huth <thuth@redhat.com>
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
Subject: Re: [PATCH v4 0/2] riscv: char: Avoid dropped charecters
Date: Thu, 17 Oct 2024 15:22:45 +0200 [thread overview]
Message-ID: <2ef501ab-df75-418b-9c94-df47b9389723@redhat.com> (raw)
In-Reply-To: <20240910045419.1252277-1-alistair.francis@wdc.com>
On 10/09/2024 06.54, Alistair Francis wrote:
> This series fixes: https://gitlab.com/qemu-project/qemu/-/issues/2114
>
> This converts the RISC-V charecter device callers of qemu_chr_fe_write()
> to either use qemu_chr_fe_write_all() or to call qemu_chr_fe_write() async
> and act on the return value.
>
> v4:
> - Drop the unused char_tx_time
> - Update the migration in vmstate_sifive_uart
> v3:
> - Fixup spelling
> v2:
> - Use Fifo8 for the Sifive UART instead of a custom FIFO
>
> Alistair Francis (2):
> hw/char: riscv_htif: Use blocking qemu_chr_fe_write_all
> hw/char: sifive_uart: Print uart characters async
Hi!
What's the status of these patches? Are they good to go, or do they still
need more work? (I'm asking because I'd like to convert
tests/avocado/riscv_opensbi.py to the functional test framework, but it
would be good to have the problem with the dropped characters fixed first)
Thanks,
Thomas
next prev parent reply other threads:[~2024-10-17 13:23 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é
2024-09-10 20:34 ` Mark Cave-Ayland
2024-09-11 1:53 ` Alistair Francis
2024-10-17 13:22 ` Thomas Huth [this message]
2024-10-21 3:44 ` [PATCH v4 0/2] riscv: char: Avoid dropped charecters 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=2ef501ab-df75-418b-9c94-df47b9389723@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).