From: Robin Murphy <robin.murphy@arm.com>
To: "Guilherme G. Piccoli" <gpiccoli@igalia.com>,
linux-arm-kernel@lists.infradead.org
Cc: catalin.marinas@arm.com, will@kernel.org, broonie@kernel.org,
u.kleine-koenig@pengutronix.de, kernel@gpiccoli.net
Subject: Re: [PATCH] arm64: Fix early pointer print plus improve comment
Date: Tue, 21 Dec 2021 10:11:28 +0000 [thread overview]
Message-ID: <17cb7d5e-cdee-855d-8ce9-d64c7c7101e1@arm.com> (raw)
In-Reply-To: <20211220155427.1499417-1-gpiccoli@igalia.com>
On 2021-12-20 15:54, Guilherme G. Piccoli wrote:
> When facing a really early issue on DT parsing we have currently
> a message that shows both the physical and virtual address of the
> FDT. The printk pointer modifier there was not right for the physical
> address, due to the hashed address stuff, so hereby we fix that.
>
> Also, we tried to improve a bit commenting on that function, given that
> if kernel fails there, it just hangs forever in a cpu_relax() loop.
> The reason we cannot BUG/panic there is that is too early to do so;
> thanks to Mark Brown for pointing that on IRC.
>
> Signed-off-by: Guilherme G. Piccoli <gpiccoli@igalia.com>
> ---
> arch/arm64/kernel/setup.c | 6 +++++-
> 1 file changed, 5 insertions(+), 1 deletion(-)
>
> diff --git a/arch/arm64/kernel/setup.c b/arch/arm64/kernel/setup.c
> index be5f85b0a24d..0d5c51a9549e 100644
> --- a/arch/arm64/kernel/setup.c
> +++ b/arch/arm64/kernel/setup.c
> @@ -189,11 +189,15 @@ static void __init setup_machine_fdt(phys_addr_t dt_phys)
>
> if (!dt_virt || !early_init_dt_scan(dt_virt)) {
> pr_crit("\n"
> - "Error: invalid device tree blob at physical address %pa (virtual address 0x%p)\n"
> + "Error: invalid device tree blob at physical address %px (virtual address 0x%p)\n"
%pa is the correct specifier for printing a physical address, so I don't
really follow what's being "fixed" here. Especially given that what this
will now do is print the virtual address of the local dt_phys variable
itself. How is that useful?
Robin.
> "The dtb must be 8-byte aligned and must not exceed 2 MB in size\n"
> "\nPlease check your bootloader.",
> &dt_phys, dt_virt);
>
> + /* Note that in this _really_ early stage we cannot even BUG()
> + * or oops, so the least terrible thing to do is cpu_relax(),
> + * or else we could end-up printing non-initialized data, etc.
> + */
> while (true)
> cpu_relax();
> }
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
next prev parent reply other threads:[~2021-12-21 10:12 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-12-20 15:54 [PATCH] arm64: Fix early pointer print plus improve comment Guilherme G. Piccoli
2021-12-21 10:11 ` Robin Murphy [this message]
2021-12-21 14:43 ` Guilherme G. Piccoli
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=17cb7d5e-cdee-855d-8ce9-d64c7c7101e1@arm.com \
--to=robin.murphy@arm.com \
--cc=broonie@kernel.org \
--cc=catalin.marinas@arm.com \
--cc=gpiccoli@igalia.com \
--cc=kernel@gpiccoli.net \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=u.kleine-koenig@pengutronix.de \
--cc=will@kernel.org \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.