Re: [edk2-devel] Alignment fault in __memcpy when SbsaQemu is built uncompressed

2024-06-29 Thread Rebecca Cran
On 6/29/24 9:26 AM, Ard Biesheuvel wrote: It looks like the FvReadFile() call is doing a memory copy from the firmware volume (FV), which seems to be mapped with device attributes rather than normal memory. With a compressed image, the FV will be decompressed to normal RAM, so this can never hap

Re: [edk2-devel] Alignment fault in __memcpy when SbsaQemu is built uncompressed

2024-06-29 Thread Ard Biesheuvel
On Sat, 22 Jun 2024 at 20:04, Rebecca Cran wrote: > > I decided to do some testing around the cost of copying vs decompressing > and moved all the drivers in SbsaQemu into the uncompressed section (as > described in > https://github.com/tianocore/tianocore.github.io/wiki/ArmPkg-Compression), > but

Re: [edk2-devel] Alignment fault in __memcpy when SbsaQemu is built uncompressed

2024-06-24 Thread Marcin Juszkiewicz
W dniu 22.06.2024 o 20:04, Rebecca Cran pisze: I decided to do some testing around the cost of copying vs decompressing and moved all the drivers in SbsaQemu into the uncompressed section (as described in https://github.com/tianocore/tianocore.github.io/wiki/ArmPkg-Compression), but firmware bu

[edk2-devel] Alignment fault in __memcpy when SbsaQemu is built uncompressed

2024-06-22 Thread Rebecca Cran
I decided to do some testing around the cost of copying vs decompressing and moved all the drivers in SbsaQemu into the uncompressed section (as described in https://github.com/tianocore/tianocore.github.io/wiki/ArmPkg-Compression), but firmware built with CLANGDWARF causes an alignment fault w