From: Schspa Shi <schspa@gmail.com>
To: Peter Maydell <peter.maydell@linaro.org>
Cc: qemu-arm@nongnu.org, qemu-devel@nongnu.org
Subject: Re: [PATCH] hw/arm/boot: set initrd parameters to 64bit in fdt
Date: Tue, 29 Nov 2022 15:50:55 +0800 [thread overview]
Message-ID: <m2bkoqmatm.fsf@gmail.com> (raw)
In-Reply-To: <CAFEAcA_EgkndLQs=1KtXHuvVPLGs9RzHWL3QWG4CWCjbNfipQw@mail.gmail.com>
Peter Maydell <peter.maydell@linaro.org> writes:
> On Tue, 8 Nov 2022 at 02:35, Schspa Shi <schspa@gmail.com> wrote:
>>
>> We use 32bit value for linux,initrd-[start/end], when we have
>> loader_start > 4GB, there will be a wrong initrd_start passed
>> to the kernel, and the kernel will report the following warning
>
>> To fix it, we can change it to u64 type.
>>
>> Signed-off-by: Schspa Shi <schspa@gmail.com>
>> ---
>> hw/arm/boot.c | 4 ++--
>> 1 file changed, 2 insertions(+), 2 deletions(-)
>>
>> diff --git a/hw/arm/boot.c b/hw/arm/boot.c
>> index 57efb61ee419..da719a4f8874 100644
>> --- a/hw/arm/boot.c
>> +++ b/hw/arm/boot.c
>> @@ -638,14 +638,14 @@ int arm_load_dtb(hwaddr addr, const struct arm_boot_info *binfo,
>> }
>>
>> if (binfo->initrd_size) {
>> - rc = qemu_fdt_setprop_cell(fdt, "/chosen", "linux,initrd-start",
>> + rc = qemu_fdt_setprop_u64(fdt, "/chosen", "linux,initrd-start",
>> binfo->initrd_start);
>> if (rc < 0) {
>> fprintf(stderr, "couldn't set /chosen/linux,initrd-start\n");
>> goto fail;
>> }
>>
>> - rc = qemu_fdt_setprop_cell(fdt, "/chosen", "linux,initrd-end",
>> + rc = qemu_fdt_setprop_u64(fdt, "/chosen", "linux,initrd-end",
>> binfo->initrd_start + binfo->initrd_size);
>> if (rc < 0) {
>> fprintf(stderr, "couldn't set /chosen/linux,initrd-end\n");
>
> Hi; the device-tree folks got back to me a bit late on this one,
> but apparently the intention is that these fields should be
> of a size that matches the #address-cells (and they'll fix the
> schema docs to say that at some point). Some future kernel
> or dtb-schema-check might warn about this, and also since it is
> what u-boot does:
> https://github.com/u-boot/u-boot/blob/218e2c45af83f2cb7b1374b9023b4ced6eb0bb77/common/fdt_support.c#L248
> following that same approach is the safest thing in terms of not
> breaking existing code.
>
> I think that to do this in QEMU we just need to call
>
> qemu_fdt_setprop_sized_cells(fdt, "/chosen", "linux,initrd-start",
> acells, binfo->initrd_start);
>
> and similarly for initrd-end.
>
> Would you mind doing a respin and test of this patch that works
> that way?
>
I have made a new patch & test it this way, it works perfectly.
> thanks
> -- PMM
--
BRs
Schspa Shi
prev parent reply other threads:[~2022-11-29 8:21 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-08 2:35 [PATCH] hw/arm/boot: set initrd parameters to 64bit in fdt Schspa Shi
2022-11-08 9:14 ` Alex Bennée
2022-11-08 12:52 ` Schspa Shi
2022-11-08 13:54 ` Peter Maydell
2022-11-08 14:16 ` Peter Maydell
2022-11-08 15:36 ` Schspa Shi
2022-11-10 17:19 ` Peter Maydell
2022-11-16 6:07 ` Schspa Shi
2022-11-16 13:14 ` Peter Maydell
2022-11-16 13:52 ` Schspa Shi
2022-11-22 13:27 ` Peter Maydell
2022-11-28 19:01 ` Peter Maydell
2022-11-29 7:50 ` Schspa Shi [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=m2bkoqmatm.fsf@gmail.com \
--to=schspa@gmail.com \
--cc=peter.maydell@linaro.org \
--cc=qemu-arm@nongnu.org \
--cc=qemu-devel@nongnu.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.