Re: [PATCH 0/1] hw/arm/aspeed: Add fby35 machine type

[Cédric Le Goater]

On 5/4/22 00:47, Peter Delevoryas wrote:
> > On May 3, 2022, at 2:35 PM, Cédric Le Goater <clg@kaod.org> wrote:
> >
> > On 5/3/22 22:44, Peter Delevoryas wrote:
> > > Hey everyone,
> > > I'm submitting another Facebook (Meta Platforms) machine type: this time I'm
> > > including an acceptance test too.
> > > Unfortunately, this machine boots _very_ slowly. 300+ seconds.
> >
> > This is too much for avocado tests.
>
> Erg, yeah I figured as much. I’ll just resubmit it without the avocado test 
> then,
> if that sounds ok to you.
>
> > > I'm not sure why this is (so I don't know how to fix it easily)
> >
> > The fuji has the same kind of problem. It takes ages to load the lzma ramdisk.
> > Could it be a modeling issue ? or how the FW image is compiled ?
>
> Yeah, one reason is that Facebook OpenBMC machines have an unnecessarily
> big initramfs that includes all the rootfs stuff, 

Indeed,

   Trying 'ramdisk@1' ramdisk subimage
     Description:  RAMDISK
     Type:         RAMDisk Image
     Compression:  lzma compressed
     Data Start:   0x2047da18
     Data Size:    21938373 Bytes = 20.9 MiB

That doesn't help for sure.

> whereas regular OpenBMC machines have a smaller initramfs right? 

yes, about 1MB.

> I don’t entirely know what I’m talking about though.
>
> I think most FB machines have moved to zstd compression recently though,
> but this one may have been missed: I can fix that on the image side. I’ll
> also experiment more to see if it’s something wrong with the image, or possibly
> a regression in QEMU. It would really be super awesome if it could boot faster,
> so I’m very motivated to find a solution.

there is something else because loading the kernel on the fuji takes
much longer than on the ast2600-evb and it is the same size :

   Trying 'kernel@1' kernel subimage
     Description:  Linux kernel
     Type:         Kernel Image
     Compression:  uncompressed
     Data Start:   0x201000e0
     Data Size:    3659848 Bytes = 3.5 MiB


Is uboot doing some special CPU configuration which would slow down
emulation ? Try profiling may be.

Thanks,

C.