From: Andrew Jones <andrew.jones@linux.dev>
To: Thomas Huth <thuth@redhat.com>
Cc: Alexandru Elisei <alexandru.elisei@arm.com>,
Eric Auger <eric.auger@redhat.com>,
kvm@vger.kernel.org, Nicholas Piggin <npiggin@gmail.com>,
kvmarm@lists.linux.dev
Subject: Re: [kvm-unit-tests PATCH] lib/arm/io: Fix calling getchar() multiple times
Date: Mon, 19 Feb 2024 15:22:07 +0100 [thread overview]
Message-ID: <20240219-a8fd2613c2a3dc474c966ffb@orel> (raw)
In-Reply-To: <20240216140210.70280-1-thuth@redhat.com>
On Fri, Feb 16, 2024 at 03:02:10PM +0100, Thomas Huth wrote:
> getchar() can currently only be called once on arm since the implementation
> is a little bit too naïve: After the first character has arrived, the
> data register never gets set to zero again. To properly check whether a
> byte is available, we need to check the "RX fifo empty" on the pl011 UART
> or the "RX data ready" bit on the ns16550a UART instead.
>
> With this proper check in place, we can finally also get rid of the
> ugly assert(count < 16) statement here.
>
> Signed-off-by: Thomas Huth <thuth@redhat.com>
> ---
> lib/arm/io.c | 34 ++++++++++++++--------------------
> 1 file changed, 14 insertions(+), 20 deletions(-)
>
> diff --git a/lib/arm/io.c b/lib/arm/io.c
> index c15e57c4..836fa854 100644
> --- a/lib/arm/io.c
> +++ b/lib/arm/io.c
> @@ -28,6 +28,7 @@ static struct spinlock uart_lock;
> */
> #define UART_EARLY_BASE (u8 *)(unsigned long)CONFIG_UART_EARLY_BASE
> static volatile u8 *uart0_base = UART_EARLY_BASE;
> +bool is_pl011_uart;
>
> static void uart0_init_fdt(void)
> {
> @@ -59,7 +60,10 @@ static void uart0_init_fdt(void)
> abort();
> }
>
> + is_pl011_uart = (i == 0);
> } else {
> + is_pl011_uart = !fdt_node_check_compatible(dt_fdt(), ret,
> + "arm,pl011");
> ret = dt_pbus_translate_node(ret, 0, &base);
> assert(ret == 0);
> }
> @@ -111,31 +115,21 @@ void puts(const char *s)
> spin_unlock(&uart_lock);
> }
>
> -static int do_getchar(void)
> +int __getchar(void)
> {
> - int c;
> + int c = -1;
>
> spin_lock(&uart_lock);
> - c = readb(uart0_base);
> - spin_unlock(&uart_lock);
> -
> - return c ?: -1;
> -}
> -
> -/*
> - * Minimalist implementation for migration completion detection.
> - * Without FIFOs enabled on the QEMU UART device we just read
> - * the data register: we cannot read more than 16 characters.
> - */
> -int __getchar(void)
> -{
> - int c = do_getchar();
> - static int count;
>
> - if (c != -1)
> - ++count;
> + if (is_pl011_uart) {
> + if (!(readb(uart0_base + 6 * 4) & 0x10)) /* RX not empty? */
> + c = readb(uart0_base);
> + } else {
> + if (readb(uart0_base + 5) & 0x01) /* RX data ready? */
> + c = readb(uart0_base);
> + }
I think I'd eventually prefer encapsulating these separate implementations
into a console device, but that might be a bit heavy handed for a fix that
we want to pull into the multi-migration series.
Thanks,
drew
next prev parent reply other threads:[~2024-02-19 14:22 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-02-16 14:02 [kvm-unit-tests PATCH] lib/arm/io: Fix calling getchar() multiple times Thomas Huth
2024-02-17 10:43 ` Nicholas Piggin
2024-02-19 6:59 ` Thomas Huth
2024-02-19 11:58 ` Nicholas Piggin
2024-02-19 13:46 ` Andrew Jones
2024-02-17 14:28 ` Nicholas Piggin
2024-02-19 14:22 ` Andrew Jones [this message]
2024-02-19 16:56 ` Alexandru Elisei
2024-02-20 1:37 ` Nicholas Piggin
2024-02-20 8:51 ` Nicholas Piggin
2024-02-20 10:22 ` Alexandru Elisei
2024-02-21 3:39 ` Nicholas Piggin
2024-02-21 7:42 ` Andrew Jones
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=20240219-a8fd2613c2a3dc474c966ffb@orel \
--to=andrew.jones@linux.dev \
--cc=alexandru.elisei@arm.com \
--cc=eric.auger@redhat.com \
--cc=kvm@vger.kernel.org \
--cc=kvmarm@lists.linux.dev \
--cc=npiggin@gmail.com \
--cc=thuth@redhat.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