From: "Marcin Juszkiewicz" <marcin.juszkiewicz@linaro.org>
To: Rebecca Cran <rebecca@bsdio.com>,
"devel@edk2.groups.io" <devel@edk2.groups.io>
Cc: Ard Biesheuvel <ardb@kernel.org>,
Leif Lindholm <quic_llindhol@quicinc.com>
Subject: Re: [edk2-devel] Alignment fault in __memcpy when SbsaQemu is built uncompressed
Date: Mon, 24 Jun 2024 18:47:09 +0200 [thread overview]
Message-ID: <8cdaeb62-6cb8-4367-be66-0e05a7f65833@linaro.org> (raw)
In-Reply-To: <428c3293-3899-4794-a51b-7670331e58a2@bsdio.com>
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 built with CLANGDWARF causes an alignment fault when
> writing the last 64 bytes in __memcpy via FvReadFile ->
> AllocateCopyPool -> InternalAllocateCopyPool -> InternalMemCopyMem ->
> __memcpy (AArch64/CopyMem.S in BaseMemoryLibOptDxe).
I can confirm that managed to reproduce failure. Sorry, but that's all I
can say at the moment. No idea what is going on here.
-=-=-=-=-=-=-=-=-=-=-=-
Groups.io Links: You receive all messages sent to this group.
View/Reply Online (#119698): https://edk2.groups.io/g/devel/message/119698
Mute This Topic: https://groups.io/mt/106820121/7686176
Group Owner: devel+owner@edk2.groups.io
Unsubscribe: https://edk2.groups.io/g/devel/unsub [rebecca@openfw.io]
-=-=-=-=-=-=-=-=-=-=-=-
next prev parent reply other threads:[~2024-06-24 16:47 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-06-22 18:04 [edk2-devel] Alignment fault in __memcpy when SbsaQemu is built uncompressed Rebecca Cran
2024-06-24 16:47 ` Marcin Juszkiewicz [this message]
2024-06-29 15:26 ` Ard Biesheuvel
2024-06-29 17:42 ` Rebecca Cran
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-list 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=8cdaeb62-6cb8-4367-be66-0e05a7f65833@linaro.org \
--to=devel@edk2.groups.io \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox