Re: [PATCH] hw/arm/boot: set initrd parameters to 64bit in fdt

Peter Maydell writes: > On Tue, 8 Nov 2022 at 02:35, Schspa Shi 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

Re: [PATCH] hw/arm/boot: set initrd parameters to 64bit in fdt

On Tue, 8 Nov 2022 at 02:35, Schspa Shi 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-

Re: [PATCH] hw/arm/boot: set initrd parameters to 64bit in fdt

On Wed, 16 Nov 2022 at 13:14, Peter Maydell wrote: > > On Wed, 16 Nov 2022 at 06:11, Schspa Shi wrote: > > Yes, I think we should accept this patch, because it will not affect > > 32-bit devices, and provides support for 64-bit devices to put initrd > > above 4GB. > > Yes, I agree. However since

Re: [PATCH] hw/arm/boot: set initrd parameters to 64bit in fdt

Peter Maydell writes: > On Wed, 16 Nov 2022 at 06:11, Schspa Shi wrote: >> >> >> Peter Maydell writes: >> >> > On Tue, 8 Nov 2022 at 15:50, Schspa Shi wrote: >> >> >> >> >> >> Peter Maydell writes: >> >> >> >> > On Tue, 8 Nov 2022 at 13:54, Peter Maydell >> >> > wrote: >> >> >> >> >> >> O

Re: [PATCH] hw/arm/boot: set initrd parameters to 64bit in fdt

On Wed, 16 Nov 2022 at 06:11, Schspa Shi wrote: > > > Peter Maydell writes: > > > On Tue, 8 Nov 2022 at 15:50, Schspa Shi wrote: > >> > >> > >> Peter Maydell writes: > >> > >> > On Tue, 8 Nov 2022 at 13:54, Peter Maydell > >> > wrote: > >> >> > >> >> On Tue, 8 Nov 2022 at 12:52, Schspa Shi w

Re: [PATCH] hw/arm/boot: set initrd parameters to 64bit in fdt

Peter Maydell writes: > On Tue, 8 Nov 2022 at 15:50, Schspa Shi wrote: >> >> >> Peter Maydell writes: >> >> > On Tue, 8 Nov 2022 at 13:54, Peter Maydell >> > wrote: >> >> >> >> On Tue, 8 Nov 2022 at 12:52, Schspa Shi wrote: >> >> > I think this lowmem does not mean below 4GB. and it is to

Re: [PATCH] hw/arm/boot: set initrd parameters to 64bit in fdt

On Tue, 8 Nov 2022 at 15:50, Schspa Shi wrote: > > > Peter Maydell writes: > > > On Tue, 8 Nov 2022 at 13:54, Peter Maydell wrote: > >> > >> On Tue, 8 Nov 2022 at 12:52, Schspa Shi wrote: > >> > I think this lowmem does not mean below 4GB. and it is to make sure > >> > the initrd_start > memblo

Re: [PATCH] hw/arm/boot: set initrd parameters to 64bit in fdt

Peter Maydell writes: > On Tue, 8 Nov 2022 at 13:54, Peter Maydell wrote: >> >> On Tue, 8 Nov 2022 at 12:52, Schspa Shi wrote: >> > Alex Bennée writes: >> > > There is a whole comment in boot.c talking about keeping initrd within >> > > lowmem: >> > > >> > > /* >> > > * We want to p

Re: [PATCH] hw/arm/boot: set initrd parameters to 64bit in fdt

On Tue, 8 Nov 2022 at 13:54, Peter Maydell wrote: > > On Tue, 8 Nov 2022 at 12:52, Schspa Shi wrote: > > Alex Bennée writes: > > > There is a whole comment in boot.c talking about keeping initrd within > > > lowmem: > > > > > > /* > > > * We want to put the initrd far enough into RAM th

Re: [PATCH] hw/arm/boot: set initrd parameters to 64bit in fdt

On Tue, 8 Nov 2022 at 12:52, Schspa Shi wrote: > Alex Bennée writes: > > There is a whole comment in boot.c talking about keeping initrd within > > lowmem: > > > > /* > > * We want to put the initrd far enough into RAM that when the > > * kernel is uncompressed it will not clobber t

Re: [PATCH] hw/arm/boot: set initrd parameters to 64bit in fdt

Alex Bennée writes: > Schspa Shi writes: > >> 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. >> >> [0.00] [ cut here ]--

Re: [PATCH] hw/arm/boot: set initrd parameters to 64bit in fdt

Schspa Shi writes: > 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. > > [0.00] [ cut here ] > [0.00] initrd n

[PATCH] hw/arm/boot: set initrd parameters to 64bit in fdt

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. [0.00] [ cut here ] [0.00] initrd not fully accessible via the linear