From: Andre Przywara <andre.przywara@arm.com>
To: Alexandru Elisei <alexandru.elisei@arm.com>
Cc: kvmarm@lists.cs.columbia.edu, kvm@vger.kernel.org
Subject: Re: [kvm-unit-tests PATCH 2/7] lib: arm: Remove warning about uart0_base mismatch
Date: Thu, 24 Jan 2019 11:59:43 +0000 [thread overview]
Message-ID: <20190124115943.12296810@donnerap.cambridge.arm.com> (raw)
In-Reply-To: <20190124111634.4727-3-alexandru.elisei@arm.com>
On Thu, 24 Jan 2019 11:16:29 +0000
Alexandru Elisei <alexandru.elisei@arm.com> wrote:
> A warning is displayed if uart0_base is different from what the code
> expects qemu to generate for the pl011 UART in the device tree.
> However, now we support the ns16550a UART emulated by kvmtool, which
> has a different address. This leads to the warning being displayed
> even though the UART is configured and working as expected.
>
> Now that we support multiple UARTs, the warning serves no purpose, so
> remove it.
Mmh, but we use that address before, right? So for anything not
emulating an UART at this QEMU specific address we write to some random
(device) memory?
Drew, how important is this early print feature for kvm-unit-tests?
Cheers,
Andre.
>
> Signed-off-by: Alexandru Elisei <alexandru.elisei@arm.com>
> ---
> lib/arm/io.c | 6 ------
> 1 file changed, 6 deletions(-)
>
> diff --git a/lib/arm/io.c b/lib/arm/io.c
> index 35fc05aeb4db..87435150f73e 100644
> --- a/lib/arm/io.c
> +++ b/lib/arm/io.c
> @@ -61,12 +61,6 @@ static void uart0_init(void)
> }
>
> uart0_base = ioremap(base.addr, base.size);
> -
> - if (uart0_base != (u8 *)UART_EARLY_BASE) {
> - printf("WARNING: early print support may not work. "
> - "Found uart at %p, but early base is %p.\n",
> - uart0_base, (u8 *)UART_EARLY_BASE);
> - }
> }
>
> void io_init(void)
next prev parent reply other threads:[~2019-01-24 11:59 UTC|newest]
Thread overview: 39+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-01-24 11:16 [kvm-unit-tests PATCH 0/7] arm/arm64: Add support for running under kvmtool Alexandru Elisei
2019-01-24 11:16 ` [kvm-unit-tests PATCH 1/7] lib: arm: Discover ns16550a UART Alexandru Elisei
2019-01-24 11:54 ` Andre Przywara
2019-01-24 13:11 ` Andrew Jones
2019-01-25 14:07 ` Alexandru Elisei
2019-01-24 11:16 ` [kvm-unit-tests PATCH 2/7] lib: arm: Remove warning about uart0_base mismatch Alexandru Elisei
2019-01-24 11:59 ` Andre Przywara [this message]
2019-01-24 12:37 ` Andrew Jones
2019-01-25 16:36 ` Alexandru Elisei
2019-01-25 16:47 ` Andrew Jones
2019-01-28 14:24 ` Alexandru Elisei
2019-01-28 16:31 ` Andrew Jones
2019-01-28 17:58 ` Andre Przywara
2019-01-29 10:32 ` Andrew Jones
2019-01-29 11:16 ` Alexandru Elisei
2019-01-29 12:23 ` Andrew Jones
2019-01-29 13:40 ` Alexandru Elisei
2019-01-24 11:16 ` [kvm-unit-tests PATCH 3/7] lib: chr-testdev: Make chr_testdev_init() return status Alexandru Elisei
2019-01-24 12:56 ` Andrew Jones
2019-01-24 11:16 ` [kvm-unit-tests PATCH 4/7] lib: arm: Implement PSCI SYSTEM_OFF in psci_system_off() Alexandru Elisei
2019-01-24 13:01 ` Andrew Jones
2019-01-25 14:08 ` Alexandru Elisei
2019-01-25 14:25 ` Andrew Jones
2019-01-24 11:16 ` [kvm-unit-tests PATCH 5/7] lib: arm: Fallback to psci_system_off() in exit() Alexandru Elisei
2019-01-24 13:00 ` Andrew Jones
2019-01-24 13:35 ` Andrew Jones
2019-01-25 14:56 ` Alexandru Elisei
2019-01-25 15:31 ` Andrew Jones
2019-01-25 15:51 ` Alexandru Elisei
2019-01-25 16:05 ` Andrew Jones
2019-01-25 16:14 ` Andre Przywara
2019-01-25 16:44 ` Alexandru Elisei
2019-01-25 16:50 ` Andrew Jones
2019-01-25 14:18 ` Alexandru Elisei
2019-01-24 11:16 ` [kvm-unit-tests PATCH 6/7] lib: argv: Implement argv_find() for test parameters Alexandru Elisei
2019-01-24 11:16 ` [kvm-unit-tests PATCH 7/7] arm/arm64: Use argv_find() for test names Alexandru Elisei
2019-01-24 13:07 ` Andrew Jones
2019-01-24 13:43 ` Andre Przywara
2019-01-28 12:16 ` Alexandru Elisei
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=20190124115943.12296810@donnerap.cambridge.arm.com \
--to=andre.przywara@arm.com \
--cc=alexandru.elisei@arm.com \
--cc=kvm@vger.kernel.org \
--cc=kvmarm@lists.cs.columbia.edu \
/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