Hi Ard, all,
Could you please help explain how the depex section in an image is
mapped in terms of memory attribute?
As my observation, dispatcher locates[1] the depex section inside the
module image and write[2] an evaluated data to the depex if necessary
for scheduled boot order. The problem that the depex section is now in
RO+X memory due to a part of the module image, so a writing to depex
would cause data abort. I'm unsure whether this issue is generic in EDK2
or not.
I think of two approaches:
#1 Relocate the depex section to heap memory for dependency evaluation?
#2 EDK2 build tool to support granting write permission for depex section.
[1] StandaloneMmPkg/Core/FwVol.c:236
[2] StandaloneMmPkg/Core/Dependency.c:256
Thanks,
Nhi
-=-=-=-=-=-=-=-=-=-=-=-
Groups.io Links: You receive all messages sent to this group.
View/Reply Online (#113373): https://edk2.groups.io/g/devel/message/113373
Mute This Topic: https://groups.io/mt/103594587/21656
Group Owner: devel+ow...@edk2.groups.io
Unsubscribe: https://edk2.groups.io/g/devel/unsub [arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-
